This page explains what happens on this domain when a page loads, what small pieces of information are recorded, and where the reader's activity stops being visible to this site. It covers only the mechanisms confirmed for this build.
Visit Data
When a visitor arrives from a search engine, this site 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 happens through a first-party visit beacon sent to an edge analytics endpoint, and it is triggered only for search-engine arrivals — not for every visit. The data is used solely to count page views and clicks on outbound buttons, and it is stored in the operator's own logs on the same domain. Alongside this, a session view flag is kept in the browser only for the current session, so that a single page view is counted once rather than multiple times as the page is used.
Cookie
One first-party cookie is set, and 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 to the search engine that brought the visitor here. No other cookie, browser storage, or persistent identifier is set by this site.
Pages and Links
The pages themselves are self-contained: fonts are embedded locally and every file a page needs is served from this domain, hosted as static files on a content delivery network. No outside host is contacted while a page is displayed. Outbound links to third-party sites work through a first-party redirect on this domain before the visitor's browser is sent on to the partner site; that partner then receives the request directly and keeps its own separate record of it, outside this site's control or knowledge.
This site has no forms, no third-party analytics, no external subresources, and no contact channels. There is nothing to submit here, no account to create, and no personal detail requested at any point. Any information exchanged after following an outbound link happens on that separate destination, under its own practices, not on this page.