What happens when you visit this site?
When you arrive here from a search engine, a first-party visit beacon records a small set of details: the page path you landed on, the type of event that occurred, the name of the search engine that referred you, and the text of any outbound button you click. This happens only for visits that arrive from a search engine — browsing here directly or from another type 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, for the sole purpose of counting page views and clicks on outbound buttons. It is not used for anything beyond that traffic count.
Alongside this, the content delivery network that serves the site reports the country a request came from, with no finer location detail than that. A single first-party cookie is set only on visits arriving from a search engine, lasts for up to one hour, holds nothing but the name of that search engine, and exists so that a later click on an outbound link can be matched to the search engine that brought you here. A separate session view flag is kept in your browser only for the duration of your current session, and its only job is to make sure a single page view is not counted twice.
What does the site avoid collecting?
- No forms are present anywhere on the site, so there is nothing to submit and nothing typed by you to store.
- No third-party analytics services receive any data — all counting happens through the first-party mechanisms described above.
- No external subresources are loaded while a page is displayed. The pages are self-contained, and the fonts you see are embedded locally rather than fetched from another host.
- No contact channels exist on the site, so no personal details are collected through messages or enquiries.
- No names, e-mail addresses, account identifiers or payment details are collected, and no login or registration exists.
- No browser storage beyond the two items above is set, and no persistent identifier is created.
How does hosting and outbound linking work?
This site is a set of static files served by a content delivery network, which acts as hosting provider and processes the technical details of each request. Because everything the page needs comes from this domain, no outside host receives data while a page is being viewed.
Outbound links to third-party sites work through a first-party outbound redirect: the link first points to a path on this domain before sending you on to the partner site. This step does not pass any stored visitor data to the partner — once you follow the link, the partner site receives your request directly from your browser and keeps its own separate record of that visit.
What this page cannot speak for
This page describes only the mechanisms confirmed to operate on this domain. It has no visibility into, and makes no claim about, how a partner site handles data once you leave here through an outbound link — that site receives your request directly and applies its own practices, which this page cannot describe or vouch for. Because there are no forms and no contact channels on this site, there is no reason to submit personal information here, and nothing on this page should be read as an invitation to do so.