This page explains what happens on this domain and nothing beyond it. Read it before following any outbound link, since a separate site takes over the moment you leave.
See what triggers data collection here
A small analytics beacon only fires when a visitor arrives from a search engine. It notes the page path, the type of event, the referring search engine's name and the text of any outbound button clicked. This information goes to the operator's own edge analytics endpoint and is stored in logs on the same domain.
The content delivery network also reports the country associated with a request, without any finer location detail. None of this happens for visitors who arrive directly or from a link that isn't a search engine.
Know what the cookie and session flag do
One first-party cookie is set only for search-engine arrivals. It holds nothing but the name of that search engine, lasts up to one hour, and exists so a later outbound click can be matched to the search engine that brought the visitor here.
Separately, a session view flag lives in the browser only for the current visit. Its sole purpose is to stop a single page view from being counted twice. Neither of these leaves a lasting identifier once the session or the hour ends.
Understand how outbound links are handled
Outbound links first pass through a first-party redirect on this domain before sending you onward. That redirect step is how a click gets recorded before you land on the partner site. Once you arrive there, that separate site receives your request directly and keeps its own record of it, independent of anything logged here.
Recognize what this site does not do
This site has no forms, no third-party analytics, no external subresources and no contact channels. Every page is self-contained, with locally embedded fonts, and served as static files from a content delivery network. Nothing here asks for names, e-mail addresses, account details or payment information, and there is no login or account of any kind.
Know the limits of this page
This page describes only the mechanisms confirmed for this build: the visit beacon, the analytics endpoint, the session flag, the outbound redirect, and the absence of forms, third-party trackers, external resources and contact channels. It makes no claims about any partner site's own data practices. Treat any site reached through an outbound link as a separate destination with its own record-keeping, and avoid submitting personal data through channels that aren't described here.