This page explains exactly what happens on this site when a page loads or an outbound link is clicked. It covers only what the site itself does, not the destinations reached after leaving this domain.
What does this site actually record?
When a visitor arrives from a search engine, the site notes the page path, the type of event, the name of the referring search engine and the text of any clicked outbound button. This happens through a first-party visit beacon that sends this small set of details to an edge analytics endpoint on the same domain. The data is used only to count page views and clicks on outbound buttons, nothing else. Alongside the page path and event type, the site also picks up the country that the hosting network reports for the request — no more precise location is collected.
How long does any of this stick around?
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 a later click on an outbound link can be matched to the search engine that brought the visitor here. Separately, a session view flag lives in the browser only for the current visit, making sure one page view is counted once rather than repeatedly. Neither of these leaves any longer-lived identifier behind, and no other browser storage is used.
Where do the pages and their files come from?
Every page here is self-contained: fonts are embedded locally and no file needed to display a page is pulled from an outside host while it loads. The whole site is a set of static files served through a content delivery network, which handles the technical delivery of each request. The only place a visitor is sent elsewhere is through outbound links to third-party sites, and clicking one opens a separate destination that receives the request directly from the visitor's own browser.
What is missing from this site, on purpose?
There are no forms here, so there is nothing to submit and nothing typed to store. There is no third-party analytics service reading this traffic, no external subresource loaded from another host, and no contact channel of any kind on the site. No names, e-mail addresses, account identifiers or payment details are collected, and no account or login exists to tie any activity to a person.
What can this page not speak for?
This page describes only the mechanisms built into this domain. It has no knowledge of, and no control over, what happens on a site reached by following an outbound link — that separate destination keeps its own record of the visit directly from the browser. Readers should treat any page beyond this domain as a distinct destination with its own practices, and should avoid submitting personal details anywhere without checking what that destination itself states about handling them.