What happens when you arrive from a search engine?
When a visitor reaches this site by clicking through from a search engine, a first-party visit beacon sends a small record to an edge analytics endpoint on this same domain: 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 only fires for search-engine arrivals, not for every visit. The operator uses this record solely to count page views and clicks on outbound buttons, and for no other purpose. Alongside this, a first-party cookie is set only on search-engine arrivals, holding nothing but the name of the referring search engine, kept for up to one hour, and used only so that a later outbound-link click can be matched back to that search engine. A separate session view flag is kept in the browser for the current session so a single page view is counted once rather than multiple times as you browse.
What location or technical detail is recorded?
The content delivery network that serves this site's static files processes the technical details of every request as part of hosting the pages, and reports the country the request came from. Nothing more precise about location is recorded. This country detail and the visit data described above are stored in the operator's own logs on this domain; nothing is sent to an outside analytics service, advertising network, or data broker.
Why are there no forms or contact channels here?
This site has no forms, no contact channels, no login, and no registration. There is nothing here to fill in and nowhere on the site itself to submit a name, an e-mail address, or any other personal detail. Pages are self-contained, with fonts embedded locally rather than pulled from an outside host, so nothing loads from third-party subresources while a page is displayed. This is part of why the site does not ask for consent or an account: there is no submission point that would require one.
What happens when you follow an outbound link?
Outbound links on this site point to third-party destinations. Clicking one first passes through a first-party outbound redirect on this domain, which is how the button-click text mentioned above gets recorded, before sending you on to the partner site. The visit data stored in the operator's logs is not shared with the partner as part of that redirect; once you land on the third-party site, that site receives your request directly from your browser and keeps its own separate record of it, under its own practices. This page describes only what happens on this domain, not what a linked destination does after you leave.