Scope of this record: build-verified only
This page describes what the build of this site has verified about visit handling, and nothing beyond that. It covers a small set of mechanisms that were confirmed at build time: a first-party visit beacon, a session view flag, self-contained pages, locally embedded fonts, outbound links to third-party sites, and static hosting on a content delivery network. Anything not on that list is left undescribed here rather than assumed, so this page does not attempt to speak for practices, storage, or handling that were not part of the verified build.
Visit counting and session flag: how it works
When a visitor arrives at this site by way of a search engine, a first-party visit beacon records a small set of details: the page path, the type of event, the name of the referring search engine, and the text of an outbound button if one is clicked. This happens only on that search-engine arrival path, not on every visit. The purpose is limited to counting page views and outbound button clicks for this site's own traffic totals; the data is used for that counting and for nothing else described in the build. Alongside this, a single flag is kept in the browser for the current session, and its only job is to make sure one page view is counted once rather than multiple times while that session lasts; it does not persist beyond the session.
The pages themselves are self-contained, meaning each one carries what it needs to display without pulling in outside subresources while it loads. Fonts are embedded locally as part of the build rather than fetched from an external font service. The site is served as static files through a content delivery network, which handles the technical delivery of each request as the hosting layer; this is a hosting mechanism, not a separate collection of visitor content. Where the site links out to third-party destinations, following one of those links opens a separate site that receives the visitor's request directly, and whatever happens on that separate site is outside what this build can describe.
Absent mechanisms: forms and channels
The build confirms that this site has no forms, no third-party analytics, no external subresources, and no contact channels. There is nowhere on this site to type in a name, an email address, or any other detail, and no submission point exists for one to be sent anywhere. No outside analytics service is loaded alongside the first-party visit beacon described above, and no external subresource is fetched to render any page. Because none of these channels exist, this site does not ask for consent, does not require an account, and does not request personal details of any kind — there is simply no mechanism built into it that would collect or transmit them.
This absence is also why the site cannot offer a way to reach an operator, request a copy of anything, or ask a question through the site itself. If a reader interacts with a third-party destination reached through an outbound link, that interaction is handled entirely by that separate site under its own practices, and this page does not describe or vouch for those practices in any way. Readers who want to keep any personal detail private should be cautious about what they submit on any site reached through an outbound link, since this privacy page only speaks to the static pages hosted on this domain and stops at the point where an outbound link is followed.