This page explains what happens with visit data on this site, a set of static files served by a content delivery network, and how that differs from the separate sites reached through outbound links.
Understand what gets counted when you arrive from a search engine
When a visitor arrives on this site from a search engine, a first-party visit beacon 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 happens only for arrivals from a search engine — browsing the site directly or from another kind of link does not trigger this collection. The data travels to an edge analytics endpoint and is stored in the operator's own logs on the same domain, alongside the country the content delivery network reports for the request. Nothing more precise about location is collected. All of this exists for one purpose: counting page views and clicks on outbound buttons. It is not used for anything else.
Know what the cookie and session flag actually do
One first-party cookie is set, but only on a visit arriving from a search engine. It holds nothing but the name of that search engine, lasts up to one hour, and exists so that a later click on an outbound link can be matched to the search engine that brought the visitor here. Separately, a session view flag is kept in the browser for the current session only, so that a single page view is counted once rather than multiple times. Neither of these is a persistent identifier, and no other browser storage is set. Once the hour passes or the session ends, this data is gone.
See how the pages themselves are built and delivered
The pages on this site are self-contained: every file a page needs, including locally embedded fonts, comes from this domain. Nothing is fetched from an outside host while a page is displayed, so no external subresource loads and no third-party analytics script runs anywhere on the site. The site itself is static hosting on a content delivery network, which processes the technical data of every request in its role as the hosting provider.
Follow what happens when you click an outbound link
Outbound links to third-party sites on this site work through a first-party outbound redirect: the link first goes to a path on this domain, then redirects to the partner. Stored visitor data is not shared with the partner at that point. Once the redirect completes, the partner site receives the request directly from the visitor's browser and keeps its own separate record of that visit. This site does not control what a partner site does with that request, and the practices of any linked destination are entirely separate from what is described on this page.
Recognise what this site does not do
There are no forms anywhere on this site, so there is no channel for submitting names, e-mail addresses, account details, or payment information, and none of that is collected. There are no contact channels on this site either. No third-party analytics tools are used, no advertising or tracking cookies are set, and no data is shared with advertising networks, data brokers, or outside analytics services. Nothing is retained about an individual visitor beyond the short-lived cookie and session flag already described, and there is no login, registration, or user account of any kind. Because none of that machinery exists, this site does not ask for consent, does not ask you to create an account, and does not ask for any personal detail. If you follow an outbound link and reach a partner site, treat that site as a separate destination with its own separate practices, distinct from anything stated here.