You are reading the privacy page for this site, and it describes only the mechanisms that were verified when this site was built. It does not describe practices found on other sites, and it does not describe anything beyond what is listed below.
Understand What This Page Can Speak To
This page is limited to the mechanisms confirmed in this site's build. Where a mechanism is not listed here, this page says nothing about it, one way or the other. Treat anything not mentioned below as outside the scope of what this page addresses.
Read How the Visit Beacon and Session Flag Work
When a visitor arrives at this site from a search engine, a first-party visit beacon fires and passes along the page path, the type of event, the name of the referring search engine, and the text of any outbound button that gets clicked. This happens only on arrivals from a search engine; visits that come in another way do not trigger it. The purpose of this beacon is narrow: counting page views and counting clicks on outbound buttons, and nothing else.
Alongside the beacon, a session view flag is kept in the browser for the duration of the current session. Its only job is to make sure a single page view is counted once rather than multiple times while that session is active. This flag does not persist beyond the session and does not act as a lasting identifier.
See How Pages, Fonts, and Outbound Links Are Handled
Every page on this site is self-contained: the files a page needs to display are served from this domain, so nothing is fetched from an outside host while a page is being shown to you. Fonts used on the page are embedded locally as part of the same self-contained delivery, rather than being pulled in from an external font service.
Outbound links to third-party sites work through a first-party redirect: clicking a link first passes through a path on this domain and is then redirected to the destination. That redirect step does not hand stored visitor data to the destination — the destination receives only the request that the visitor's own browser sends directly to it once redirected, and it keeps its own separate record of that request. This site has no influence over how that separate destination handles what it receives.
The whole site is delivered as static files through a content delivery network. As the hosting layer, that network necessarily processes the technical details of each request in order to serve the files — that is simply how static hosting works, distinct from the visit beacon described above.
Know What Was Confirmed Absent
Alongside the mechanisms above, the build confirmed a specific set of absences:
- No forms are present anywhere on this site, so there is no field for you to fill in and submit.
- No third-party analytics services are embedded; the only counting mechanism is the first-party beacon described above.
- No external subresources are loaded while a page displays — this matches the self-contained pages and locally embedded fonts already described.
- No contact channels exist on this site.
These absences are the reason this site does not ask you for consent, does not ask you to create an account, and does not ask for any personal detail. There is no login, no registration, and no account to manage. If you follow an outbound link from this site, you are leaving for a separate destination that operates under its own practices, and anything you choose to share there is a matter between you and that destination, not this page.