This page explains what happens on a technical level when this site is visited, based only on how the site is actually built. It covers the small amount of visit data that is recorded, the one short-lived cookie in use, how outbound links to partner sites work, and what this site does not include at all.
Records the essentials of a search-engine visit
A first-party visit beacon and an edge analytics endpoint work together to note a page path, an event type, the name of a referring search engine and the text of a clicked outbound button. This only triggers when a visitor arrives from a search engine, and the data is written into logs kept on this same domain.
- Page path and event type — recorded to count page views and clicks on outbound buttons.
- Referring search engine name — recorded only when the visit originates from a search engine.
- Country of the request — reported by the content delivery network handling the request; nothing more precise about location is captured.
- Session view flag — a single marker kept in the browser for the current session, so one page view is counted once rather than repeatedly.
Uses one short cookie and no persistent identifiers
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 up to one hour, and exists so that a later click on an outbound link can be matched back to the search engine that brought the visitor here. Beyond this cookie and the session view flag, no other browser storage and no persistent identifier are set. Every page on this site is self-contained, with fonts embedded locally rather than pulled from an outside source, so nothing else loads from beyond this domain while a page is displayed. The site itself is a set of static files served from a content delivery network, which handles the technical delivery of each request as the hosting layer.
Sends outbound clicks through a first-party redirect
Outbound links to third-party sites do not go straight to the partner. Each one first passes through a path on this domain, which then redirects the browser onward. This first-party outbound redirect step is how a clicked button's text can be recorded before the visitor leaves. Once the redirect completes, the destination site receives the request directly from the visitor's browser and keeps its own separate record of that visit; this page describes only the mechanics on this domain, not what happens after departure.
Has no forms, accounts or outside data sharing
There are no forms anywhere on this site, so nothing is ever typed in and submitted here. There is no third-party analytics service reading this traffic, no external subresources loaded from other domains, and no contact channel of any kind — no address, no submission box, nothing to fill in and send. Nothing recorded here is passed to advertising networks, data brokers or outside analytics tools. If a reader wants to reach the operator of a linked destination, that has to happen on the destination's own site, under its own terms, since this page has no bearing on how that separate site is run.