Privacy. Boringly straightforward.
Last updated: April 2026 (revised to clarify the small set of features that touch our backend). We believe privacy is a right, not a feature.
Your data stays on your device
MyMoneyMap stores your financial profile, goals, and progress exclusively in your browser's localStorage. Nothing is uploaded to any server. We don't have a database of user profiles. We couldn't look at your data even if we wanted to.
- Profile data (income, assets, debts, goals):
localStorageonly - Encrypted backups: AES-256-GCM with PBKDF2-SHA256 (600,000 iterations). Only your password can decrypt them.
- Auto-sync files: written to a file you choose on your computer. If you put it in a cloud folder, that's your cloud service syncing, not us.
- Learning progress, badges, streaks: localStorage only
What we don't do
- We do not sell or share your data with anyone
- We do not use advertising or ad networks
- We do not collect email addresses for marketing
- We do not use third-party trackers like Facebook Pixel
- We do not store your transactions, balances, or any financial figures on a server
- We do not monetize your financial data in any way
For transparency: we use anonymized Google Analytics 4 (IP-anonymized, no personal identifiers) to count page views so we know which tools are useful. Disabled if you have Do Not Track enabled.
What goes to our backend
Most of MyMoneyMap is local-only. A few features need a backend (Supabase), and we want to be specific about exactly what:
- Sign-in (Google / Apple): only your provider-supplied identity (e-mail + display name) so progress can sync across devices. You can use every calculator and tool without signing in.
- Learning progress (signed-in only): path completion, badges, streaks, and MoneyCoins are written to a private row keyed to your account so they survive a browser wipe. Row-level security blocks every other user from reading it.
- Bucky feedback & corrections: when you click "Suggest" or send Bucky a chat message, the message text and the page path are written to an admin-only feedback table. We don't attach your account or device to it.
- Merchant fingerprints: when the Statement Analyzer learns that a merchant string belongs to a category (e.g. "LOBLAWS #1234" → groceries), an anonymized fingerprint of that string is shared so the next person's statement auto-categorizes too. No amounts, no dates, no account info.
- Community posts & comments (opt-in): if you post in the Community, the post text and your chosen handle are public - that's the point of a community. You can delete your own posts at any time.
What we still don't send: your transactions, balances, income, debts, goals, calculator inputs, or any other financial figures. Those stay in localStorage on your device.
Cookies and local storage
MyMoneyMap uses browser localStorage (not cookies) for the following:
| Storage key | Purpose |
|---|---|
| mmm.profile.v1 | Your financial profile |
| mmm_auth_v1 | Sign-in state |
| mmm_progress_v1 | Learning progress, badges, streaks |
| mmm_community_v1 | Community contributions |
| mmm.dashboard_view.v1 | Simple vs Detailed preference |
| mmm.merchant_overrides.v2 | Learned merchant categories |
| mmm.category_rules.v1 | User-created category rules |
| mmm.recommendations.v1 | Recommendation learning history |
No cookies are set by MyMoneyMap. Zero. None.
Your rights
- Export: download all your data as encrypted or plaintext JSON from the dashboard
- Delete: one-click "Wipe everything" in the dashboard erases all data
- Portability: your backup is standard JSON - readable, importable, deletable
- No lock-in: stop using MyMoneyMap at any time with zero consequences
PIPEDA & Law 25 compliance
MyMoneyMap is designed to comply with Canada's PIPEDA and Quebec's Law 25 by default. We don't collect personal information beyond what's stored locally in your browser. No third-party data sharing, no tracking cookies on first visit, and you can delete everything at any time.
Questions? This privacy policy is intentionally short because our practices are simple. Use the Community Q&A or the "Suggest a correction" button.