This page explains what happens to visit data on this site, a static set of pages served from a content delivery network, and how that differs from the separate sites reached through outbound links.
Understand What Is Recorded When You Arrive From a Search Engine
When a visitor arrives here by following a link from a search engine, the 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 happens only for arrivals from a search engine, not for every visit. The purpose is limited to counting page views and clicks on outbound buttons for the operator's own traffic figures. That data is written to the operator's own logs on this domain, and it is used for nothing beyond that counting. Alongside this, the content delivery network reports the country the request came from, with no finer location detail than that.
Know the Cookie and Session Flag in Plain Terms
- Search-engine cookie: set only when a visit arrives from a search engine, holds nothing but the name of that search engine, lasts up to one hour, and exists so a later click on an outbound link can be matched to the search engine that brought the visitor here.
- Session view flag: a marker kept in the browser for the current session only, used so a single page view is not counted more than once.
- No other browser storage: no persistent identifier and no other cookie or storage entry is set beyond these two.
See How Pages Are Served and Where Outbound Links Lead
Every file a page needs is self-contained on this domain, including locally embedded fonts, so no outside host is contacted while a page is being displayed. The content delivery network that serves these static files processes the technical details of each request in its role as hosting provider. Outbound links to third-party sites work through a first-party redirect: the link first goes to a path on this domain, then forwards the visitor to the partner. Stored visitor data is not shared with that partner during this step; once the redirect completes, the destination site receives the request directly from the visitor's browser and keeps its own separate record of it, under practices this page does not control.
Recognize What This Site Does Not Do
- No forms are present anywhere on this site.
- No third-party analytics services receive any data.
- No external subresources are loaded from other domains.
- No contact channels are offered on this site.
These absences are why the site collects no names, e-mail addresses, account identifiers or payment details, keeps no login or account system, and asks for no consent, no registration and no personal detail to be read or used.