Understand What Happens When You Arrive From a Search Engine
When a visitor reaches this site by clicking through from a search engine, a first-party visit beacon records a small set of details: the page path, the type of event, the name of the referring search engine, and, if applicable, the text of a clicked outbound button. This information travels to an edge analytics endpoint and is stored in the operator's own logs on the same domain. It is used only to count page views and clicks on outbound buttons, and for nothing else. The content delivery network that serves this site also reports the country associated with the request, with no more precise location data collected.
Alongside this, a single first-party cookie is set only when a visit arrives from a search engine. It holds nothing but the name of that search engine, lasts for up to one hour, and exists so that a later click on an outbound link can be matched to the search engine that brought the visitor here. A separate session view flag is kept in the browser for the current visit only, so that a single page view is counted once rather than multiple times. Neither of these stores a persistent identifier, and no other browser storage is set.
Know How Pages Are Built and Served
Every page on this site is self-contained: the fonts are embedded locally, and no page pulls files from an outside host while it is being displayed. The site itself is a set of static files served by a content delivery network, which handles the technical delivery of every request as the hosting provider. Because of this design, there are no forms to fill in, no third-party analytics scripts running alongside the first-party beacon, and no external subresources loading from other domains.
Recognise the Difference Between This Site and the Sites It Links To
This site contains outbound links to third-party sites. When one of these links is followed, the click first passes through a first-party outbound redirect on this domain before sending the visitor on to the partner site. No stored visitor data is shared with the partner during that redirect. Once the visitor's browser reaches the partner site, that site receives the request directly and keeps its own separate record of it; this page has no say over how that destination handles the visit. There are no contact channels on this site, so any information a reader wishes to share should go to the destination site itself rather than to this one.