This page explains what happens to visit data on this site, and it explains what does not happen. Everything below reflects how the pages are actually built and served.
Understand What Your Visit Triggers
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 information is sent through a first-party visit beacon to an edge analytics endpoint and stored in the operator's own logs on the same domain, not on any outside server. It is used only to count page views and clicks on outbound buttons, and for nothing else. Alongside this, a session view flag is kept in the browser for the current session, so a single page view is only counted once. A first-party cookie is set only when a visit arrives from a search engine; it holds nothing but the name of that search engine, lasts up to one hour, and is used only to tell which search engine a later outbound click came from. The content delivery network that serves this site's static files also reports the country the request came from, with no more precise location involved.
Follow How Outbound Links and Fonts Work
Pages are self-contained, with fonts embedded locally rather than pulled from an outside host while a page displays. Outbound links to partner sites first pass through a first-party redirect on this domain before reaching the outside destination. Once a partner site is reached, that site receives the request directly from the visitor's browser and keeps its own separate record of it; this page does not describe and cannot control what happens there.
Know What This Site Does Not Do
There are no forms on this site, no third-party analytics, no external subresources loaded into pages, and no contact channels. No names, e-mail addresses, account identifiers, or payment details are collected. No login, registration, or user account exists, and no persistent identifier or other browser storage is set beyond the single short-lived cookie described above. Because of these absences, no consent request, account, or personal detail is ever asked for.