Show the Working

Privacy

This page makes one promise about how it is maintained, and then tells you exactly what is switched on today. The promise is the important half, because the list will change and the promise will not.

The promise

Every tool says what it does with what you give it, on its own page, before you give it anything. Not here, in a policy nobody reads — there, next to the box you are about to type in.

This site will grow. Tools that need an account, that accept a file and hand you back a converted one, or that need to remember something between visits are all possible, and some are likely. When one arrives it will say so on its own page, and the list below will say so too, before it launches rather than after.

That is a promise about process rather than a list of features, which is deliberate. A list of features goes out of date the first time something is added. A promise about how changes are made does not.

What is switched on today

This list is read automatically from the site's own code. If it ever stops matching what actually loads, the build fails — in both directions, so it cannot understate what is running and cannot claim something that is not.

What you type into a tool

Where a tool sends something out, its own page says so and names where it goes. That is the promise, and it is the one worth making: a guarantee that nothing ever leaves your browser would have to be withdrawn the moment this site adds anything that needs a server, and a promise withdrawn later is worth less than a smaller one kept.

Most tools here still send nothing at all. Every calculator, every serial decoder, the name finder’s filters: the work happens on your own machine, so there is nothing to log and nothing to lose. Where that is true the page says it plainly, and where it is not the page says that instead.

Where nothing is sent, nobody measuring traffic can see what you typed. A visit registers as somebody opened the guitar page. It cannot register as somebody looked up serial 61450, because that number never travelled.

There are three exceptions as things stand, and all of them are named below. This list will grow — tools that convert a file have to receive the file — and when it does, it is this page and the tool’s own page that change, in that order.

This is a property of each tool, not a slogan about the site. A future tool that genuinely needs a server — converting a file you upload, for instance — could not honestly make this claim, so it will not make it. It will say what it does instead, on its own page, and the status list above will change.

The first exception: the VIN decoder

The VIN decoder sends the VIN you type to a United States government server. It has to — a vehicle's identity cannot be worked out from the number alone, and the decoding is done by the National Highway Traffic Safety Administration's public database.

The request goes from your browser straight to vpic.nhtsa.dot.gov. It does not pass through this site and nothing about it is recorded here. What the NHTSA do with it is governed by their policy. The VIN page says this on the page itself, before you type anything — which is the promise at the top of this page, working as intended.

A VIN identifies a vehicle. If the vehicle is yours, treat it as information about you.

The second exception: the bicycle serial checker

The bicycle page sends the serial number you type to Bike Index. It has to — whether a bicycle has been reported stolen is a fact held in somebody else's register, and no arithmetic on the number can answer it.

The request goes from your browser straight to bikeindex.org. It does not pass through this site and nothing about it is recorded here. What Bike Index do with it is governed by their policy. The bicycle page says this on the page itself, before you type anything.

A bicycle serial identifies a bicycle. If the bicycle is yours, treat it as information about you.

The third exception: the report form

The report a problem page sends what you write in it to an email service, Mailjet, which delivers it to one mailbox. That is the entire purpose of the page: it is the one place here designed to carry a message to a person rather than to work something out on your own device.

This exception is different in kind from the two above. Those send a serial number to somebody else’s register and the answer comes back to you; this site never sees either. This one is addressed to this site, and it is read.

What is sent is what you put in the boxes: which page you are reporting, what sort of problem it is, your description, and an email address only if you choose to give one. Leave that blank and there is nothing in the report that identifies you. Nothing on this site keeps a copy: it is handed straight to Mailjet, who deliver it to one mailbox. What they retain of it afterwards is governed by their own policy.

Nothing is collected from you anywhere else on the site for this, and no tool page sends anything to the report form. The page says all of this above its own form, before there is anything to type into.

Visitor measurement

This site uses Cloudflare Web Analytics. Every page loads one small script, which sends one message per page view and then does nothing else.

What that message contains was measured, not taken on trust. The script was loaded on a page carrying nothing else and what it sent was read before it left the browser. All of it:

It sets no cookie, and writes nothing to your browser’s storage — no localStorage, no sessionStorage, no database. That was checked too, on the same bare page.

The stripped # is the part that matters here, and it is why the name finder can still say what it says. Searching a name puts it after the # — /baby-names#emma — and that is exactly the part the measurement never receives. It records that somebody opened the baby names page. It cannot record which name they were looking for.

What this site does not claim is that the data could never identify anybody: a browser version and a set of timings are a small amount of information about a machine. The reason your page views cannot be joined into a profile here is simpler and checkable — nothing is stored in your browser to join them with.

Advertising

The intention is to fund this site with advertising. It is free, there is nothing to buy, and advertising is how it pays for itself.

Advertising works differently from the measurement above and it would be dishonest to blur them. When adverts are running:

Two commitments go with that, and they are firm:

Adverts will sit around the tools and not on top of them. A tool you cannot use is not a tool.

Cookies and browser storage

There are none today. No cookies, nothing in local storage, nothing remembered between visits.

That will change if advertising is added, and it may change if a tool is added that genuinely needs to remember something for you. If it does, the status list above will say so and this section will say what the cookie is for. A cookie set for one purpose will not quietly be used for another.

Accounts, and files you might upload

There are none of either today, and the status list above says so. Both are plausible later — a tool that converts a file you upload and hands the result back is exactly the kind of thing this site might add.

If that happens, this page will say, before it launches: what is stored, where, for how long, and how to get rid of it. A file you upload for a conversion is yours, not material for anything else. That is the standard being committed to now, so that it is on the record before there is any temptation to do otherwise.

Server logs

This site is hosted by Netlify, and like every web host they keep access logs — which pages were requested, roughly when, and the IP address that asked. That is how the web works rather than a decision made here. Those logs are Netlify's, governed by their terms; nothing is added to them by this site and nothing is read back out of them.

Links to other sites

The tool pages link out to manufacturers and to the people whose research they rely on, because you are entitled to check the sources. Those sites have their own policies. Following a link takes you out of this one.

Your rights

Under UK GDPR you have rights over personal data held about you — access, correction, erasure, and others. As things stand this site holds none: no account, no record of your visit kept here, and nothing you typed was ever received.

If that changes — and an account would change it — this section will say how to exercise those rights, and the status list above will already have told you the change happened. To raise anything at all, the contact page has the address and a person reads it.

How this page is kept honest

The status list is not decorative. A check in this site's source reads the code of every page, works out what is actually loading, and fails the build if this page disagrees — whether it is understating what runs or claiming something that does not.

That exists because a privacy policy which quietly stops being true is worse than not having one, and because the gap between adding a script and remembering to update a legal page is exactly where good intentions go.

Changes

This page lives in the same source repository as the site, so every change is recorded with a date and a reason. Last changed 11 September 2026.