This page explains what happens on a technical level when someone visits this site. It describes only what the site's build actually does: a small amount of visit counting, a short-lived first-party cookie in one specific case, and outbound links to other sites. Nothing here should be read as a broader promise beyond these mechanisms.
What does this site record when a page loads?
When a page is viewed, a first-party visit beacon can send a small piece of information to an edge analytics endpoint on the same domain: the page path, the type of event, the name of a referring search engine if there is one, and the text of any outbound button that gets clicked. This only happens when a visitor arrives from a search engine result. The purpose is limited to counting page views and outbound clicks, and nothing else is done with it.
Is any of this kept in the browser?
A session view flag is kept in the browser only for the current visit, so that a single page view is not counted more than once while that visit lasts. This flag does not persist after the session ends and does not act as an identifier. 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 up to one hour, and is used solely to match a later outbound click to that same search engine visit.
Where does the visit data go and how long does it stay?
Any data collected through the visit beacon is stored in the operator's own logs on this domain, not passed to an outside analytics service. The hosting layer, a content delivery network, also sees the country associated with each request as part of serving the static files, but nothing more precise about location. Static hosting means every page is a self-contained set of files, including locally embedded fonts, so nothing is fetched from an outside host while a page is displayed.
What happens when an outbound link is followed?
Outbound links on this site pass through a first-party outbound redirect hosted on this domain before reaching the destination. This redirect step does not carry any stored visitor data to the partner site. Once the redirect completes, the destination is a separate, third-party site that receives the request directly from the visitor's browser and keeps its own separate record of that visit. This site has no influence over what that destination does with the request it receives.
What is confirmed not to happen here?
This site has no forms, so there is no channel for a visitor to type in a name, an e-mail address, or any other personal detail. There is no third-party analytics service reading this traffic, and no external subresources are loaded from other domains while a page is open. There is also no contact channel of any kind built into these pages. Together with the absence of any persistent browser storage or identifier, this is why the site does not ask for consent, an account, or any personal detail: the mechanisms in place are limited to short-lived, first-party counting of visits and clicks.
What can and cannot be said about linked destinations?
This page describes only the static site itself, not the practices of any third-party destination reached through an outbound link. Once a link is followed, the visitor is on a different site with its own separate handling of the request, outside the scope of anything verified here. Readers should treat each destination on its own terms and avoid submitting personal data anywhere without first checking how that specific destination handles it, since this page cannot speak for pages it does not control.