This page explains what happens on this site when a page is viewed and when an outbound link is followed. It covers only what this build actually does.
How visit counting works
This site records a small set of visit details, but only when a visitor arrives from a search engine. When that happens, it notes the page path, the type of event, the name of the referring search engine, and the text of any clicked outbound button. This information is sent to an analytics endpoint on the same domain and stored in the operator's own logs, alongside the country the content delivery network reports for the request — nothing more precise about location is collected.
- First-party visit beacon and edge analytics endpoint: triggered only on arrival from a search engine; used solely to count page views and clicks on outbound buttons; nothing else is done with this data.
- One first-party cookie: set only for a visit that arrives from a search engine, holding just the name of that search engine, kept for up to one hour, and used to link a later outbound-link click back to the search engine that brought the visitor here.
- Session view flag: a temporary marker kept in the browser for the current session only, so a single page view is not counted twice. It does not persist beyond the session and carries no identifying information.
- Self-contained pages and locally embedded fonts: every file a page needs, including fonts, is served from this domain, so no outside host is contacted while a page displays.
- First-party outbound redirect: following a link to a partner site first passes through a path on this domain before redirecting onward. No stored visitor data is shared with the partner in that process.
- Outbound links to third-party sites: once a redirect completes, the destination site receives the request directly from the visitor's browser and keeps its own separate record. This site does not control what that destination does with the visit.
- Static hosting on a content delivery network: the files are served by the content delivery network, which processes the technical details of every request in its role as hosting provider.
Confirm what this site does not do
Several things are confirmed absent from this build, and they explain why no consent request, account, or personal detail is ever asked for.
- No forms: there is nowhere on this site to type in a name, an e-mail address, or any other personal detail.
- No third-party analytics: all counting happens on this domain's own logs; no outside analytics service receives visit data.
- No external subresources: nothing on a page is loaded from another domain, so no other party sees a visitor's request while a page is open.
- No contact channels: this page offers no address, form, or channel for reaching anyone, and none should be assumed to exist.
Because no personal data such as names, account identifiers, or payment details is collected or stored, and because browser storage is limited to the one short-lived cookie and the session flag described above, this site keeps no persistent identifier tied to an individual visitor. Any site reached through an outbound link is a separate destination with its own practices, which this page cannot describe or vouch for.