Privacy Policy

Depending on which parts of the app you use, finvue stores:

• Account info. Your email address and password. Supabase Auth handles both; finvue's own code never sees or stores your password.
• Financial data you enter or import. Stock, T-Bill, dividend and Endowus holdings, expenses and income, bank account balances, debts and loans, savings goals, CPF balances, salary splits.
• Receipt photos. Scanned receipts go into a private file bucket. See Security for how access is restricted.
• An avatar image, if you upload one. Unlike receipts, avatar images sit in a public bucket, since a profile picture is meant to be seen by people you connect with.
• Emails you forward or auto-forward to your personal finvue inbound address (bank, PayNow, e-commerce notifications), so they can be parsed into transactions. The raw forwarded text is kept, truncated, alongside the transaction it produced.
• Social data, only if you use friends or splits. See "Data shared with other users" below.

• finvue never asks for or stores your bank or brokerage login credentials. There is no live bank connection. You forward the notification email your bank already sends you, or use a device-local automation, and finvue parses the text.
• finvue does not execute trades, move money, or connect to any brokerage or bank API on your behalf. It is a tracker: you tell it what happened, it does the maths.
• finvue does not sell your data, and does not run advertising of any kind.

A few external services are involved in making finvue work. None of them are ad networks, and none receive more than they need to do their one job:

• Supabase. Hosts the database, authentication and file storage. Every table is protected by row-level security, so a query only ever returns rows that belong to the signed-in user.
• Resend. Sends transactional email (weekly summaries, alerts, account emails) on finvue's behalf.
• Google Gemini. Powers receipt scanning, transaction-text parsing, spending insights and the AI coach. This is the one place a meaningful slice of your financial data leaves Supabase. Scanning a receipt sends that photo. Asking the AI coach a question sends a snapshot of the figures relevant to answering it (balances, holdings, debts, goals), so it can give a grounded answer instead of a generic one.
• Public market-data sources. Yahoo Finance, exchangerate-api.com, Nasdaq, SGX and SEC EDGAR are queried for prices, FX rates, earnings dates and filings by ticker or symbol only. No account or personal data is ever sent to them.
• Vercel Analytics. Records anonymous, aggregated page-view counts in production. It doesn't use cookies and can't identify you.

finvue's social features (friends, linked debts, shared receipt splits) are entirely opt-in and only activate once you deliberately connect with someone. Once you do:

• A debt you link to a friend becomes visible to them. They see the amount, currency and description, nothing else.
• Tagging a friend in a split expense shares the full expense with them, including the merchant, amount, category, itemised breakdown and the receipt image itself, the moment they're tagged. It isn't gated on the debt being settled.

Nothing is shared with anyone until you explicitly add a friend or tag them in a split.

Your data is kept for as long as your account exists. Delete your account (Settings → Privacy & Security → Delete Account) and everything tied to it goes with it: holdings, transactions, receipts, your avatar, the account itself, gone immediately and for good. A debt you'd linked to a friend doesn't disappear from their side. It just gets unlinked, so their own record stays intact.

Both of the following are self-service, in the app, with no need to contact anyone:

• Export everything. Settings → Data lets you download your full financial history as CSV files, for any date range.
• Delete everything. Settings → Privacy & Security → Delete Account permanently removes your account and every record tied to it.

finvue uses a session cookie, set by Supabase Auth, to keep you signed in. A few preferences stay local to your browser: whether Privacy Mode is masking values, PIN lock state, which notifications you've already seen. None of that leaves your device.

This page may be updated as the app changes. The date at the top always reflects the current version.