“We encrypt your data” is almost free: HTTPS is encryption too, even if your spending history sits in plain text on a server. Of our 2,298 finance apps, 49 mention “encryption” in descriptions; 16 claim explicit end-to-end encryption — under one percent. “There is encryption” is marketing; “only you hold the key” is architecture.
Three levels of protection
- TLS (in transit). Data is encrypted only in transit — that stops interception on public Wi-Fi, but both ends stay plain text.
- Server-side encryption (at rest). The database is encrypted on disk — safe from a stolen drive, but the key belongs to the service, often automatically. A hacked account, an insider, or a government request makes it readable. 1,863 of the 2,298 catalog apps store data in the developer’s cloud — most work this way.
- End-to-end (E2EE). The key is generated on your device and never leaves it; the server gets only ciphertext. A breach yields bytes, not your spending history.
AES-256 is used at all three levels. The only question separating marketing from privacy: who holds the key. Without it, “256-bit encryption” describes an algorithm, not an access model.
Zero knowledge vs password recovery
“Zero knowledge” means the server stores ciphertext and holds nothing sufficient to decrypt it. Hard consequence: if a service restores access via e-mail, SMS, or a “security question” without data loss, it keeps the key — or a wrapper — on its side. Lossless recovery and end-to-end encryption are mathematically incompatible — exactly one of the two is true.
In real E2E systems, a forgotten passphrase means lost data — by design. Ask support: “I forgot my password — what can you recover?” “We’ll reset it, data stays intact” is more honest than any landing page. From the catalog: Recap, a crypto tax calculator — encryption happens on the device, keys belong to the user, though data is stored in the service’s cloud.
How to tell real E2E from marketing
Whitepaper
A real scheme is described in detail: where the key is generated, what encrypts the data, what the server sees during sync, what happens when a device is added. Such whitepapers are rare — onbalance, an offline-first private finance app, has its whitepaper on the website. A verifiable promise, not a padlock on a logo.
Open source
Actual Budget (MIT) encrypts budget sync end-to-end; the code is open — read the scheme, run your own sync server. rotki (AGPL-3.0) stores a crypto portfolio locally, encrypted. Open code shows the opposite too: Budget Zen honestly did e2e, but development stopped in February 2025, the repository archived — check whether the project is alive.
Audits: who, when, what
An independent audit is worth three details: the firm’s name, the date, the full published report with its problems. One from three years ago says nothing about the current version; “protected to audit standards” without a report is an empty press-release line.
Local storage: no data, nothing to leak
201 of the 2,298 apps are marked local: the database lives on the device, and there is physically nothing for a server to decrypt or leak. The extreme form of privacy isn’t “encrypted data” but “no data”:
- Vento keeps all records in SQLite on the phone, with no bank connections and no ads;
- Subtle stores data on the device and syncs through the user’s own encrypted iCloud — a cloud exists in the scheme, but not the developer’s;
- Rebills is an offline subscription tracker with no accounts at all.
Without bank connections the logic is the same: an offline-first app like onbalance keeps transactions on the device, passes nothing to third parties, and syncs between your devices end-to-end. First “nothing to encrypt,” then “we encrypt what we send.”
The trade-offs
E2EE shifts part of the server’s job onto you:
- A lost passphrase. Forget the key — the data is gone, and support is powerless by design. Store the phrase outside your phone (password manager, paper in a safe) from day one.
- Sync. The key must reach every new device — by phrase, QR code, or file. Each is an attack surface; a phrase messaged to yourself counts as handed over already.
- Shared access. A shared budget means dividing the key. Before enabling it, check whether you can revoke a member’s access, and what happens to their copy.
- Export still matters. E2EE protects against prying eyes, not a service shutting down: without an export you stay bound to someone else’s business plan.
The five-minute checklist
- Search the developer’s site for “security,” “whitepaper,” “encryption”: a detailed document is good; a slogan is a red flag.
- Ask support: “I forgot my password — what will you recover?” “Everything, lossless” means no end-to-end encryption.
- Turn on airplane mode and open the app — if it works, the data is local.
- Google login instead of a passphrase means the key isn’t yours alone.
- For open source, check the repository: license, last commit, “encrypt” in issues.
- An audit must be public, dated, and complete.
- Find the CSV or database export in settings. No export — you’re building a dependency no encryption will save.
“There is encryption” answers the algorithm question; “only you have the key” answers the trust question. One password-recovery question tells them apart better than any store description.