Privacy

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

Almost everything below is a description of how the site is built rather than a promise about how we behave. Where it is a promise instead, it says so — the difference matters, because one you can verify and the other you can only trust.

The short version

No accounts, no cookies set by us, no calculation stored anywhere.

  • 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. The figures you type are not transmitted to us, and we could not retrieve them if asked.
  • 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.

Why the arithmetic can't reach us

Not a promise to discard your figures — an absence of anywhere to send them.

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 the values never arrive, 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.

Two consequences follow, and both are costs we accept rather than features: we cannot restore a calculation you made yesterday, and we cannot tell you what the average visitor enters, because we do not have it.

The exception: shared links

One case where figures do travel over the network. Stated because it is easy to leave out.

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, this costs nothing in privacy terms: the address is rewritten in place by your browser and no request is sent.

But if you copy that link and open it — or send it to someone who does — the figures are part of the URL, and a URL is sent to the server in the request that fetches the page, exactly like any other address. In that one case your numbers do cross the network. They are not stored or logged by us, but the honest statement is that they left the browser, and a policy claiming otherwise without qualification would be wrong.

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 — fine in a message to your partner, not fine 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, which is a separate safeguard with a different purpose: it stops a URL containing someone's salary from being treated by a search engine as a page worth indexing.

Analytics

Currently not enabled. The complete list of what it may send is below.

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 — which 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.

Who else your browser talks to

Two hosts, named. Nothing else is requested.

Loading a page here makes requests to these hosts and no others. There are no embedded widgets, no social buttons, no chat popups, no session recording and no A/B testing service.

  • fonts.googleapis.com and fonts.gstatic.com — the three typefaces the site is set in. Google receives the request for the font files, which includes your IP address, as any request does.
  • www.googletagmanager.comnot requested in this build. It would be the analytics script, and it loads only when a measurement ID is configured.

Self-hosting the fonts would remove the first entry, and it is the obvious next improvement to this list. It is named here rather than omitted because a "no third parties" claim with a font CDN in the page would be false.

Cookies and stored data

None set by this site. The code contains no call that could set one.

This site sets no cookies. It also writes nothing to local storage, session storage or any in-browser database. Your last calculation is not remembered between visits, and that is a direct consequence of storing nothing rather than a setting.

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.

Your rights, and what they amount to here

Mostly nothing to exercise them against, which is the point.

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.

What we will say is what they amount to in this case. We hold no account, no email address unless you sent us one, and no record of any calculation. So an access request would return nothing about your use of the calculators, because nothing about it exists — and a deletion request has nothing to delete.

If you have written to us, that message is personal data and your rights apply to it normally. Ask us on the contact page and we will delete the correspondence.

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.

Changes

A policy that changes
quietly is not a policy.

Most of what this page says is a description of the software, so the way it changes is that the software changes first. If analytics is switched on, if a cookie is introduced, or if advertising is enabled, this page and the revision date below change in the same release — not afterwards.

If you find something here that does not match what your browser actually does, that is a defect and we want to hear about it. A network panel screenshot is the most useful thing you can send.

Last reviewed September 19, 2026. Applies to Rate & Sum at every address it is served from.