Why (Not) Build Yet Another Finance App — Part 6: Privacy and Security
Security in a finance app looks like a checklist item: the padlock in the browser, hashed passwords, sign in with Google and Apple.
In our heads, it was just using HTTPS.
This is Part 6 of the diary we started in Part 0. In Part 0, we wrote that a bank statement says more about someone's life than any diary. Where they live, who they share bills with, how much they earn, what medicine they buy. All of it passes through Snabber. This part is about how we take care of it.
Quick context: Snabber reads bank data through Open Finance, read-only. It does not make transfers or payments. The data lives in a cloud database, and Snabber itself needs to read it to categorize, build reports and answer the AI.
What we thought it was
- HTTPS everywhere
- Hashed passwords
- Sign in with Google and Apple
What it really was
Encrypting is easy. Living with encryption is not.
Every transaction's description and amount are encrypted in the database with AES-256. Anyone with access to the database would see only scrambled text. That is the easy part.
The hard part comes after, because a database that cannot read what it stores cannot search for anything either:
- Duplicates. To know whether the bank sent the same purchase twice, we store a fingerprint (a hash) of the description and amount. It can only answer "is it equal?". A time difference between two versions of the same purchase is enough for it to miss the match.
- Text search. "How much did I spend on transactions containing 'pharmacy'?" cannot be asked of the database. The search runs in memory, after decrypting the period.
- Categorization. In Part 3, we explained that matching a transfer to the same person's history means decrypting up to 3,000 transactions per sync.
Every feature that needs to "read" the description pays this price. We think it is worth it.
Encrypted in transit and at rest
Data travels encrypted: between your phone, Snabber and the bank, everything goes over HTTPS. And it stays encrypted when stored, with AES-256. It is only decrypted on the server, at the moment a feature needs it: categorizing a purchase, building a report, answering a question for the AI.
That is different from end-to-end encryption, where not even the server can read the data. No app that categorizes your statement works that way, because categorizing means reading. So, on the site and in ads, we describe exactly what we do, without overstating it. We would rather promise only what we can deliver.
Not even our own queries see your data
Many of the numbers in this series came from queries against production. They use a separate, read-only access, locked down in the database itself. It cannot see descriptions, amounts, emails, names, phone numbers or documents. Those columns simply do not exist for it.
Granting a new column to that access is an explicit decision, one at a time, and personal data never gets in. That is why this series talks about numbers of transactions and almost never about amounts. The few amounts that appear came from somewhere else: the refund of Snabber's own subscription, which we know from the payment system, or one of our own cards.
Privacy is not a layer. It is a price every feature pays.
Fear of scams has a number
In October, 70% of people who opened the bank connection on their phone gave up before finishing. On a computer, 30%. Our hypothesis: on a phone, the person leaves Snabber, goes to their bank's app and sees an authorization request in the name of a company they have never heard of (the partner that bridges us to the banks). For someone who keeps getting scam messages, that looks like a scam.
On October 13, we started showing four points before opening the connection:
- 1Snabber never sees your password. With Open Finance banks, you authorize in your bank's app.
- 2Read-only. Snabber does not make transfers or payments.
- 3Central Bank Open Finance. You can cancel any time, in Snabber or in your bank's app.
- 4Encrypted data. Descriptions and amounts stored with AES-256.
And, right before the connection, one line explaining that the request will appear in the partner's name, not Snabber's.
Each point was written to be true for every connection, not just most of them. A security notice that only holds some of the time is not a notice. It is marketing.
Anyone can say they are ChatGPT
Snabber talks to AI assistants like ChatGPT and Claude through the MCP protocol. For that, the assistant registers itself with Snabber and asks you to authorize it. That registration is open by the protocol's design, so any app could use the name "ChatGPT".
That is why the name proves nothing. The authorization screen looks at where access will be delivered, not at the name. If the destination belongs to one of the known AIs, it shows as verified. If not, the person has to confirm the destination address before allowing it, and the app warns when the name imitates a known app. Registration also has a rate limit.
The audit we asked for
In August, we ran an internal security review of the whole codebase: 280 API routes, the libraries and the server configuration. It confirmed what was right (queries protected against injection, passwords with bcrypt, no secrets in the repository) and pointed out what could be improved.
The issues it raised were fixed in order of priority. The project's libraries were updated too, with no critical alerts in the latest review, in November.
Your data, your call
In the "My data" area, you can download your data or ask for it to be deleted, without emailing anyone. When you remove a bank connection, you choose between removing just the connection or also deleting what came from it.
Deleting your account works space by space: connections, transactions, accounts, bills and investments in each of your spaces (Part 5 covers what happens in spaces shared with other people).
Some security and privacy commits, August to November 2026. LGPD is Brazil's data protection law; "dicas de segurança ao conectar banco" means "security tips when connecting a bank".
What we did
- ✓Descriptions and amounts encrypted, with hashes only where an exact match is needed.
- ✓A production diagnostics access that cannot see personal data.
- ✓Four security points before connecting a bank, in plain language.
- ✓AI authorization that checks the destination, not the name.
- ✓An internal audit of the whole codebase, with the fixes applied.
- ✓Download or delete your data from the "My data" area.
What we still haven't solved
The fear of scams went down, but it did not go away. Even with the four points, almost half of the people who open the connection on iPhone still do not finish. Explaining Open Finance to someone who has never heard of it is work that does not end on one screen.
Anyone who connects Snabber to ChatGPT or Claude chooses to share data with that AI, under their own account and that company's rules. Making that clear without scaring people is still a work in progress.
And security is a list that never ends. With every new feature, the question "who can see this?" starts over.
If you are going to keep someone's bank statement
Encrypt from day one, and accept that every search will get more expensive. Migrating later costs far more.
Also write down what you do not promise, and deliver the rest. And set up a diagnostics access that cannot see personal data before you investigate your first production bug.
Want to see how it works? Create your Snabber account and connect your bank through Open Finance, read-only.
In the last part: after all this, is it worth it?
