Quick answer
Client-side calculation means your inputs stay local. Check for yourself rather than trusting a claim: the network tab tells you the truth.
Client-side and server-side
A client-side calculator ships the logic to your browser as JavaScript and runs it there. You type a date, your own device does the arithmetic, and the result appears. No request carrying your values is made because there is nothing to make it to.
A server-side calculator sends your inputs to a remote machine, which computes and sends a result back. That is a perfectly normal design, but it means your values leave your device and may be logged, retained or analysed depending on what that service does.
Use this guide with the right tool: Open the Age Calculator for exact chronological age in completed years, calendar months and remaining days. If the question shifts, compare it with the Date Difference Calculator or the Birthday Countdown Calculator.
How to tell which you are using
Open your browser's developer tools, go to the network tab, clear it, then press Calculate. If no new request appears, the calculation happened locally. If a request goes out carrying your values, it did not.
A second test: disconnect from the network after the page has loaded, then calculate. A client-side tool keeps working. This is a more accessible check than reading a privacy policy, and it is harder to get wrong.
What client-side does not protect against
Local calculation says nothing about analytics, advertising scripts or embedded third-party code running on the same page. A page can compute your age locally and still report your visit, your referrer and your behaviour to several other companies.
It also says nothing about URLs. Where a tool writes your inputs into the address bar so a result can be shared — as the tools here do — that URL contains your dates. It stays on your device unless you share it, but it will appear in your history and in anything you paste it into.
Sensitive dates deserve the check
Dates of birth, gestational dates and employment dates are ordinary-looking and genuinely identifying. A date of birth combined with a postcode narrows a population sharply, which is why it appears in so many identity-verification flows.
That is a reason to spend thirty seconds checking a tool before entering something you would not want logged — particularly a tool you found through an advert, or one that asks for more than the calculation needs. Any field that is not used in the arithmetic is a question worth asking about.
Worked example
Pressing Calculate with developer tools open produces no new network request, so the dates never leave the tab, while a share link stays local until you send it. Test your own calculator page the same way before trusting its privacy claim.
What one date gives away
A date of birth looks like a single fact. It is a compressed file. From 18 November 1994 alone, anyone can derive that the person was born on a Friday; that on 16 August 2026 they had lived 11,594 days and were exactly 31 years, 8 months and 29 days old; that their thirty-second birthday falls on Wednesday 18 November 2026; and that their ten-thousandth day of life was Tuesday 5 April 2022. None of that was typed anywhere. All of it was inside the one field, waiting for arithmetic — the same arithmetic this page performs in the browser precisely so that the field itself never has to travel.
That is the right way to understand what a shareable result link contains. It does not contain an answer; it contains the input from which every answer can be rebuilt, by anyone who receives it, at any later date, without your involvement. A link encoding a birth date of 12 January 2026 and a reference date of 16 August 2026 discloses that a particular baby was 216 days old on a particular day — the child's birth date and the family's checking date in a single string of text, reproducible forever by whoever holds it. The calculation stayed private. The link is the part that leaves.
The network-tab check itself rewards a closer reading. The requests to look for are not all requests: a page legitimately loads its own code, styles and fonts before you type anything, and those requests can carry nothing you have entered because you have not entered it yet. The check is segmented — load the page and watch, then type, then calculate, and confirm that the second and third stages add no request at all. On this site the only external call in the first stage is the font. A tool that phones home only when you press Calculate has arranged its traffic in exactly the segment where your values exist to be carried, and the segmented check is how you catch that.
The offline test makes the same point without any developer tools. Load the page, disconnect, and calculate: a client-side tool is unaffected, because everything it needs is already on the device. A server-side tool fails at exactly the moment of calculation — which is also the moment it would have transmitted. The two tests together take under a minute, they work on any calculator you will ever be handed, and they are worth the most on precisely the dates that unfold the furthest: births, pregnancies, and the start dates of employments, each of which is a small biography disguised as a field in a form.
The second date in a link deserves the same suspicion as the first. A reference date timestamps the calculation itself: it says when someone was checking, and often why — a school cutoff being tested in August, a pension date being tested in the month before retirement. Combined with the birth date it narrows the field further. There are only about 36,500 possible birth dates in a hundred-year span, and each additional dated fact — a weekday of birth, a reference date, a milestone reached — divides that field again. None of this requires the values to be sent anywhere. It only requires them to be written down somewhere they can be read together, which is what a URL is.
Common mistakes to avoid
- Reading a privacy claim instead of checking. The network tab is faster and more reliable than any policy page.
- Assuming local calculation means no tracking. Analytics and advertising scripts are separate from where the arithmetic runs.
- Sharing a result URL without reading it. If it contains your inputs, sharing it shares your dates.
Use the right calculator
The Age Calculator gives age in years, months and days, the Date Difference Calculator compares two dates, and the Birthday Countdown Calculator counts down to the next birthday.
Frequently asked questions
Do the calculators on this site run locally?
Yes. Press Calculate with the network tab open and you will see no request. They also keep working offline once loaded.
Does this site use analytics?
No — no analytics, advertising, tag manager or session recording. The only external request is to Google Fonts.
Is a date of birth personal data?
In most privacy regimes, yes, particularly combined with anything else. It is worth treating as sensitive even when a form treats it casually.