Security you can verify, not just trust.
The safest place for your financial data is the phone in your pocket. Here’s exactly how WealthWise keeps it there.
On your device, by default
Your transactions live in a local database on your phone. There is no table on any server with your spending in it — not encrypted-at-rest on our infrastructure, not there at all. The smallest attack surface is the one that doesn’t exist.
No bank credentials, ever
No bank login, no Plaid, no screen-scraping, and nowhere in the app to hand over a credential. WealthWise reads the transaction SMS your bank already sends you, on your device — or imports a statement file (CSV, OFX, QIF). Nothing is fetched, nothing is forwarded.
AES-256-GCM backups
Backups are encrypted with AES-256-GCM before they ever leave the app, and that’s in the free tier. The backup file is opaque without your key — losing your phone means restoring, not exposure.
Your cloud, your key
Pro’s optional Cloud Sync writes to your own iCloud Drive or Google Drive, under your account and your quota. We never hold the file and can’t read it: the encryption key never leaves your device, so sync is end-to-end by construction.
Intelligence that never phones home
The insights are on-device, rule-based and deterministic — they run with airplane mode on. No cloud model, no API call, no prompt with your salary sitting in an inference log. The same input always produces the same result, and you can see the reasoning.
Nothing destroyed by a wrong tap
Deleting is soft everywhere — transactions, budgets, categories, debts, goals, recurring rules, even alerts — and everything sits in a 30-day Trash. There is no screen where a mistake is permanent.
We have never held a copy of your transactions. If someone demanded your spending history, we could not produce it — there is nothing to hand over.
Found something? Tell us.
If you believe you’ve found a security issue, we want to hear about it before anyone else does. Email sumesphere@gmail.com with the details and steps to reproduce, and please give us a reasonable window to fix it before disclosing publicly.
For the full data-handling story, see the privacy overview and the Privacy Policy.