Security
How Nummo keeps your money data safe: no bank login, encrypted connections, the most personal fields encrypted with a key kept apart from the database, and data deleted on a schedule.
Last updated 8 November 2026. What this page says is what the code does. If something here stops being true, we change the page. Questions or a problem to report: hello@getnummo.com.
What we never have
- Your bank login, card numbers or UPI PIN. Nummo never asks for them.
- Your email password. When you connect Gmail or Outlook, the connection is held by One (withone.ai); we keep only a reference to it, and our access through it can only read.
- The emails themselves. We read receipts, bills and renewals, keep what we read in each one (shop, amount, date, items) and not the email.
Where your data lives
In a Postgres database run by Supabase, on AWS in the United States (Virginia), used by our server on Fly.io in the same region.
- Encrypted in transit. The app talks to our server over HTTPS. Our server talks to the database over TLS and checks the database's certificate against Supabase's own root certificate, so the connection can't be quietly redirected.
- Encrypted on disk. Supabase encrypts all data at rest with AES-256.
- Closed to the outside. Supabase offers a public API onto every database; ours has row-level security switched on for every table with no rules that let anyone in, so that API returns nothing.
The most personal parts, encrypted by us as well
Disk encryption protects against a stolen disk. It doesn't help if someone gets a copy of the database itself, for example through a leaked password. So Nummo encrypts these fields itself before they are stored, with AES-256-GCM and a key kept on our server, apart from the database:
- Notes on your spends, and the items on a receipt
- Payment references (UPI and bank reference numbers) and the last four digits of a card or account
- Your take-home pay
- Questions you ask the Advisor, and its answers
- The activity log of shared spaces (who added or moved what)
- Bank texts we keep, and what we read in each one
- What we read from each email, and a spreadsheet's rows while you import it
A copy of the database shows these only as scrambled text. If the key were ever replaced with a wrong one, the server refuses to start rather than write anything with it.
What isn't encrypted this way, and why: amounts, dates, shop names and categories. The server adds these up all day (your daily number, budgets, subscriptions), and doing that inside the database keeps the app fast. They are still encrypted on disk and closed off as above.
Who can see your data
Your data is shown to you, and to the people in a shared space only what you share with it. Our server decrypts the encrypted fields when it needs them: to show them to you, and to run what you've switched on, like the morning inbox scan and the Advisor. Nobody at Nummo reads your data, except with your permission to fix a problem you report, for security, or where the law requires. We don't sell it or use it for ads. The services that process it for us are listed in the Privacy Policy; Anthropic, which reads emails and answers the Advisor, does not train its models on it.
Kept only as long as it's needed
A job runs every day and deletes:
- bank texts after 30 days, and the text itself as soon as it becomes a spend
- Advisor questions and answers after 30 days
- what was read from each email after 90 days (the spend it became stays)
- a spreadsheet import you didn't save after a day, and a saved import's undo after 30 days
You stay in control
- Disconnect your inbox in Settings › Privacy. The connection is removed, and the spends already found stay.
- Take your data with you as an Excel workbook from Settings › Export (Pro).
- Delete your account in Settings. Everything goes straight away, and the database host's backup copies within 30 days (how).
- Turn AI features off in Settings › Privacy, and nothing of yours is sent to an AI service.
Found a problem?
Write to hello@getnummo.com with what you found. We'll reply, fix it, and say when it's fixed.