Understand What This Page Can Verify
This page describes only the mechanisms confirmed in this site's build. It does not draw on outside policy language, and it does not describe any behavior beyond what was checked when the site was constructed. Where the build found no mechanism at all, that absence is stated plainly rather than filled in with assumptions.
The site is a set of static files delivered through a content delivery network. Every page is self-contained: the files a page needs to display are served from this domain, and locally embedded fonts are part of that self-contained delivery rather than pulled from an outside font service. There are no forms on this site, so there is no field where a visitor is asked to type in a name, an email address, or any other personal detail. There are no third-party analytics services connected to the pages, no external subresources loaded from other domains while a page displays, and no contact channel of any kind presented to the reader.
See How a Visit Is Counted
When a visitor arrives from a search engine, the build records a small set of technical details tied to that visit: the path of the page viewed, the type of event (such as a page view or an outbound button click), the name of the referring search engine, and the text of any outbound button that was clicked. This is triggered only on arrivals from a search engine, not on every visit. It is used only to count page views and outbound clicks; the build does not use this information for any other purpose.
To avoid counting the same page view twice, the browser holds one session view flag for the current visit. This flag applies only while that browsing session lasts and is meant to keep a single page view from being counted more than once during that time.
Follow an Outbound Link With This in Mind
Outbound links on this site use a first-party outbound redirect: the link first points to a path on this domain, which then sends the browser on to the partner site. The partner site itself is a separate destination outside this build. Once a visitor's browser reaches it, that site receives the request directly and keeps its own record of the visit, under practices this page has no way to verify. This page describes only what happens on this domain up to the point of that redirect.
Because there are no forms, no contact channel and no external subresources on this site, readers are not asked to submit personal data here at any point. Any information a reader chooses to share happens only after leaving this site, on a separate destination this page does not control and cannot describe.