This page explains what happens on this domain when a page loads, when a visitor arrives from a search engine, and when an outbound link is followed. It describes only what the build of this site verifies, and nothing beyond that.
How a Page View Gets Counted
When a page loads, a small beacon on this domain sends a short record to an analytics endpoint that also lives on this domain. That record can include the page path, the type of event, the name of the referring search engine when one is present, and the text of an outbound button if one was clicked.
This collection only happens when a visitor arrives from a search engine. The data is used solely to count page views and clicks on outbound buttons, for the operator's own traffic counting, and for nothing else. The country reported by the content delivery network is recorded, but nothing more precise about location is captured.
A session view flag is kept in the browser only for the current session, so that one page view is not counted twice. It does not persist beyond that session and does not identify an individual visitor.
What the Search-Engine Cookie Does
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 for up to one hour, and is used only to tell which search engine a later click on an outbound link came from.
No other browser storage is set, and no persistent identifier is created. Once that hour passes, the cookie's information is no longer available for that purpose.
Why Pages Load Without Outside Requests
Each page on this site is self-contained: the fonts it displays are embedded locally rather than pulled from an external font service, and no other outside file is fetched while a page is being shown. The site itself is a set of static files served from a content delivery network, which handles the technical delivery of every request as the hosting provider.
Because of this structure, there are no forms on this site, no third-party analytics running alongside the first-party beacon, no external subresources loaded from other domains, and no contact channel of any kind. These absences are the direct reason this site does not ask for consent, does not ask for an account, and does not ask for any personal detail: there is nothing built here to collect it.
What Happens When an Outbound Link Is Followed
Outbound links on this site point to third-party destinations. Following one of these links first passes through a first-party redirect path on this domain, which is how a click can be attributed to the search engine recorded in the short-lived cookie, before sending the visitor on to the outside site.
No stored visitor data is shared with the partner during that redirect. Once the browser reaches the outside site, that site receives the request directly and keeps its own separate record of the visit; this page describes only the redirect step on this domain, not what any linked destination does afterward.
Because this site has no contact channel, readers should not submit personal data through any outbound destination expecting it to be handled by this domain. Any information entered on a linked site is that site's own matter, separate from this static page.