Scope of This Notice: verified mechanisms
This page describes only what the underlying build of this site has been confirmed to do. It does not describe a general privacy program, and it makes no claims beyond the specific mechanisms verified for this site. Where a practice is not listed below, it is because there is no confirmed basis for describing it, not because it has been overlooked.
Visit Recording: search referrals only
When a visitor arrives from 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 any clicked outbound button. This beacon is sent to an edge analytics endpoint that operates on the same domain as the site itself. The data collected this way is used only to count page views and clicks on outbound buttons, and for no other purpose. It is stored in the operator's own logs on that domain, alongside the country the content delivery network reports for the request — nothing more precise about location is collected. A single first-party cookie supports this process. It is set only when a visitor arrives from a search engine, holds nothing but the name of that search engine, lasts for up to one hour, and exists solely so that a later click on an outbound link can be matched to the search engine that brought the visitor here. A separate session view flag is kept in the browser for the duration of the visit so that a single page view is counted only once. Neither of these mechanisms creates a persistent identifier, and neither is used for anything beyond this basic counting.
Page Delivery: self-contained hosting
The site consists of self-contained pages served as static files through a content delivery network. Fonts used on the page are embedded locally rather than loaded from an outside source, and no other external subresources are called in while a page is displayed. This means that everything needed to render a page comes from this domain, with the content delivery network processing the technical details of each request in its role as hosting provider. No third-party analytics service receives any data from this site.
Outbound Links: redirect and separation
Some pages contain outbound links to third-party sites. Following one of these links starts with a first-party outbound redirect: the click first goes to a path on this domain, which then sends the visitor on to the partner site. Because of this design, any visit data stored on this domain is not shared with the partner at the point the link is followed — the partner's site receives the request directly from the visitor's browser once the redirect completes, and keeps its own separate record of that visit. This site has no influence over what a partner site does with that request, and this page makes no claim about the privacy practices of any destination reached through an outbound link.
What Is Not Present: forms and contact
This site has no forms, no contact channels, and no way for a visitor to submit personal details such as a name, an email address, an account identifier, or payment information. There is no login, no registration, and no user account of any kind. No third-party analytics service is used, and no browser storage beyond the single hour-long cookie and the session view flag described above is set — there is no other persistent identifier. Because none of these channels exist, the site has nothing to ask consent for beyond the minimal first-party counting already described, and no personal data is retained about any individual visitor. Readers should not attempt to submit personal information to this site, since no channel exists to receive or process it, and should treat any third-party destination reached through an outbound link as a separate site with its own separate record-keeping.