This page explains what this site's build actually does when a page loads and when an outbound link is followed. It does not describe any practice beyond what the build verifies, and it does not speak for the destinations reached through outbound links.
Scope of this notice: build verified
The statements below cover only mechanisms confirmed in this site's build. If a mechanism is not listed here, this page makes no claim about it in either direction. Readers should treat anything not described here as outside the scope of this notice rather than assume a particular practice is or is not present.
Arrival counting: search referral
When a visitor arrives from a search engine, a first-party visit beacon records the page path, the type of event, and the name of the referring search engine. This is triggered only on arrival from a search result and is used solely to count page views for this site's own traffic totals. A session view flag is kept in the browser for the current visit so that a single page view is not counted more than once during that session. The flag applies only to the current browsing session and serves counting accuracy rather than identification.
Outbound clicks: button text only
When a visitor clicks an outbound button, the same first-party mechanism records the text of that button along with the page path and event type. This is used only to count clicks on outbound buttons as part of the same traffic totals. Following an outbound link works through a first-party outbound redirect: the click first reaches a path on this domain and is then redirected to the outbound links to third-party sites. That separate site receives the request directly from the visitor's browser once the redirect completes and keeps its own record of that visit independently of this site.
Page delivery: static hosting
This site consists of self-contained pages with locally embedded fonts, so each page does not call out to other domains to render. It is served as static files through static hosting on a content delivery network, and the hosting provider processes the technical data of every request as part of delivering those files. No file needed to display a page is loaded from an outside host while the page is shown.
What this build does not include
This build contains no forms, so there is no field on this site through which a visitor can type in personal details. It contains no third-party analytics, no external subresources loaded from other domains while a page displays, and no contact channel such as an email address or message form. These absences are why the site does not ask for consent, does not create an account, and does not request any personal detail from a visitor.
Reader guidance: outbound destinations
Because this site has no forms and no contact channel, there is no first-party place on this domain to submit personal data, and readers should not expect one. Any site reached through an outbound link is a separate destination that receives requests directly from the visitor's browser and keeps its own records under its own practices, which this page does not describe and cannot speak for.