1. Who we are
Subik is developed and operated by The Oat Labs, an independent software studio based in Israel, operated by Omer Attias (“The Oat Labs”, “we”, “us”). We are the controller of the personal data described in this policy.
Contact for anything privacy-related: subik@theoatlabs.com. Postal correspondence can be arranged through that address.
2. What Subik does
Subik is a subscription tracker. You sign in, connect the Gmail mailbox your receipts arrive in, and Subik scans it for payment receipts and renewal notices to build a list of the services you pay for. You can also add subscriptions by hand. Subik then shows spend totals, charge history and reminders before renewals. Subik does not connect to your bank, cards or payment providers and does not initiate or cancel any payment.
3. Information we collect
3.1 Account information
You sign in with Sign in with Apple or Google Sign-In. We receive the name and email address you choose to share (Apple’s “Hide My Email” relay addresses work) and a provider account identifier. We create a Subik account keyed to a random user ID and store your display name, chosen language and preferred currency.
3.2 Gmail data
How you connect. Subik does not ask Google for access to your Gmail. You create an app password, a 16-letter code, in your own Google account under App passwords, and paste it into Subik (step by step). Google requires 2-Step Verification for app passwords. Subik never asks for your Google password.
The honest part. The code itself would allow full access to your mailbox: an app password can’t be limited to reading. That is why it never leaves your phone, and why Subik limits what it does instead: it only reads.
Where your mail is read: on your phone. The app keeps the code in your phone’s secure storage and uses it only to read your mailbox from the phone, over an encrypted (TLS) IMAP connection to Gmail. Subik opens the mailbox in a way that changes nothing: it never sends, deletes, moves or labels a message, and never even marks one as read. During a scan the app asks Gmail for messages from the last two years whose subject or sender looks like a payment receipt, invoice, renewal or trial notice. It reads only those messages, headers and body (amounts and dates are in the body), in the phone’s memory, and discards them when the scan ends. Our servers take no part in reading your mail: they never receive it or the code, so they cannot open your mailbox.
What stays on your phone.
- The code, in your phone’s secure storage (the Keychain on iPhone, the Keystore on Android), tied to your Subik account and to that phone. It never moves to another device; a new phone needs its own code.
- The Gmail message identifiers of the receipts behind each subscription, and the bookkeeping that lets a later scan skip messages it has already read (which messages matched, which to retry, when the last scan ran), in encrypted app storage. These are opaque IDs, counts and dates; they contain no message content.
Subik never sends these to our servers. The app also keeps a copy of your subscription list and charge history in the same encrypted app storage so it opens quickly.
What reaches our servers. Only the result of a scan, which you review, edit or delete in the app, and the sender domains you choose to send us (below):
- The subscriptions it found: merchant and product name, the sender’s domain (for example netflix.com — never the full address), amount, currency, billing cadence (weekly, monthly, quarterly, yearly), last and next charge dates, trial end date, category, logo, and detection status (waiting for your review, tracked or dismissed).
- Each subscription’s charge history: the date, amount and currency of every charge found in a receipt.
- Mailbox metadata: the Gmail address you connect, its connection status, when it was last scanned and whether recent scans succeeded.
- Scan records: when each scan ran, what started it, whether it finished and how many subscriptions it added — used to count your free scan and scan credits.
To name what it found, the app also looks up the senders’ domains in our merchant catalog (section 4).
Sender domains you choose to send us. After a scan, the app may list senders whose receipts it couldn’t read. If you tap Help us read them, it shows you those senders’ domains (for example example.com), each one ticked, and sends only the ones you leave ticked when you tap Send. Nothing is sent unless you do this, and you choose again each time. Each domain is stored with the day it was sent and nothing else: not your user ID, and no names, amounts, dates or email content. They are not linked to you or your account.
What never reaches our servers. Email bodies, subject lines, headers, full sender or recipient addresses, attachments, contacts, Gmail message identifiers, the code, your Google password, and any message that was not a receipt. Nothing from your mailbox is written to our logs.
3.3 Subscriptions you add manually
Merchant name, amount, currency, cadence, dates and category — stored exactly like detected subscriptions, marked as manual.
3.4 Purchases
Subik Pro and scan-credit packs are sold through the Apple App Store and Google Play. Purchases are processed by RevenueCat, which validates store receipts on our behalf. We store your entitlement state (plan, expiry, credit balance) and RevenueCat’s pseudonymous customer ID. We never receive your card or bank details — Apple and Google handle payment.
3.5 Notifications
Reminder settings you choose. Renewal reminders, trial alerts and scan results are scheduled by the app on your phone. If you allow notifications, we also store a device push token, used for one thing: when you have Subik Pro with background auto-refresh on, our server sends your phone a silent wake-up push every few days so the app can check your mailbox for new receipts. The push carries no data and shows nothing; the check itself runs on your phone as described in 3.2, and whether it runs depends on your phone’s settings (such as Background App Refresh on iPhone). Pushes travel through Apple’s and Google’s push services via Expo’s push relay.
3.6 Usage analytics (optional)
To understand which features are used, Subik sends a small set of product events (for example “scan completed”, “paywall viewed”, or which step of connecting Gmail you reached) with counts and booleans, tied to your random Subik user ID (before you sign in, a random ID the app creates), to PostHog (EU Cloud). Each event also carries the device model, the OS and app version, and your language and time zone. PostHog works out an approximate location (city and country) from the connection’s IP address and keeps it with the events; the IP address itself is discarded. By design these events cannot carry merchant names, amounts, email addresses, the code or message content. You can turn analytics off in Settings → Privacy & Data → Share usage data.
3.7 Crash and error reports
When the app crashes or hits an error, a report (stack trace, device model, OS and app version, your random user ID, or before you sign in a random installation ID) is sent to Sentry (EU data centre), along with performance measurements such as how long the app takes to start and how long a scan takes. Reports are scrubbed of personal data, and of anything that looks like an app password, before they leave the device.
3.8 Technical data
Our servers receive the usual request metadata (IP address, timestamps, app version) to operate and secure the service. Exchange rates for currency conversion are fetched from a public rates API without any personal data.
4. How we use Gmail data
Subik reads Gmail with the code you created, not through a Google API, so Google’s API rules don’t govern your mail here. We hold ourselves to the same commitments anyway, as our own. They cover the messages the app reads and everything derived from them: the subscription records and charge history in section 3.2 and the merchant catalog below.
- Gmail data is used only to provide and improve Subik’s subscription-detection feature, which is visible and central in the app.
- Your mail is read on your phone; its content never reaches our servers. What does reach us is listed in section 3.2 and is used only to show, sync and remind you about your subscriptions, except the sender domains you choose to send us, which are used only to improve detection (below).
- The merchant catalog is the one thing shared between users: senders’ domains, each mapped to a display name, product, category and logo that we choose ourselves, plus a count of how many times users confirmed it. Confirming a subscription adds one to that count for a sender already in the catalog; it never adds a sender or a name from your mail, so nothing you confirm names another user’s subscriptions. The counts hold no user identifier and nothing else about you — no amounts, dates or email content.
- We do not transfer Gmail data to anyone else, except to our infrastructure processors listed in section 6 as needed to run the feature, for security investigations, or when the law requires it.
- No person at The Oat Labs reads your email — our servers never receive it. We look at your subscription records only when you ask us to (for example to fix a problem you report), or where it is strictly necessary for security or legal compliance. Otherwise we see them only as part of totals across all users (next point).
- Improving detection. To find the senders whose receipts Subik reads wrong, we count, across all users, the subscriptions the scan found that users dismissed in review or deleted from their list, by the sender’s domain (for example netflix.com), out of how many users have any subscription from that sender. We see only these totals, and only for senders that at least three users dismissed. They carry no user identifier and nothing else about you: no names, amounts, dates or email content.
- Learning to read more senders. The sender domains you choose to send us (section 3.2) are used only to teach Subik to read those senders’ receipts. We see them only as totals by domain, and only for domains that users sent at least three times.
- Gmail data is never used for advertising, never sold, never shared with data brokers, never used to assess credit-worthiness, and never used to develop, improve or train generalized AI or machine-learning models.
Google Sign-In. If you sign in with Google, Subik receives the name, email address and account identifier described in section 3.1, and nothing from your mailbox. When you connect Gmail, you pick the account from Google’s list; Subik keeps only its address, as the mailbox you connect.
Subik’s use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Ending access. In the app, Settings → Privacy & Data → Connected inboxes → Disconnect makes Subik forget the code on your phone and stop reading that mailbox. Only Google can end the code itself: delete “Subik” on your Google Account’s App passwords page, or change your Google password (Google then removes all your app passwords). Either way the code stops working.
5. How we use information and why we may
| Purpose | Data | Legal basis (EU/UK users) |
|---|---|---|
| Create and secure your account | Account information, technical data | Performance of our contract with you |
| Detect and track subscriptions | Gmail data (read on your phone), subscription records, charge history, mailbox metadata | Your consent: you create the code and connect the mailbox, and you can withdraw it at any time by disconnecting or deleting the code |
| Name senders in everyone’s scans | The merchant catalog we curate, and its confirmation counts (no user identifier, no other data about you) | Our legitimate interest in accurate detection for every user |
| Learn to read more senders | The sender domains you choose to send us (no user identifier, no other data about you) | Your consent: you choose which domains to send, each time |
| Find where detection goes wrong | Totals across all users, by sender domain, of the subscriptions users dismissed or deleted (no user identifier, no other data about you) | Our legitimate interest in accurate detection for every user |
| Send reminders you asked for | Reminder settings (reminders are scheduled on your phone) | Performance of our contract; your device-level consent to notifications |
| Refresh your list in the background (Pro) | Push token, mailbox scan times, your auto-refresh setting | Performance of our contract; your device-level consent to notifications |
| Sell and honour Pro and credits | Purchase and entitlement data, scan records | Performance of our contract |
| Fix crashes and keep the service secure | Crash reports, technical data | Our legitimate interest in a reliable, secure service |
| Understand feature usage | Usage analytics | Your consent, via the in-app toggle |
| Answer support requests | Whatever you send us | Our legitimate interest in helping you |
| Comply with law | As required | Legal obligation |
We do not use your data for automated decisions with legal or similarly significant effects, and we never sell personal data.
6. Who we share data with
We share data only with the service providers that run Subik, under contracts that limit them to processing on our instructions:
| Provider | Role | Location |
|---|---|---|
| Supabase | Database, authentication and server functions — no mail credentials | Frankfurt, Germany (EU) |
| Google Sign-In; Gmail, which the app on your phone reads with the code you created | Global | |
| Apple | Sign in with Apple; App Store billing; push notifications (APNs) | Global |
| Google Play | Android billing; push notifications (FCM) | Global |
| RevenueCat | Purchase validation and entitlements | United States |
| Expo (EAS) | Push-notification delivery relay; app updates | United States |
| Sentry | Crash and error reporting | European Union |
| PostHog | Product analytics (if enabled) | European Union |
| Cloudflare | Hosting of this website and our support email routing | Global |
Gmail data is processed on your phone; only the list in section 3.2 reaches Supabase; none of it goes to RevenueCat, Expo, Sentry, PostHog or Cloudflare.
We may also disclose data if required by law, to enforce our Terms, to protect the rights and safety of users, or as part of a merger or acquisition — and in that last case, only after telling you and, for Gmail data, only with your explicit prior consent.
7. International transfers
Your account data and subscription records are stored in the EU. Some providers above operate in the United States or globally; where personal data leaves the EU, UK or Israel, we rely on the providers’ standard contractual clauses, the EU–US Data Privacy Framework where the provider is certified, or an adequacy decision (the EU recognises Israel as providing adequate protection).
8. How long we keep data
- Account, subscriptions and charge history, mailbox metadata, scan records: for as long as your account exists. Deleting your account (section 10) removes them immediately; encrypted database backups are overwritten within 30 days.
- Gmail message content: not retained anywhere — read in your phone’s memory during a scan and discarded when it ends.
- On your phone — the code and scan bookkeeping: until you disconnect that mailbox or delete your account. Signing out keeps them on the phone, tied to your Subik account, so signing back in needs no new code and another account on the same phone cannot read them. Deleting the app removes them on Android; an iPhone can keep the code in its Keychain after the app is deleted, so disconnect the mailbox first, or delete “Subik” in App passwords.
- Disconnected mailbox: the code and that mailbox’s bookkeeping are deleted from the phone at once, and the mailbox is removed from your account; your other phones delete their copy of the code the next time Subik opens on them. The code itself stays valid at Google until you delete “Subik” in App passwords or change your Google password. Subscriptions already detected stay in your account until you delete them.
- Merchant catalog confirmation counts: kept after you delete your account — they are not linked to you.
- Sender domains you chose to send us: kept after you delete your account — they are not linked to you.
- Crash reports: 90 days.
- Usage analytics: no longer than 12 months.
- Purchase records: kept by Apple, Google and RevenueCat for as long as required to honour refunds, disputes and accounting law.
- Support emails: up to 24 months after the conversation ends.
9. Security
All traffic is encrypted in transit (TLS), including the app’s connection to Gmail. Data on our servers is encrypted at rest. Every database table is protected by row-level security so that your rows can only be read by you. The code stays on your phone in its secure storage and is used only to read your mailbox from the phone; the scan bookkeeping and the app’s copy of your data are kept in encrypted app storage. Our servers hold no mail credential and run no code that can reach Gmail. No system is perfectly secure; if we learn of a breach affecting you we will notify you and the relevant authorities as the law requires.
10. Your rights and choices
Wherever you live, you can:
- See and export your data — everything Subik holds about you is visible in the app; email us for a machine-readable copy.
- Correct data — edit any subscription, your name, language and currency in the app, or ask us.
- Disconnect Gmail — Settings → Privacy & Data → Connected inboxes → Disconnect. Subik forgets the code, deletes that mailbox’s bookkeeping from your phone, and removes the mailbox from your account. To end the code at Google too, delete “Subik” in App passwords.
- Turn off analytics — Settings → Privacy & Data → Share usage data.
- Delete your account — Settings → Privacy & Data → Delete Account, or follow the account-deletion instructions if you no longer have the app. Deleting in the app deletes every Gmail code and Subik’s data from that phone, and removes your account and every row that belongs to it from our servers; your other phones delete their copy the next time Subik opens on them. The codes stay valid at Google until you delete “Subik” in App passwords. A deletion we carry out by email cannot reach your phone: delete “Subik” in App passwords and delete the app yourself.
- Withdraw consent, object, or restrict processing — email us. Withdrawing consent does not affect processing that already happened.
- Complain — to your local data-protection authority. In Israel that is the Privacy Protection Authority; in the EU, the authority of your member state.
We answer requests within 30 days. We may ask you to confirm the request from the email address on your account.
11. Notice under the Israeli Protection of Privacy Law
In accordance with section 11 of the Protection of Privacy Law, 5741-1981 (as amended):
- No legal duty. You are not legally required to provide any information to Subik. Providing it — and connecting Gmail — is voluntary and depends on your consent.
- Purpose. The information is requested to operate the Subik service as described in sections 2 and 5: identifying you, detecting and tracking your subscriptions, sending reminders you ask for, processing purchases, and keeping the service secure.
- Consequences of refusal. Without an account you cannot use Subik; without connecting Gmail, automatic detection is unavailable and you can only add subscriptions manually; without notification permission you will not receive reminders.
- Recipients. The information is transferred to the service providers listed in section 6, for the purposes stated there, and otherwise only as the law requires.
- Controller and contact. The Oat Labs (Omer Attias), Israel — subik@theoatlabs.com.
- Right of access and correction. You are entitled to inspect the information held about you and to request that inaccurate, incomplete or outdated information be corrected or deleted, as set out in sections 13 and 14 of the Law. Section 10 above explains how.
12. Children
Subik is not directed to children and we do not knowingly collect data from anyone under 16. If you believe a child has created an account, contact us and we will delete it.
13. Changes to this policy
When we change how we handle Google user data or make any other material change, we will update the effective date above and tell you in the app before the change takes effect. Earlier versions are available on request.
14. Contact
The Oat Labs · Israel · subik@theoatlabs.com · subik.theoatlabs.com/support