Privacy Policy

Last updated: 29 July 2026

The short version: Suby tracks your subscriptions on your device. We collect a small amount of usage data to keep the app working and never sell it. If you sign in for cloud backup, your data is encrypted in transit and at rest.

1. What we collect

Stored locally on your device

Your subscriptions — service name, price, billing period, payment method, notes — are stored in a database on your device. No account is needed to use Suby, and nothing here is ever sold. Cloud backup is optional, encrypted, and off unless you turn it on.

When you sign in (optional)

If you create an account to enable cloud backup, we collect your email address and an encrypted copy of your subscription data. Authentication is handled by Supabase.

Collected automatically

• Analytics events — which screens you open and which features you use
• The service name and price when you add or edit a subscription
• Crash reports — stack traces, breadcrumbs, app version, device model

Once you sign in, these events carry your account ID, so they are tied to you. Analytics is on by default, and we use it to decide what to build and fix next.

2. How we use your data

• Provide the service. Show your subscriptions, send renewal notifications, calculate totals.
• Improve the app. Understand which features are used so we can prioritize improvements.
• Fix bugs. Crash reports help us identify and fix issues.
• Process payments. Manage Suby Premium subscriptions through RevenueCat and your app store.

We do not sell your data. We do not share it with advertisers. We do not use it to build profiles of you for anything other than running the app you're using.

3. Third-party services

Suby uses the following third-party services. Each has their own privacy policy linked below.

Service	Purpose	Data shared	Privacy policy
Amplitude	Usage analytics	Event names, service names and prices, app version, device model	amplitude.com/privacy
Sentry	Crash reports	Stack traces, breadcrumbs, device info	sentry.io/privacy
Firebase Crashlytics	Crash reports	Stack traces, device info	policies.google.com/privacy
RevenueCat	Subscription billing	Account ID, purchase state	revenuecat.com/privacy
Supabase	Auth and cloud backup (opt-in)	Email, encrypted sync data	supabase.com/privacy
Anthropic	Email receipt extraction (opt-in email scan)	Short snippets of billing emails during a scan — processed in memory, never stored, not used to train AI models	anthropic.com/privacy
Groq	AI-assisted service enrichment (Smart Suggest)	The service name you type in Smart Suggest (no personal data, no subscription details)	groq.com/privacy-policy

4. Google user data (email scan)

Suby offers an optional email scan that finds subscription receipts in your Gmail inbox so you can import them into the app. It only runs when you explicitly connect your Google account, and it works like this:

• Read-only access. Suby requests only the read-only Gmail permission (gmail.readonly). We can never send, modify, or delete your email.
• Your inbox stays on your device. Searching and filtering happen locally in the app, and your Google sign-in token never leaves your device.
• What leaves your device. Only short snippets of emails that look like billing receipts are sent, encrypted in transit, to our server to identify the subscription (service name, price, billing period). We use Anthropic's Claude API as a processor for this step; snippets are processed in memory and are not used to train AI models.
• What we store. Nothing from your email. Our server keeps only anonymous request counts and timestamps for rate limiting. Detected subscriptions are saved only if you choose to import them — locally on your device, like any other subscription.
• No ads, no sale, no profiling. Google user data is never used for advertising, never sold, and never read by humans except with your explicit permission, for security investigations, or where required by law.
• Revoke anytime. You can disconnect Suby's access at myaccount.google.com/permissions.

How we protect Google user data

We apply the following data protection mechanisms to all sensitive data obtained through Google APIs:

• Encryption in transit. All communication between the app, Google's APIs, and our server uses TLS 1.2 or higher (HTTPS). Email snippets are never transmitted over unencrypted connections.
• Encryption at rest. We do not store Gmail message content at all, so there is no Gmail data at rest on our servers. Any other account data stored on our servers (cloud backup, if you opt in) is encrypted at rest using industry-standard AES-256 encryption.
• Token handling. Your Google OAuth access token is short-lived, held only in the app's memory for the duration of a scan, and is never written to disk, never persisted, and never sent to our servers. When the scan ends or the app closes, the token is gone. Refresh tokens are not requested.
• Least-privilege access. We request only the single read-only Gmail scope required for the feature. Server-side, access to production systems is restricted to the developer, protected by multi-factor authentication, and all access is logged.
• No human access. Gmail data is processed automatically. No employee or contractor reads your email content, except with your explicit permission (e.g., a support request), when necessary for security purposes, or where required by law.
• Secure development. Dependencies are kept up to date, code changes are reviewed before release, and we monitor crash and error reports (which never contain email content) to detect and fix security issues promptly.
• Incident response. If we become aware of a data breach affecting Google user data, we will notify affected users and relevant authorities without undue delay, consistent with GDPR and applicable law.
• Deletion. Because we never store your email content, there is nothing to delete on our side after a scan. Revoking access at your Google Account permissions page immediately ends Suby's ability to read your mailbox.

Suby's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of raw or derived user data received from Workspace APIs (including Gmail) will adhere to the Google User Data Policy, including the Limited Use requirements. Google user data is not used to develop, improve, or train generalized AI or machine-learning models, and is never transferred to third-party AI tools that would use it for model training.

5. Your rights

• Access. All your data is in the app — you can see everything we have at any time.
• Export. You can export your subscriptions to CSV from the app settings.
• Delete. Uninstalling the app removes all local data. Deleting your account (if you signed up) removes all cloud-stored data.
• Analytics. Events are deleted automatically after 365 days.

If you're in the EU (GDPR), UK (UK GDPR), or California (CCPA), you have additional rights including the right to lodge a complaint with your local data protection authority. We honor these rights for all users regardless of location.

6. Children's privacy

Suby is not directed at children under 13. We do not knowingly collect data from children under 13. If you believe a child has provided us with personal data, contact us and we'll delete it.

7. Data retention

• Local data: Until you delete it from the app or uninstall.
• Cloud backup data: Until you delete your account.
• Crash reports: Up to 90 days, then automatically deleted.
• Analytics events: Up to 365 days, then automatically deleted.
• Email scan: Email content is never stored. Anonymous scan counters (no content) are kept for abuse prevention.

8. Changes to this policy

We'll update the "Last updated" date at the top whenever we change this policy. Material changes will be communicated via an in-app notice. Continued use after changes constitutes acceptance of the updated policy.

9. Contact us

Questions, requests, or complaints about privacy: support@subyapp.com