This page describes what the build of this site actually does when someone visits it, covering how visits are counted, what a search-engine referral triggers, and how outbound links to other organisations' websites are handled.
What happens when a page loads?
This site is a set of static files served by a content delivery network, which acts as the hosting provider and processes the technical data of every request, including the country it reports for that request, without anything more precise about the visitor's location. Pages are self-contained: every file a page needs, including its fonts, is embedded locally and loaded from this domain, so nothing is fetched from an outside host while a page is being displayed. A first-party visit beacon sends a small amount of information to an edge analytics endpoint on the same domain: the page path, the type of event, the name of the referring search engine, and the text of a clicked outbound button. This only happens when a visitor arrives from a search engine. That data is used solely to count page views and clicks on outbound buttons, and for nothing else.
Is anything stored in the browser?
A session view flag is kept in the browser for the current session so that a single page view is counted once; it does not persist beyond that session. Separately, one first-party cookie is set, but only for a visit arriving from a search engine. It holds nothing but the name of that search engine, lasts for up to one hour, and is used only so that a later click on an outbound link can be matched to the search engine that brought the visitor here. No other browser storage is set, and there is no persistent identifier tied to a visitor across sessions.
How do outbound links work?
Outbound links on this site point to third-party organisations. A first-party outbound redirect means a link first goes to a path on this domain before sending the visitor on to the destination. Once that redirect happens, the destination site receives the request directly from the visitor's browser and keeps its own record of it, under its own practices, which this page does not describe or control.
What forms, contact channels or accounts does this site have?
There are no forms on this site, no contact channels, and no login, registration or account system of any kind. Nobody is asked to type a name, an email address, a payment detail or any other personal identifier into this site, because no field exists to receive one. Readers should not submit personal data through any channel presented on a linked destination while treating that submission as though it were happening on this site.
Does this site use outside analytics or advertising tracking?
No third-party analytics service is used, no external subresources are loaded, and no third-party or advertising cookies are set. The only measurement described above is the first-party visit beacon reporting to the first-party edge analytics endpoint, both on this domain. Visit data is not shared with advertising networks, data brokers, or outside analytics providers, and this page does not describe any mechanism that would send data to such parties, because no such mechanism exists in this build.
What does this mean for a reader?
Because there are no forms, no third-party analytics and no external subresources, visiting this site does not involve submitting anything or being tracked by outside services. This page is a static information page; it is separate from the third-party destinations reached through outbound links, and each of those destinations is responsible for what happens once a visitor lands there. Nothing on this page should be read as a statement about how long the operator's own logs are kept.