What we know about you, and what we can't.

• There is no sign-up, no login and no user account, so there is no profile of you to hold.
• The calculators run entirely in your browser. Typing figures does not send them to us. Opening or reloading a URL containing figures sends that URL to our server, where it may appear in access logs.
• This site sets no cookies of its own and writes nothing to local storage. That is a property of the code, not a policy choice we could quietly reverse without changing the software.
• We do not sell, rent or share data with data brokers. That one is a policy, and you have only our word for it.

Every calculator on this site is JavaScript that ships with the page and runs on your device. When you enter an income, a balance or a property value, the computation happens locally and the result is written straight back into the page. No request is made, because there is no calculation endpoint on the server to make one to.

This is worth distinguishing from the usual assurance. A site that computed your figures on a server could promise not to keep them, and you would have to believe it. Here typing values triggers no calculation request, which is verifiable rather than trusted: open your browser's network panel, type into any calculator, and watch that no request carries what you typed.

There is no account history from which to restore yesterday's calculation. A saved URL can restore the inputs it contains, but it also shares them with anyone who can read that URL. Request logs are distinct from a saved calculation history.

So that a result can be shared, each calculator mirrors its current inputs into the page's address. After a moment with the mortgage calculator, the address bar reads something like:

/calculators/mortgage-calculator/?amount=421500&rate=6.5

While you are typing, the address is rewritten in place by your browser and no request is sent. The address bar still contains the figures, so consider who can see or copy it.

If you copy that link and open it, reload it, or send it to someone who opens it, the figures are part of the URL sent to the server to fetch the page. Your numbers then cross the network. Our web server records access logs, including the requested URL and query string, IP address, time and browser information. Figures in a requested URL may therefore be stored in those logs. Browser history and anyone you share the link with may also retain the URL.

What follows practically: a link with your real figures in it is as private as the place you put it. Treat it the way you would treat a screenshot of the same numbers: share it only with someone you intend to show those figures, not in a public post. To share the tool without the figures, link to the page address with the ? and everything after it removed.

The canonical URL of every calculator page is query-free. It tells search engines which page address we prefer, but it does not make a shared URL private or guarantee that a URL containing figures cannot be indexed.

No analytics is loaded in this build. No measurement ID is configured, so no third-party analytics script is requested and no analytics event is sent at all. The rest of this section describes what would be collected if it were switched on, so that the answer does not change quietly.

Everything the site can report passes through a single allowlist in src/lib/analytics.ts. An event not named there is dropped, and so is any property not declared for that event. This means adding a field at a call site is not enough to publish it. The list below is generated from that allowlist, so it is the real inventory rather than a summary of one:

calculator_used

calculator_id

detail_opened

calculator_id, detail

result_shared

calculator_id, method

source_followed

calculator_id, source_host

Every value in that column is a page identifier, a tool identifier or a fixed word. No figure you enter appears in any of them, and not in bucketed form either: a range is still a statement about your money, and combined with a timestamp it starts to identify you. The allowlist rejects numbers as a type, independently of the field names, so the same mistake is caught twice.

Analytics reports the page address with the query string removed, for the reason section 03 explains: the address bar on a calculator page holds your figures, and the default behaviour of an analytics tag is to report the address it finds. That default is overridden explicitly on every event and on the page view.

IP anonymisation is on. We do not use Google Signals, advertising features or cross-device tracking, and there is no remarketing audience.

The three typefaces the site is set in are self-hosted: the WOFF2 files ship from this origin, not from a font CDN, so loading a page here makes no request to Google or anyone else for fonts. There are also no embedded widgets, no social buttons, no chat popups, no session recording and no A/B testing service.

• www.googletagmanager.com: not requested in this build. It would be the analytics script, and it loads only when a measurement ID is configured.

That is a change from an earlier build, which served the same three typefaces from fonts.googleapis.com and fonts.gstatic.com. Those requests are gone now, not merely described as an improvement to make.

This site sets no cookies. It also writes nothing to local storage, session storage or any in-browser database. A saved URL or browser history can still contain your inputs and restore them on a later visit. Server access logs can contain requested URLs, as explained in section 03.

Google Analytics would set its own cookies if it were loaded. It is not loaded in this build. The cookie policy lists each one individually, including what it is for and how long it lasts.

No advertising is enabled on this build, so no advertising cookie is set. Should that change, this page and the cookie policy change with it, before the ads go live rather than after.

Depending on where you live, you may have rights to access, correct, delete or port personal data an operator holds about you, and to object to its processing. Under the GDPR and under US state laws such as the CCPA those rights are legally specific, and we are not going to paraphrase them badly here.

We hold no user account or saved calculation history. If you contact us, your correspondence can contain personal data. Server access logs can also contain personal data, including your IP address and figures included in a requested URL. A rights request may therefore concern correspondence or logs even though the calculators run locally.

To ask about personal data or exercise applicable rights, use the contact page. Please do not include sensitive financial figures unless needed to explain your request.

We ask for no consent banner because we set no cookie that requires consent. If advertising or a non-essential cookie is ever introduced, consent will be asked for properly at that point.

This site is not directed at children and we do not knowingly collect anything from anyone under 13.