Privacy
Last updated: 11 September 2026
Every number you type — your salary, your bonus, your family — is used by JavaScript running in your own browser tab and is never sent anywhere. There is no account, no database and no server-side calculation. Close the tab and it is gone.
How that is enforced rather than promised
The site is served with a Content-Security-Policy whose connect-src does not
include this site itself. That means no fetch, XMLHttpRequest or
beacon from this page can reach our server, which is how a calculator would send data if it
sent any. form-action is 'none': no form here can submit to anything.
You can read the policy in the _headers file of the repository, or see it in your
browser's network tab on any response from this site.
To be exact about what a policy can and cannot do: it is not a proof. img-src
allows images from this origin, and a request for an image is still a request — a careless
script could put a number in a URL that way, and no policy would stop it. What the policy does
is remove every destination that is not named in it, and make adding one a visible change to a
file in the repository. The rest is the code being small enough to read.
Nothing is written to localStorage, sessionStorage, IndexedDB or a
cookie by this site's own code.
What is loaded from elsewhere
The pages, stylesheet, icons and scripts all come from this domain. Fonts are the ones already on your device; none are downloaded.
Google Analytics 4 is loaded, if and only if a measurement ID has been set in
assets/config.js. While that value is empty — as it is until the site's analytics
property exists — no analytics script, cookie or request happens at all.
When it is set, it records the usual page-level things: the page you are on, the referrer, your device and browser, and an approximate location. Google derives that location from your IP address on arrival and, in GA4, does not store the address itself. Two things worth being straight about rather than reassuring about: your IP address is still sent to Google in order to be used that way, and GA4 sets a persistent identifier in a first-party cookie so that two visits from the same browser can be counted as one person. That identifier is not a name and we have no way to attach one to it, but it is not nothing either. A content blocker that refuses the Google script stops both, because then nothing is requested at all. Google’s own opt-out add-on is weaker than that: it stops the script reporting your activity, but the script is still fetched, and a cookie already set is not removed by installing it.
It also records a small number of named events so we can tell which parts of the tool get used:
- a page view
copy_result— that somebody copied the month-by-month table
None of those events carry an amount, a salary, a date of arrival or anything else you typed — that is the part this site controls, and it is absolute. Google's own handling of the data it collects is described in Google's privacy policy, and you can switch it off for every site with the Google Analytics opt-out add-on or any content blocker.
Advertising
The page reserves the space for one advertisement, and at the time of writing loads nothing
into it: no ad script, no ad network, no ad cookie. An application has been made, so this may
change; when it does, this page will say which network it is and what it sets, and the
Content-Security-Policy in _headers will have to name the network's hosts before
the browser allows them, which is a change you could see in the repository.
Hosting logs
The site is hosted on Cloudflare Pages. Like any web host, Cloudflare's edge records requests it serves — the URL, the time, your IP address, your user agent — for delivery, caching and abuse prevention. Those logs are Cloudflare's, are not joined to anything we hold, and contain nothing you typed into the calculator, because none of it is ever sent.
Who runs this
YenTake is made by Tekiba, which builds small tools that run in the browser. Questions and corrections, including anything wrong on this page: hello@tekiba.app.