Two analytics tools, and what each one sees
This site runs Google Analytics, which counts visits, and Microsoft Clarity, which records how a page is used and can replay a visit. No advertising network, no profile sold to anybody, no account, and one form, on the corrections page, which sends only what you type into it.
Last updated
What the analytics does
Google Analytics records that a page was viewed, roughly where in the world the visit came from, which page sent you here, and what kind of device you are on. It sets cookies in your browser to tell one visit apart from the next. It is used here for one thing: working out which pages answer a question and which ones do not.
Both were added on 26 July 2026, and before that this site made no third-party requests at all. That is a real change to what happens when you load a page, which is why it is written at the top of this one rather than buried.
What Clarity does, and it is more than counting
Microsoft Clarity records how a page gets used: where a cursor moves, what gets tapped, how far a page is scrolled, and where somebody gives up. It builds heatmaps from that, and it can replay an individual visit as a reconstruction of those movements. It is here for one reason, which is finding the pages where a person at an equipment pad cannot get an answer.
It is a session recorder, and that is a materially different thing from a page counter, so it is named as one here rather than folded into the word analytics. Clarity masks text content by default, and this site has no login, no cart, no address field and no payment form, so there is nothing sensitive on a page for it to capture. The one form on the site is the corrections form, and what you type there goes to the host either way.
What neither of them is
No advertising is sold or served here, nothing you do is sold to a data broker, there is no email capture and no account. The honest qualification, which an earlier version of this page got wrong: Clarity sets a Microsoft advertising identifier as part of how it works, so a Microsoft advertising cookie does exist on your browser after you visit, even though this site runs no ads and buys none. Fonts are served from this domain rather than from a font network, so apart from those two tools and Microsoft's identifier sync, nothing leaves this site.
Turning them off
Any browser tracking-protection setting stops both, and so does Google's own opt-out browser add-on for the analytics half. Nothing on this site breaks when they are blocked: every page is static and the only other script is the lookup on the home page, which talks to nothing.
The one piece of JavaScript on the site runs the lookup on the home page. It reads a list of routes that is already inside the page and sends you to one of them. It talks to nothing.
How to check it rather than trust it
Open your browser's developer tools, load any page here, and look at the network panel. You will see requests to this domain, to Google's analytics domains, to clarity.ms, and to c.bing.com, which is Clarity handing Microsoft an identifier so the same visitor is recognised across Microsoft's own services. Twelve cookies get set across four domains: two for Google Analytics, two for Clarity, and the rest belonging to Microsoft, including an advertising identifier called MUID. That last one is why the sentence above says two tools and this paragraph says four domains: Clarity brings Microsoft with it, and this page would rather name that than round it off. That is a stronger assurance than this paragraph, and it is the one worth acting on.
The one exception, and it is opt-in
The corrections page carries a form. If you choose to send a correction, what you type in it goes to the hosting provider and is read before the next data refresh. It asks for a page, a claim and a document, and it deliberately has no field for your name or your email, because there is no reply address and collecting a contact detail nobody will use is collection for its own sake. Nothing else on the site sends anything anywhere.
What the host can see
This site is served by a hosting provider, and a web server necessarily receives the address of the computer asking for a page in order to send it back. Those server logs are the hosting provider's, they are not read for anything here, and nothing on this site connects a request to a person.
When this changes again
It changes the day the site carries a commercial link, because an outbound link to a retailer means that retailer knows you arrived from here. That will be disclosed at the link itself, and this page will be updated on the same day rather than afterwards. The analytics tag was added that way too: the page changed in the same commit as the tag, not after somebody noticed.