This page explains exactly what happens on this site when a page loads, when a search-engine visitor arrives, and when an outbound link is followed. Nothing described below extends beyond what the site's own build actually does.
Visit Tracking: search referrals
When a visitor arrives from a search engine, a first-party visit beacon fires and sends a small set of details to the site's own edge analytics endpoint: the page path, the type of event, the name of the referring search engine, and the text of any outbound button that gets clicked. This happens only for search-engine arrivals — visits that come directly or from other sources do not trigger this collection. The data is used solely to count page views and outbound-button clicks for the operator's own traffic figures, and for nothing else. It is stored in the operator's own logs, on this domain, alongside the country the content delivery network reports for the request. No more precise location is collected.
Session Signals: short-lived markers
A session view flag is kept in the browser for the current visit only, so that a single page view is not counted more than once. Separately, one first-party cookie is set, but only when a visitor arrives from a search engine. It holds nothing beyond 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 to the search engine the visit came from. Neither of these signals stores a persistent identifier, and no other browser storage is set.
Outbound Links: redirect handling
Links to third-party sites on this page do not go straight to the partner. Each one first passes through a first-party outbound redirect on this domain before sending the visitor onward. This redirect step is part of how the click text is recorded for counting purposes. Once the visitor reaches the partner site, that site receives the request directly from the visitor's browser and keeps its own separate record of it. This site does not control what a partner site does with that request, and nothing stored here is shared with the partner at that point.
Site Construction: static hosting
This site consists of self-contained pages with locally embedded fonts, served as static files through a content delivery network. Every file a page needs comes from this domain, so no outside host is contacted while a page is being displayed. The content delivery network processes the technical details of each request in its role as hosting provider. Because the site is built this way, there are no forms anywhere on it, no third-party analytics scripts, no external subresources loaded from other domains, and no contact channels of any kind. There is no login, no registration, no user account, and no field anywhere that asks a visitor to type in personal details. Nothing here is designed to collect a name, an e-mail address, an account identifier or payment information, and nothing of that kind is retained. No visitor data or personal data is shared with advertising networks, data brokers, or outside analytics services, and no third-party or advertising cookies are used. This is why the site does not ask for consent, does not require an account, and does not request any personal detail from the people who read it.