I built a privacy-first net worth tracker — no account, no Plaid, data never leaves your browser
Hey IH 👋
I shipped Vaulted — a free, open-source net worth tracker where your financial data never leaves your browser.
The problem
Every net worth tracker wants your bank login. Mint did. Monarch does. Copilot does. They all pipe your data through Plaid or Yodlee. If you just want to answer "am I richer than last month?" without handing over credentials, your options are basically spreadsheets.
What I built
A static PWA (Next.js) that runs entirely in your browser:
- No account, no email, no phone number — open it and start
- No bank login — you enter balances manually (2 min/month)
- No server — data lives in IndexedDB + localStorage
- Works offline — PWA with service worker
- Multi-currency — USD, EUR, GBP, BRL, etc.
- JSON export/import for backups
- Open source — verify every privacy claim yourself
Stack
Next.js static export → GitHub Pages. Zero ongoing server cost.
Links
🔗 Live: vaultedworth.com
📦 Source: github.com/douglascorrea/vaulted
What I'd love feedback on
- Does the privacy angle resonate, or is it too niche?
- Any features that would make you actually use this monthly?
- Would you pay for encrypted cloud backup (optional, opt-in)?
Building in public. Happy to share numbers as they come in.
The privacy angle resonates — but I'd argue it's not niche at all. The people who care most about financial privacy are exactly the people with enough assets to need a net worth tracker. You're not appealing to a small paranoid minority, you're appealing to the core user who has something worth protecting.
The "2 min/month" framing is smart and underused. Manual entry sounds like a bug until you reframe it as a feature — no sync errors, no stale data, no dependency on a third party staying in business. That's worth making louder on the landing page.
On encrypted cloud backup: yes, charge for it, but only if the encryption is genuinely client-side with a key you never see. If you can access the data, the privacy story breaks. If you can't, that's your entire pitch in one feature — "even we can't read it." That distinction is the difference between a nice-to-have and a trust-building product decision.