This page explains what happens on a technical level when someone visits this site, and nothing beyond that. It covers only what this build actually does: a small amount of visit counting, one short-lived cookie tied to search-engine arrivals, the fonts and files the pages load, and the way outbound links are handled.
Visits
When a visitor arrives from a search engine, a first-party beacon sends a small piece of visit data to an edge analytics endpoint on this domain.
- What is sent: the page path, the type of event, the name of the referring search engine, and the text of any clicked outbound button.
- When it fires: only for a visit that arrives from a search engine — not for other visits.
- What it is used for: counting page views and clicks on outbound buttons, for the operator's own traffic counting.
- Where it stays: in logs kept on the same domain, alongside the country the content delivery network reports for the request. Nothing more precise about location is recorded.
Cookie
One first-party cookie is set, and only under the same condition as the beacon above.
- It is set only for a visit that arrives from a search engine.
- It holds nothing but the name of that search engine.
- It is kept for up to one hour, then expires.
- It is used only so that a later click on an outbound link can be tied to the search engine the visit came from.
Alongside this, a separate session view flag is kept in the browser for the current session so that a single page view is counted once. This flag does not persist beyond the session and carries no identifying content.
Pages
The pages themselves are self-contained: fonts are embedded locally rather than pulled from another host, and the site is served as static files from a content delivery network acting as the hosting provider. That provider processes the technical data of every request in the ordinary course of serving those files. No other browser storage and no persistent identifier are set beyond the one-hour cookie and the session flag described above.
Links
This site links out to third-party destinations. Following one of those links passes first through a first-party outbound redirect hosted on this domain before continuing to the partner site.
- While a page is being displayed, every file it needs comes from this domain — nothing is fetched from an outside host during that display.
- Once a visitor follows an outbound link, the redirect hands off to the partner site, which then receives the request directly from the visitor's browser and keeps its own separate record of that visit.
- What a partner site does with that request is outside this page's scope: it is a separate destination with its own practices.
Forms and contact
This build has no forms, no contact channels, no login, and no registration on it. There is no mechanism here for submitting a name, an email address, an account identifier or a payment detail, because no such field exists on these pages. Readers should not attempt to submit personal details through this site, since no channel is built to receive or store them.
Scope
Everything above describes only the mechanisms built into this static site. It does not describe, and should not be read as describing, what happens on any partner site reached through an outbound link — those are separate destinations with their own separate records.