🔏 Privacy Policy
What we store, why, and the rights you have over it — in plain English.1. What we collect
Only what you give us: a username and password (stored as a one-way hash — we cannot read it); optionally an alert e-mail address; and the financial information you choose to enter — watchlists, paper trades, real-holding entries, budgets, bills, debts, goals, net-worth items, and bank-statement rows you import. Community posts you write are visible to other users by design.
2. What we never collect
No real names, no addresses, no phone numbers, no government IDs, no bank credentials (imports are files you upload yourself — we never connect to your bank), and no payment details (the site is free). Our own analytics are cookieless and never identify you (section 8). The site shows advertising served by Google AdSense; what that involves is spelled out in section 9.
3. How your data is used
Solely to run the features you see: showing your own dashboards back to you, computing your reports, and sending the alert e-mails you asked for. Your financial data is never sold, rented, shared with advertisers, or used to target anything at you — ever. That commitment holds even if the site ever carries advertising.
4. Who can see it
You. Your financial data is scoped to your account. Site administrators can see operational metadata (traffic logs, security events) and aggregate statistics, and administrator access itself requires two-factor authentication. Nobody outside the site is given your account data. Market-data providers (Yahoo Finance, FRED, etc.) receive only ticker symbols — never anything about you.
Like any website, the services that deliver the site see ordinary web-request data (your IP address, browser type, the page requested, and the cookies each of them set): Cloudflare (our content delivery network and firewall — privacy policy); Cloudflare Web Analytics and our self-hosted Umami (both cookieless, aggregate page-view measurement — they cannot identify you); and Google AdSense when an ad is shown (section 9). None of them receives your username, e-mail or anything you enter into MoneyDesk.
5. How it is protected
HTTPS everywhere with HSTS; passwords hashed (PBKDF2), recovery and reset codes stored only as hashes; optional two-factor authentication (mandatory for administrators); a web-application firewall that blocks and bans attack traffic automatically; brute-force lockouts; encrypted server storage; and nightly backups with an encrypted off-site copy. The most sensitive imported fields — bank/card transaction descriptions and notes, and each account’s institution and last-four digits — are additionally encrypted at the field level inside the database, so a copied database file does not reveal them.
6. How long we keep things
Your account data: until you delete it (see section 7). Imported bank/card statement rows: deleted automatically once older than your chosen retention period — 24 months by default, adjustable in Expenses to 6, 12 or 36 months, or “until I delete them”; entries you type in by hand are kept until you delete them. Traffic logs (which include IP addresses): 60 days, then deleted automatically. Security-event logs: 180 days. Expired password-reset codes are wiped immediately.
7. Your rights — export and erasure
In the 👤 account menu you can, at any time and without asking anyone: ⬇ Download my data — a complete JSON file of everything stored about you; and 🗑 Delete my account — permanent, immediate erasure of your account and every row of your data. Deletion is real deletion, not deactivation.
8. Cookies & local storage
Set by us: one signed session cookie that keeps you logged in, and nothing else. Your browser's local storage holds only preferences: theme, palette, font, chart settings, and similar. All of it stays on your device and can be cleared from your browser at any time.
Set by advertising: Google and its certified vendors may set cookies (for example the DoubleClick cookie) or use similar identifiers when an ad loads, to serve ads, limit how often you see one, measure results and — unless you opt out — personalise ads to your interests. Section 9 explains your choices. Blocking third-party cookies in your browser is also fully supported: the site works exactly the same; only the ads become non-personalised.
9. Advertising (Google AdSense)
To keep MoneyDesk free, pages may display advertisements served by Google AdSense. Google, as a third-party vendor, uses cookies and similar identifiers to show ads based on your prior visits to this and other websites, to cap how often an ad is shown, to detect fraud, and to measure whether ads were seen or clicked. How Google uses that data is described in How Google uses information from sites that use its services and Google's advertising technologies page.
Your choices. You can turn off personalised advertising from Google at Google Ads Settings; opt out of many other vendors' personalised ads at aboutads.info (US) or youronlinechoices.eu (Europe); or block third-party cookies in your browser. Ads will still appear, but they will not be based on your interests.
Visitors in the EEA, the UK and Switzerland are shown a consent message from Google (Google's certified consent management platform) before any personalised ad is served, and can change that choice at any time by reopening the message from the site footer or the ad itself. Where you decline, only non-personalised ads are shown.
What advertisers never get. As section 3 says: the financial information you enter into MoneyDesk — watchlists, portfolios, holdings, budgets, imports — is never shared with any ad network, never used to target ads at you, and never used to build a profile of you. Ad requests from this site carry only standard web data (page URL, browser, IP address, Google's own cookies), never your account details. Ads are visibly labelled and are not endorsements; MoneyDesk does not vet advertisers and nothing in an ad is financial advice.
ads.txt. The file at moneydesks.com/ads.txt lists Google as our only authorised seller of ad space (IAB ads.txt standard).
10. E-mail
We send only the e-mail you signed up for (alerts, digests, reset codes) to the address you provided, through a transactional provider (Brevo) acting on our instructions. Remove your address in the Holdings section to stop all e-mail.
11. If something goes wrong
If we ever discover a breach affecting your data, we will notify affected users by e-mail (and a site notice) without undue delay, describing what happened, what was affected, and what we and you should do next.
12. Children
The Service is not directed at children under 13 (or the applicable age in your country) and we do not knowingly collect their data.
13. Changes & contact
Changes to this policy appear on this page with a new date. Questions or requests: use ✉ Contact the operator (in the app) (no account needed), or e-mail the operator: show e-mail address (in the app) (privacy requests — access, correction, deletion — are answered within 30 days). See also the Terms of Use and Security guide.