This page describes only the data handling that this site's build actually performs. It covers how visits are counted, what is stored in the browser, how pages are delivered, and what the site does not do.
Visit Counting: how it works
When a visitor arrives from a search engine, this site 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 outbound button that gets clicked. This information is used only to count page views and outbound button clicks — nothing else. To stop a single page view from being counted more than once, the browser holds one flag for the current session; this flag lasts only as long as that session and is not a persistent identifier. Outside of this session flag, no other browser storage is set, and no cookie is used at any point.
Page Delivery And Links: technical facts
- The site consists of self-contained pages: everything a page needs, including its fonts, is embedded locally rather than pulled from another host while the page displays.
- Fonts are embedded directly in the build, so no separate font service is contacted.
- Hosting is provided as static files served through a content delivery network, which handles the technical side of each request as the hosting provider.
- Some pages contain outbound links to third-party sites. Following one of these links sends the request directly from the visitor's browser to that separate site, which keeps its own record of it. This site does not control or describe what happens after that point.
What Is Not Collected: confirmed absences
This site has no forms, so there is no channel here for submitting names, e-mail addresses, or any other personal detail through the site itself. It uses no third-party analytics service and loads no external subresources, meaning nothing on the page reaches out to another host while it is being viewed. There is also no contact channel presented on this site. Together with the absence of cookies and persistent identifiers described above, these confirmed absences are why this site does not ask for consent, does not require an account, and does not request any personal detail from readers. Any information exchange that happens after clicking an outbound link takes place on that separate destination, under its own practices, not under anything described on this page.