Check it out (https://contra.com/p/6ZZkmQk2-my-smart-accounts-a-privacy-first-personal-finance-app)Check it out (https://contra.com/p/6ZZkmQk2-my-smart-accounts-a-privacy-first-personal-finance-app)
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Saad's avatar
Privacy-first in a finance app really comes down to where the numbers live. Keeping transactions on-device with SQLite or MMKV and never shipping them to a server is the clean version, the harder part is offering backup without breaking that promise, which usually means client-side encryption with a key the server never sees.
Essam's avatar
Exactly. 🔐 Local-first gives you the privacy boundary, while client-side encryption makes cloud backup possible without giving the server access to the actual financial data.
The important part is designing that boundary from the start.
Saad's avatar
Designing that boundary from the start is the whole game. Bolting client-side encryption onto an app that already assumed a trusted server is a rewrite every time, so treating it as an architecture decision up front is the right call.
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started