Privacy Policy

Account details — your email address, first and last name, and a hashed form of your password (we use scrypt; we never store or see the password itself).

Financial data you upload — the transactions parsed from bank statements you import (Amex CSV, HSBC CSV, ING PDF), and everything you build on top of them: categories, budgets, rules, recurring items and tax-deductible flags.

That's the list. There are no analytics trackers, no advertising identifiers, and no data brokers involved.

We never ask for your bank login, and there is no Open Banking or screen-scraping connection — Quidbower only ever sees the statement files you choose to upload.

We never sell your data, share it for marketing, or use it for anything other than showing you your own finances.

Categorisation — if you use the optional “Categorise with AI” feature, the merchant name and a sample transaction description (for example, “UBER *EATS SYDNEY”) are sent to Anthropic's Claude API to suggest a category. Amounts, balances, dates and your identity are not sent. Each merchant is looked up at most once — the answer is cached as a rule so the model is never re-run for a known merchant.

Ask— when you ask a question on the Ask page, your question plus aggregated figures (monthly totals, per-category totals and recurring-charge summaries) are sent to Anthropic's Claude API to write the answer. Raw transactions and your identity are never sent, and all dollar figures in answers are computed by Quidbower itself, not the model. If you never use these features, nothing is ever sent.

Import mapping— when importing an unrecognised bank format, you can optionally click “Suggest with AI”, which sends the file's column names and a few sample rows to Anthropic's Claude API to propose the column mapping. This never happens automatically, and the resulting mapping is saved on your account so it doesn't need to be asked again.

Your own API key — if you add a personal Anthropic key for unlimited questions, it is stored encrypted (AES-256-GCM), used only to answer your questions, never displayed again, and deletable in Settings at any time.

One cookie: an httpOnly session cookie (mfa_session) that keeps you signed in for up to 30 days. There are no tracking or third-party cookies.

Your data is stored in a Postgres database, isolated per account — other users can never see your transactions. When Quidbower is hosted publicly, the database and application run on managed infrastructure providers (currently planned: Vercel and Neon), who process the data solely to run the service.

You can delete individual transactions, rules, budgets and imports in the app at any time. Deleting your account removes everything associated with it — transactions, rules, budgets, imports and sessions — immediately and permanently. Until self-serve account deletion ships in Settings, email us and we'll do it within 7 days.

You can ask for a copy of your data, ask us to correct it, or ask us to delete it — email privacy@quidbower.com. We aim to respond within 7 days. If this policy changes in a way that matters, the change will be noted here with a new “last updated” date before it takes effect.