Privacy Policy
Last updated: 6 September 2026
FiscalFox (“FiscalFox”, “we”, “us”) is a personal spending-ledger tool operated by an individual developer based in India. This policy explains what data FiscalFox handles, why, and the choices you have. It is written to be read, not to be hidden behind legalese. If anything here is unclear, email pratiknayak2710@gmail.com.
1. What FiscalFox does
Indian banks email you a transaction alert for most UPI payments and card transactions. FiscalFox reads those alert emails from your Gmail (with your explicit permission), extracts the amount, merchant, date, and payment method, and presents them as a single searchable ledger. FiscalFox does not connect to your bank, does not use your banking credentials, and does not aggregate accounts.
2. Data we collect
2.1 Account identity (from Google Sign-In)
- Your Google account's name, email address, and profile picture URL.
This is used only to create your account, authenticate you, and email you (for example, a waitlist-invite notice). Signing in does not grant FiscalFox access to your email.
2.2 Gmail data (only if you connect Gmail)
Connecting Gmail is a separate, explicit consent step. FiscalFox requests exactly one scope: https://www.googleapis.com/auth/gmail.readonly — read-only access. FiscalFox cannot send, delete, label, or modify anything in your mailbox.
- What we access: only messages returned by a bank-transaction search (known bank sender domains, plus transaction phrases such as “debited”, “credited”, “spent on”). We do not read, scan, or index the rest of your inbox.
- What we extract: transaction amount, merchant/payee name, date and time, direction (debit/credit), and payment method.
- What we store: the extracted transactions, and the raw text of each matched alert email (encrypted — see section 5) so a parsing error can be fixed without re-reading your mailbox.
2.3 Operational data
- Timestamps of your syncs and a “watermark” marking the newest email already processed, so repeat syncs are fast.
- Standard server logs from our hosting provider (Google Cloud). We deliberately keep raw email content, OAuth tokens, and authorization codes out of application logs.
3. How we use your data
We use the data above solely to:
- build and display your transaction ledger;
- authenticate you and keep your account working;
- improve the accuracy of the parser (using your own emails, for your own ledger — see the Limited Use note below);
- contact you about your account or the service.
We do not use your data for advertising, profiling for third parties, or any purpose you have not seen described here.
3a. Optional AI categorisation
When the parser cannot identify a merchant, you can ask FiscalFox to categorise it with Google's Gemini API — either by turning on “Auto-categorise unclear merchants” (off by default) or by running the “Re-attribute” action manually. When you do:
- the only data sent to the Gemini API is the raw merchant / counterparty text as it appeared in the bank alert (with any long digit sequences removed), the payment method, and a coarse amount range (e.g. “₹500–2k”);
- your email content, your name, your account or card numbers, and exact amounts are never sent;
- requests go to Google's Gemini API and are subject to the Gemini API Additional Terms; on the paid tier Google does not use the input to train its models, on the free tier it may;
- an AI-assigned merchant or category is marked with a ✨ and is always overridden by any correction you make yourself.
If you never enable it and never run it, no transaction data is sent to the Gemini API.
4. Google API Limited Use disclosure
FiscalFox'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. Specifically:
- we use Gmail data only to provide and improve the user-facing feature you requested (your ledger);
- we do not transfer Gmail data to others except as needed to provide that feature, for security, or to comply with law;
- we do not use Gmail data for advertising;
- we do not allow humans to read Gmail data unless (a) you give explicit consent for a specific message (e.g. to debug a mis-parsed transaction), (b) it is necessary for security or abuse investigation, or (c) the law requires it;
- we do not use Gmail data to develop, train, or improve generalized/AI/ML models.
5. How your data is stored and secured
- Data is stored in Google Cloud / Firebase in the
asia-south1(Mumbai) region. - Your Gmail refresh token and every raw alert email are protected with envelope encryption: each record gets a unique data key, encrypted (“wrapped”) by a key held in Google Cloud KMS that FiscalFox cannot export. A database dump alone cannot be decrypted; decrypting requires a separate KMS permission, and every decryption is recorded in Cloud Audit Logs.
- Access to our database and functions is governed by deny-by-default security rules; the browser can only ever read your own transactions and profile.
- Every request from the app is verified with Google App Check (reCAPTCHA Enterprise) and your Firebase authentication.
No system is perfectly secure. FiscalFox is an early-access product; do not treat it as your system of record.
6. How long we keep it
- Transactions and account data: until you delete your account.
- Raw alert emails: retained (encrypted) to support re-parsing, and are being moved onto a scheduled deletion window. They are deleted immediately when you delete your account.
- OAuth tokens: deleted when you disconnect Gmail or delete your account.
7. Sharing and sub-processors
We do not sell your data and we do not share it with third parties for their own purposes. FiscalFox runs on Google Cloud Platform / Firebase, which processes and stores data on our behalf. If you turn on optional AI categorisation (section 3a), the limited fields described there are also processed by the Google Gemini API. We may disclose data if required by valid legal process, or to protect the rights and safety of users.
8. Your choices and rights
- See your data: your dashboard is your data — every transaction we hold is shown there.
- Disconnect Gmail: stops all future email access and deletes the stored token.
- Delete everything: the “Delete my account and all data” button permanently erases your transactions and raw emails and revokes FiscalFox's Gmail access at Google.
- Revoke at Google directly: any time, at myaccount.google.com/permissions.
- Questions or requests: email pratiknayak2710@gmail.com and we'll respond within a reasonable time.
9. Children
FiscalFox is not directed to anyone under 18 and we do not knowingly collect their data.
10. Changes to this policy
If we make a material change, we'll update the date above and, where appropriate, notify you by email. Continued use after a change means you accept the updated policy.
11. Contact
FiscalFox · pratiknayak2710@gmail.com