Privacy Policy

What is collected

Depending on how you use the app:

• Your name and email, when you create an account.
• Bank statements you upload (PDF, CSV or XLSX) and the transactions, dates, amounts and merchant descriptions extracted from them.
• If you connect Gmail: read-only access to your inbox, scoped specifically to finding and reading bank-sender emails, plus your Google account email address. FinPlanner never gets permission to send mail, delete mail, or read anything outside what that scope allows.
• Budgets, goals, category overrides, your declared rent, and your account balance, when you set them.
• A statement’s password, if a PDF you upload needs one — stored encrypted, used only to open that file.
• Basic activity logs (what changed and when) used for troubleshooting, not for tracking you.
• Payment records if you buy Pro — see below, since most of this never reaches FinPlanner at all.

Where it’s stored

In a Supabase project hosted in AWS’s Mumbai region (ap-south-1), access controlled row-by-row so your account can only ever read or write your own data. That access control is enforced by the database itself, not just by the app’s code.

Who it’s shared with, and exactly why

Nothing here is sold, and nothing here is shared for advertising. What does leave the app:

• Google Gemini — only when a statement’s format isn’t recognised by the built-in parser. That file is sent to Gemini once, to extract the transactions, and for no other purpose.
• Groq — only when you use the chat assistant. A snapshot of your relevant financial data (recent transactions, budget, goals) is sent along with your message so it can answer about your actual numbers.
• Google — if you connect Gmail, to authenticate the connection and let FinPlanner read matching emails under the read-only scope above.
• Razorpay — if you buy Pro. Your card, UPI or other payment details go directly to Razorpay; FinPlanner never sees or stores them, only the payment’s success/failure result and Razorpay’s own payment ID.
• Resend — to send the emails FinPlanner sends: budget/goal digests, and replies to messages sent through the contact form.
• Sentry — technical error reports (what failed and the surrounding code context) when something breaks, so it can be fixed. Not your financial data.

Cookies and tracking

FinPlanner uses one cookie, set by Supabase, to keep you signed in. There is no advertising tracker, no analytics pixel, and no third-party script watching what you do in the app.

How long data is kept

For as long as your account exists, or until you ask for it to be deleted — there is no automatic expiry on your transactions or statements today.

Your rights over your data

You can see and edit most of what FinPlanner holds about you directly in the app — transactions, budgets, goals, your declared rent, your Gmail connection. Deleting the account itself isn’t yet a button in the app; it’s something I do by hand when you ask, and I’d rather say that plainly than pretend a self-serve option exists that doesn’t. Ask here for a copy of your data or to have it deleted, and I’ll act on it directly — that request reaches me personally, not a support queue.

Security

Traffic to the app is encrypted (HTTPS). Statement passwords are encrypted at rest. Database access is scoped per-user at the database layer, not only checked in application code, so a bug in one screen can’t expose another user’s data through it.

Children

FinPlanner isn’t directed at children, and isn’t knowingly used by anyone under 18.

Changes to this policy

If what’s collected or who it’s shared with changes, I’ll update the date at the top of this page and this list, not just the small print.

Questions, access, deletion

All of it goes through the contact page. If you believe something here is wrong or incomplete, tell me and I’ll fix it.