Privacy Policy
1. Who we are
"Pockets by Hoopy" ("we," "us," "the app") is operated by the developer of Pockets by Hoopy. For any privacy question or request, contact us at support@byhoopy.com.
2. Information we collect
Account information
- When you sign up with email: your name, email address, and a password (stored only as a secure hash by our authentication provider — we never see or store your plaintext password).
- When you sign in with Google: your name, email address, and profile picture, as provided by Google. We use this only to create or access your account. We request no other Google data and access nothing in your Google account beyond basic sign-in profile information.
Financial information (once you connect a bank)
Pockets is built around your bank data — connecting an account is how the app works, and most of its features depend on it. We only receive the data below once you connect a bank; if you never connect one, we never receive it. When you do, our bank-data provider (Plaid — see below) share with us:
- Account details: account name, type, masked account number, and balances.
- Transaction data: amounts, dates, merchant/description text, pending or posted status, and category information supplied by the provider.
We do not receive or store your online-banking username or password. Bank connections are handled by the provider; we store only an encrypted access token that lets us fetch the data above.
Information you enter yourself
- Pockets, budgets, funding schedules, categories, goals, and any manual transactions or notes you add.
- App preferences (sort order, theme, notification settings).
Bank notifications (only if you turn this on)
- Android app: Notification access is off until you turn it on in your phone's settings. With it on, the app reads your notifications on your phone. By default it looks at every app's notifications and keeps only those with an amount of money in them; you can instead limit it to apps you choose. Notifications with no amount in them are ignored and never leave your phone. When a notification is a charge it can read, it sends the amount, merchant, card or account digits, and the notification text, to create the transaction. When a notification contains an amount it can't read, it sends that notification's text, the app's name and its title, so you can show Pockets how to read it, or tell it to ignore that kind of notification. This can include notifications from apps that are not banks, such as a shopping app's sale price; choose specific apps if you'd rather that didn't happen.
- Teaching Pockets a new bank (Android): when you choose to, the app lists the notifications currently on your phone so you can pick one. Only the one you pick is used, and what is saved is the reading rule built from it, not the notification itself.
- The Android app keeps a short log of notifications from bank apps Pockets knows, on your phone only, to help fix reading problems. It is never sent anywhere.
- iPhone Automation: the Shortcut you set up sends the text of the notifications it is set up to send, the app's name and the notification title, for the same two purposes. The same applies to an automation app you set up on Android, such as MacroDroid.
- Notification text we couldn't read is kept until you teach Pockets to read it or dismiss it.
Technical information
- If you enable notifications, a push-notification token for your device.
- Basic operational logs (timestamps, error diagnostics) needed to run and secure the service. We do not use third-party advertising or cross-site tracking cookies.
3. How we use your information
- To provide the core service: calculating your Good to Go number, forecasting, and budgeting across your pockets.
- To categorize and clean up your transactions (see the next section on automated processing).
- To sync your accounts and, where you ask, refresh balances.
- To send you account and service emails, and any notifications you enable.
- To keep the service secure, debug problems, and prevent abuse.
4. Automated transaction categorization (AI processing)
SQ *AL'S FRENCH FRYS 0421) into a clean merchant name and
category, we send transaction description text and amounts to a
third-party AI language-model provider that performs this parsing on our
behalf. This helps your transactions show up with readable names and
sensible categories.
- We send only what's needed to identify the merchant — the transaction's description text and amount. We do not send your name, email, account numbers, or balances.
- We use the results to build a shared library of merchant-name rules, so common merchants are recognized in the future without sending anything to the AI provider again.
- This parsing is performed by our AI provider, Anthropic, under their commercial API terms. We don't control Anthropic's internal data practices, so rather than make promises on their behalf we point you to their own Privacy Policy. On our side: we send only the minimum described above, we never tie it to advertising, and we never sell it.
Receipt scanning (Premium)
If you choose to add or itemize a transaction from a photo of a receipt, we send the receipt to Anthropic for the same kind of AI parsing described above. Your device crops the photo to the receipt itself and cuts a long receipt into a few overlapping pieces, so the print stays sharp enough to read; those pieces are what is sent. Nothing is read off the photo on your device. The AI's reading is what fills the transaction in, and it happens on every receipt you scan.
You can also upload a PDF receipt — an emailed order confirmation or invoice, for example. A PDF is not cropped: the whole file is sent to Anthropic as it is, and everything in it, including any page or detail you weren't thinking about, goes with it. Check what is in a PDF before you upload it. As with a photo, we do not store it.
- When you scan a receipt the app asks where it is — your gallery, a file, or your camera. Choosing the camera opens your device's own camera app, not something inside Pockets: we never see a live preview, and nothing is recorded. Only the one photo you take, or the one file you pick, is read, and only as described here.
- A receipt can contain more than a bank description does: every line item, the store's address, the last four digits of a card, and anything else in frame or on the page. Crop or cover what you don't want read before you take the photo — everything in the picture, or in the PDF, may be sent.
- We do not store the photo or the PDF. It is read, used to fill in the transaction for you to confirm, and discarded — we never write it to our database, our logs or any file store. What we keep is the transaction and item list you save. For what Anthropic does with it on their side, the same caveat as above applies: we point you to their Privacy Policy rather than make promises on their behalf.
- Receipt scanning is a Premium feature and each scan that reaches the AI provider is counted, so you can see how often it was used.
5. Who we share data with
We share data only with the service providers ("subprocessors") that make the app work. Each receives only what it needs to perform its function.
| Provider | Purpose | Data involved |
|---|---|---|
| Supabase | Database, authentication, and file storage | Your account, budgeting, and transaction data |
| Plaid | Bank account connections | Bank account & transaction data (if you connect a bank) |
| "Sign in with Google" authentication | Your name, email, profile picture (only if you use it) | |
| Anthropic (AI provider) | Merchant-name & category parsing; receipt reading (Premium, only when you scan a receipt) | Transaction description text and amounts; for a receipt you scan, the photo (cropped to the receipt) or PDF (not stored) |
| Resend | Sending account & service emails | Your email address |
| Railway & Vercel | Application hosting | Data in transit while the app runs |
We do not sell your personal information, and we do not share it with data brokers or advertisers. We may disclose information if required by law, or to protect the rights, safety, and security of our users and the service.
6. Google user data
Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. We use Google sign-in data only to authenticate you and provide the app's features to you directly — we do not transfer or use it for advertising, and humans do not read it except as needed for security or to comply with the law.
7. Data retention and deletion
- We keep your data for as long as your account is active.
- You can disconnect a bank at any time from within the app; doing so revokes our access token with the provider and removes the associated local account data.
- You can delete your entire account from within the app. This revokes all bank-provider tokens and deletes your personal data from our systems. Some records may persist briefly in backups or logs before being overwritten in the ordinary course.
- To request deletion by email, contact support@byhoopy.com.
8. How we protect your data
- Data is transmitted over encrypted connections (HTTPS/TLS).
- Bank access tokens are encrypted at rest.
- We never receive your full card or bank-account numbers — they arrive already masked, so we only ever see the last few digits.
- Every user's data is isolated by row-level security so one account cannot read another's data.
- Only the minimum server code paths hold elevated database privileges, and we access your data only to operate, support, and debug the service — never to browse it out of curiosity.
No system is perfectly secure, but we take reasonable, industry-standard measures to protect your information.
9. Your rights and choices
- Access & correction: most of your data is visible and editable directly in the app.
- Deletion: delete your account in-app or by email.
- Bank connections: you choose which banks to connect, and you can disconnect any of them at any time.
- Notifications: opt in or out in the app or your device settings.
- Depending on where you live (for example, the EEA, UK, or California), you may have additional rights to access, port, or restrict processing of your data. Contact us to exercise them.
10. Children and family use
Pockets by Hoopy is not directed to children under 13 (or the minimum age required in your country), and we do not knowingly collect their personal information without verifiable parental consent.
We recognize that budgeting is a valuable skill to learn early. A parent or legal guardian may create and supervise an account on behalf of a minor in their household. By doing so, the parent or guardian consents to our collection and use of that account's information as described in this policy and takes responsibility for the minor's use of the app. If you believe a child has provided us information without this parental involvement, contact us at support@byhoopy.com and we will delete it.
11. Changes to this policy
We may update this policy as the app evolves. When we make material changes, we will update the "Last updated" date above and, where appropriate, notify you in the app. Your continued use after an update means you accept the revised policy.
12. Contact us
Questions, requests, or concerns? Email support@byhoopy.com and we'll get back to you.