Visit Tracking: Search Arrivals
When a visitor arrives here 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 the text of any outbound button that gets clicked. This information travels to an edge analytics endpoint and is stored in logs kept on the same domain. It is used only to count page views and outbound clicks. Alongside this, a session view flag is held in the browser for the current visit so that a single page view is counted once rather than multiple times. A first-party cookie tied to search-engine arrivals is set for up to one hour, holding only the name of the referring search engine, so a later outbound click can be matched to the search engine that brought the visitor here. None of these mechanisms set a persistent identifier, and none remain active outside of the search-arrival scenario described above.
Site Construction: Static Files
- The pages are self-contained: everything a page needs to display loads from this domain, with locally embedded fonts rather than files fetched from an outside host.
- The site is served as static hosting on a content delivery network, which handles the technical delivery of every request as the hosting provider for these files.
- The content delivery network reports the country associated with a request, and nothing more precise about where a visitor is located.
- Outbound links to third-party sites pass first through a first-party outbound redirect hosted on this domain before continuing on to the destination.
What Isn't Present Here
This site has no forms, so there is nothing to fill in and nothing typed here is captured. There is no third-party analytics running alongside the first-party visit beacon described above, and no external subresources are loaded from other hosts while a page displays. There are also no contact channels built into this site. These absences are the reason the site does not ask for consent, does not require an account and does not request any personal detail beyond the limited, short-lived, search-referral data already described.
Outbound Links: Separate Destinations
Following an outbound link takes a visitor first through a path on this domain, then on to a separate, independent site chosen by the visitor. Once that redirect completes, the destination site receives the request directly from the visitor's browser and keeps its own record of that visit, entirely apart from anything logged here. This page describes only the mechanisms built into this domain; it says nothing about how a linked destination handles data, and a visitor should treat each destination's own practices as separate from what is written here before sharing anything on that site.