Scope of this page: visit data
This page explains what happens on this site when a page is viewed and when an outbound link is followed. It covers the mechanisms that were verified when this site was built, and nothing beyond them. It does not describe the practices of any partner site reached through an outbound link, since those destinations run under separate control and keep their own separate records of anything a visitor does there.
Recording a visit: mechanism details
When a visitor arrives from a search engine, a first-party visit beacon sends a small piece of information to an edge analytics endpoint on this same domain: the page path, the type of event, the name of the referring search engine, and, if applicable, the text of a clicked outbound button. This is used only to count page views and clicks on outbound buttons, for this site's own traffic counting, and for nothing else. A session view flag is kept in the browser for the current visit only, so a single page view is not counted more than once. A separate first-party cookie is set only when the visit comes 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 in.
- Page content is served as self-contained pages with locally embedded fonts, so nothing loads from an outside host while a page is displayed.
- The site itself is a set of static files served through static hosting on a content delivery network, which processes the technical details of each request, including the country it reports for that request, as the hosting provider.
- Outbound links use a first-party outbound redirect: the link first goes to a path on this domain before sending the visitor on to the destination, which then receives the request directly and keeps its own record of it.
- Outbound links to third-party sites open pages this site does not run and cannot speak for.
What is not collected: confirmed absences
This site has no forms, so there is nothing here for a visitor to submit. It uses no third-party analytics and loads no external subresources, so no other party receives data while a page is being viewed. It offers no contact channels. There is no login, registration or account, no name, e-mail address, payment detail or other personal identifier collected, and no persistent identifier or other browser storage beyond the single short-lived session flag and one-hour search-engine cookie described above. Nothing gathered here is shared with advertising networks, data brokers or outside analytics services. Because of these absences, this site does not ask for consent, does not require an account, and does not need any personal detail from a reader to be used normally. Anyone visiting a linked destination should treat it as a separate site with its own separate handling of whatever is entered there.