This page explains what happens to visit data on this site, built from a fixed set of confirmed mechanisms rather than general promises. It covers what is measured, what is stored, and what is never collected.
Measurement
This site records a small set of visit details: the page path, the type of event, the name of a referring search engine, and the text of a clicked outbound button. This information is captured only when a visitor arrives from a search engine, and it is sent through a first-party visit beacon to an edge analytics endpoint on this domain. The sole purpose of this collection is to count page views and clicks on outbound buttons for the operator's own traffic figures. It is not used for any other purpose.
Storage
- Session view flag — a marker kept in the browser only for the current session, so that a single page view is not counted more than once. It does not persist beyond the session.
- Search-engine cookie — one first-party cookie, set only when a visit arrives from a search engine, holding nothing but the name of that search engine. It lasts up to one hour and is used solely to match a later outbound-link click to the search engine that brought the visitor here.
- Location detail — the country reported by the content delivery network for the request. Nothing more precise about location is collected.
- Server logs — visit data described above is stored in the operator's own logs on this domain, not passed to an outside analytics service.
Delivery
This site is built from self-contained pages with locally embedded fonts, served as static files through a content delivery network. Because pages are self-contained, nothing needed to display a page is requested from an outside host while that page loads. The content delivery network processes the technical details of each request in its role as the hosting provider, which is how the country-level location detail above is reported.
Outbound links
Some links on this site point to third-party destinations. When one of these is followed, the link first passes through a first-party outbound redirect on this domain before continuing to the partner site. This redirect step is part of how a click is matched to the referring search engine described above. 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 pass any stored visit data to the partner, and it has no control over what the partner site does with the visit it receives.
What is not collected
This site has no forms, so there is no field for a visitor to submit personal data through. It uses no third-party analytics service and loads no external subresources, so no outside party receives data while a page is displayed. It offers no contact channel of any kind. There is no login, no registration, no user account, and no persistent identifier stored in the browser beyond the session flag and the one-hour cookie described above. No names, e-mail addresses, account details or payment details are collected, and no personal information is retained about individual visitors. Because none of these channels exist, the site has nothing to ask consent for beyond the narrow, short-lived cookie already described, and nothing to hold that would require an account or a personal-data request.