This page describes only what this site's build actually does when someone visits it. It covers a small set of measured mechanisms and states plainly what the site does not do, so nothing here is guesswork or a generic template.
What does this site actually measure?
When a visitor arrives 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 clicked. This is sent to an edge analytics endpoint operated on the same domain as the site itself. The purpose is limited to counting page views and clicks on outbound buttons — nothing else is done with it. This collection is only triggered by arrivals from a search engine; visits that come from other sources do not generate this data. The information is stored in the operator's own logs on this domain, not passed to any outside analytics company.
What does the cookie and session flag do?
A first-party cookie is set only when a visitor arrives 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 visit only, so a single page view is counted once rather than multiple times. Neither of these is a persistent identifier, and neither survives much beyond the visit itself.
What does the hosting and page structure involve?
The site is a set of self-contained pages served through static hosting on a content delivery network. Fonts are embedded locally within the site rather than pulled from an outside source, and there are no external subresources loading from other domains while a page displays. The content delivery network processes the technical details of every request as the hosting provider, and it also reports the country associated with a request — nothing more precise about location is collected.
How do outbound links work on this site?
Outbound links to third-party sites do not go directly to the partner. Instead, a first-party outbound redirect on this domain handles the click first, then sends the visitor onward. Once that redirect happens, the partner site receives the request directly from the visitor's browser and keeps its own separate record of the visit. This site has no control over what a partner site does with that request, how long it keeps records, or what its own practices are. Anything that happens after the redirect belongs entirely to that separate destination, not to this page.
What does this site not collect at all?
There are no forms anywhere on this site, so there is no channel for a visitor to type in a name, an email address or any other personal detail. There is no third-party analytics service reading visit data, no external subresources loading from other domains, and no contact channel of any kind on the site. No names, account identifiers or payment details are collected or stored. There is no login, no registration and no user account. Because none of these mechanisms exist in the build, none of them are described here — this page does not claim otherwise anywhere else.
In short:
- Visit counting happens only for search-engine arrivals, using a page path, event type, referring search engine and outbound button text.
- One first-party cookie (up to one hour) and one session flag exist, both narrowly limited in purpose and lifespan.
- The site runs as static files on a content delivery network, with local fonts and no external subresources.
- Outbound links pass through a first-party redirect before reaching a separate partner site with its own separate records.
- There are no forms, no third-party analytics, no external subresources and no contact channels on this site.