This page explains what happens to visit data on this site and why the site does not ask for personal details. It covers the mechanisms that were actually built into this site, and nothing beyond them.
What does this site collect when someone arrives from a search engine?
When a visitor lands on this site by following a link 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 information is sent to an edge analytics endpoint on the same domain and stored only in the operator's own logs.
This data is used solely to count page views and clicks on outbound buttons. It is not used for anything else, and it is not shared with advertising networks, data brokers or outside analytics services.
What does the cookie and session flag actually do?
A single first-party cookie is set only when a visit arrives from a search engine. It holds nothing but the name of that search engine, lasts for up to one hour, and exists so that a later click on an outbound link can be matched back to the search engine that brought the visitor here.
Alongside this, a session view flag is kept in the browser for the current visit only. Its sole purpose is to make sure a single page view is not counted more than once. Neither of these mechanisms sets a persistent identifier, and no other browser storage is used.
What does the site know about location and hosting?
The content delivery network that serves this site's static, self-contained pages reports the country a request comes from, and nothing more precise. Fonts used on the pages are embedded locally, so no font request leaves this domain. Because every file a page needs is loaded from this domain, no outside host receives information while a page is being displayed.
What happens when an outbound link is followed?
Outbound links to third-party sites on this domain pass first through a first-party outbound redirect before reaching the partner site. Stored visit 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 has no control over what a partner site does with that request, because the partner is a separate operator receiving the visitor's browser connection directly.
What this site does not do
This site has no forms, so there is nothing to fill in and nothing typed here is collected. It uses no third-party analytics and loads no external subresources, so no outside company receives data through the normal operation of a page. There are no contact channels on this site, so no personal details such as names or e-mail addresses are ever collected, stored or retained here.