Privacy policy

The short version

Nothing you type into any of these tools is sent to a server, because the tools have no server component — every calculation runs in your browser, on your own device. No account exists and none can be created. As things stand today, no cookies are set and there is no analytics; the what may change section below says what could alter that, and this page will be updated before it does.

The one exception, described in full below, is that the timestamp converter saves two display preferences in your browser’s local storage so it can remember them. That data stays on your device and is never transmitted.

Information collected

None, as things currently stand. Specifically, these pages do not collect, request, store or transmit:

• Names, email addresses or any other contact details
• Account credentials of any kind — there are no accounts
• Payment information — nothing here is paid for
• The values you enter into any tool: colours, timestamps, dates, dimensions, cron expressions and everything else
• Results the tools produce for you
• Location data, contacts, device identifiers or advertising identifiers
• Anything at all through a form. Two tools do use <form> elements, so that the Enter key and field labels behave the way your browser expects, but neither has anywhere to submit to: they have no action, and the page cancels the submit event and simply recalculates on the spot.

There is no database behind these pages and no endpoint that accepts submissions. For the values you type into a tool in particular, this is a property of how the pages are built rather than a policy choice that could quietly be reversed: the tools contain no code that transmits your input anywhere, and collecting it would mean writing some.

Cookies and local storage

No cookies are currently set by these pages — not first-party, not third-party, not for analytics, not for preferences. That is why you have not been asked to consent to any: at present there is nothing to consent to and nothing to opt out of. If advertising is introduced this will change, and this section will be rewritten to say exactly what is set before it is.

Local storage is used for three display settings. The Unix timestamp converter stores your chosen timezone and your seconds-versus-milliseconds preference, and the countdown calculator stores whether you want dates read day first, month first or year first — a single letter, never a date. All three are kept in your browser’s local storage so that they are still set the next time you visit. This is not tracking: the values are display preferences, they contain no identifier, they are readable only by this site in your own browser, and they are never sent anywhere. Clearing site data for this domain in your browser settings removes them, and the tools work perfectly well without them.

Some tools also put your inputs in the page’s URL fragment — the part after the # — so that a specific result can be bookmarked or shared. URL fragments are never transmitted to a web server by the browser, so this does not disclose your inputs to anyone unless you copy the link and send it yourself.

Third-party content

There is currently none. As things stand today, these pages make no external requests: no fonts, scripts or stylesheets from a CDN, no remote images, no embedded videos, no social widgets, no comment system, no tag manager, no advertising and no analytics beacons. Every asset a page currently uses comes from this one origin.

The practical effect today is that no third party learns you visited, because no third party is contacted. You can confirm the current state for yourself: open your browser’s developer tools, switch to the Network tab, and reload any page here. Every request listed will be to this domain. If that ever changes — see what may change — what will not change is that the tools themselves keep their work local: the values you type are handled by JavaScript on the page and are not transmitted to anyone.

The pages do link out to other websites in a few places — for example to published specifications. Those are ordinary links; following one takes you to a site with its own privacy practices, which this policy does not cover.

Server logs and hosting

These pages are served as static files by a commercial hosting provider. As with any website, requesting a page means your browser sends an ordinary HTTP request that the provider’s infrastructure processes, and that infrastructure keeps its own operational and security logs — typically including IP address, timestamp, requested path and user-agent. This is standard for the whole web and is used by the provider for delivery, abuse prevention and reliability.

No analytics platform is currently layered on top of those logs, and they are not used to build profiles of visitors, connected to anything you type into a tool, sold, or shared for marketing. Mentioning this explicitly seems more useful than claiming a level of invisibility no website can honestly offer.

If you email

The contact page lists an email address. If you write, your message and address are handled by the relevant email providers and are used solely to reply to you and to act on what you reported. They are not added to any mailing list, not shared with third parties, and not used for marketing.

What may change

Two changes are realistically possible, and it is worth being upfront about them rather than quietly introducing them later.

• Advertising. Advertising may be added to help cover hosting costs. Ad networks generally load third-party code, may use cookies or similar technologies, and in some regions require a consent prompt before they run — all of which would be a genuine change to how these pages behave.
• Analytics. Aggregate analytics may be added to see which tools get used.

If either is introduced, this policy will be updated first to name what was added, what it collects, and what choices you have — before it appears on the pages, not afterwards. What will not change is the core of it: the calculations stay in your browser and your inputs are not sent to a server.

Because there is no mailing list, there is no way to notify you of a change directly. If this matters to you, check this page occasionally.

Your rights, and a note on legal claims

Data protection laws such as the GDPR and the CCPA give people rights over personal data held about them — access, correction, deletion, and objection to certain processing. Those rights are meaningful, and the honest position here is simply that, as things currently stand, there is no personal data held to exercise them against: no collection, no database, no profiles, no sale or sharing of personal information. If you believe otherwise, get in touch and it will be looked into.

This page describes actual practice in plain language. It is not legal advice, and no claim is made to hold any privacy certification, audit or formal compliance attestation.