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
The shape of the calculation stays the same with your own figures. What changes is the source of the rule, so check that before treating the number as settled.
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
Start with whichever matches the information you already hold. The other two are there for when the question shifts.
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.