Privacy policy

1. What we collect

We collect the following information when you use Ruby Native:

• Email address and password (for authentication)
• Apple Developer credentials: Team ID, App Store Connect API Key ID, Issuer ID, and private key (for building and uploading your iOS app)
• Google Play access: you invite our publisher service account to your Play Console. We never see or store your Google password or any other Google credential.
• Android upload key: we generate it for you and keep it so every build is signed with the same key
• App configuration: app name, bundle ID, Android package name, URL, icon, version, and the google-services.json file if you set up push notifications
• Payment information (processed by Stripe, not stored on our servers)

Apps built with Ruby Native also send us a small amount of data. On each launch, the app sends us its bundle ID, its platform, and a random identifier it created on first launch. We use that for one thing: the active devices count on your dashboard, which is how many devices ran your app in the last 30 days. The identifier is never linked to a person and never shared. Like any HTTP request, the ping carries the device's IP address, and we do not store it.

If the app cannot load its configuration from your site, it may also report the error, along with the app version, OS version, and device model, so you can fix it.

To turn off the launch ping, set analytics: false in config/ruby_native.yml.

2. How we use it

Your information is used to:

• Authenticate you and manage your account
• Build your iOS app and upload it to TestFlight
• Build your Android app and upload it to Google Play
• Count the devices running your app and tell you when it cannot load its configuration
• Process payments through Stripe
• Send transactional emails (build status, account updates)

3. How we protect it

Apple Developer credentials and your Android upload key are encrypted at rest. We hold no Google credential at all: our access to your Play Console comes from the invite you grant our service account, and you can revoke it from Play Console at any time. Build processes run in isolated GitHub Actions environments that are destroyed after each build. Payment data is handled entirely by Stripe and never touches our servers.

4. Third-party services

We use the following third-party services:

• Stripe for payment processing
• GitHub Actions for building your app
• Apple App Store Connect for uploading iOS builds to TestFlight
• Google Play Console for uploading Android builds
• Amazon S3 for files you upload (your icon and screenshots) and for encrypted database backups.
• Fathom Analytics for website traffic. Fathom sets no cookies and collects no personal data; we see aggregate numbers like page views and referrers.
• Honeybadger for error reporting.

Each service has its own privacy policy. Your Apple Developer credentials and Android upload key are passed to GitHub Actions only during a build and are not kept there afterward.

5. Data retention

We retain your data for as long as your account is active. If you delete your account, your data (including Apple Developer credentials and your Android upload key) is permanently removed. Build logs are retained for 90 days. Launch pings from your app are kept for 13 months, then deleted.

6. Cookies

We use a session cookie to keep you signed in. We do not use tracking cookies. Our website analytics come from Fathom, which sets no cookies and collects no personal data.

7. Your rights

You can export or delete your data at any time by contacting us. We will respond within 30 days.

8. Changes

We may update this policy from time to time. We will notify you of material changes via email.

9. Contact

Questions about this policy? Email [email protected].