What we measure

What gets written down

One row per event, in a database we run. No analytics company is involved, and no third-party script loads on this site.

Page

The path you looked at — /tools, never the query string

Event

Which of a short list happened: a view, a marked button, a link out

Came from

The hostname that linked you here, if any

Campaign

The three utm_ values, when a link carries them

Shape

Phone or desktop, browser family, operating system — no versions

Visitor

A one-way hash that stops working tomorrow (below)

What never gets written down

• Your IP address
• Your full user-agent string
• Full URLs, query strings, or anything you typed
• Your name, email, or any account — the site has no accounts
• Precise location
• Any identifier that survives to the next day, or reaches another site

Your IP address and browser string reach our server, because every web request carries them. They are used once, in memory, to work out the two things above — a rough device shape and the visitor hash — and are then gone. Neither is stored in the database or written to a log.

The hash that expires

To tell one visit from two, each row carries a short hash of your address and browser mixed with a secret key. A new key is generated every day and the previous day’s key is destroyed. Once that key is gone, the hash cannot be traced back to anything, or matched against tomorrow’s — so we can count a day’s visitors without ever being able to follow one across days.

Turning it off

If your browser sends Global Privacy Control, nothing is recorded at all — the request is dropped before anything is derived from it. Blocking requests to /api/t works just as well; the site is built to work identically either way.

How long it lasts, and who sees it

Rows are deleted after 400 days. Nothing is sold, shared, or handed to an advertising network. If you email us, that email lives in our inbox like any other — this page is about the website, not about correspondence.

Questions: get in touch.