This page explains what this site collects from visitors, how that information is used, and how it is kept apart from any outbound site a visitor chooses to follow. Everything below reflects only the mechanisms actually built into this site.
How arrival and clicks are counted
When someone reaches this site by following a link from a search engine, a first-party visit beacon fires and sends a small amount of data to an edge analytics endpoint: the page path, the type of event, the name of the referring search engine, and the text of any outbound button that gets clicked. This happens only for search-engine arrivals, not for every visit. The information is used solely to count page views and outbound button clicks for the operator's own traffic figures, and for nothing else. The data lands in the operator's own logs on the same domain, alongside the country the content delivery network reports for the request — nothing more precise about location is captured.
A single first-party cookie supports this counting. It is only set when a visitor arrives from a search engine, lasts up to one hour, and holds nothing but the name of that search engine, so a later click on an outbound link can be attributed to it. Separately, a session view flag is kept in the browser for the current visit so that one page load is only ever counted once. No other browser storage is set, and no persistent identifier is created.
How pages are served and where links lead
This site consists of self-contained pages with locally embedded fonts, served as static files from a content delivery network, which acts as the hosting provider and processes the technical details of each request. Because every file a page needs comes from this same domain, no outside host receives data while a page is being displayed, and there are no external subresources loading from anywhere else.
Outbound links to third-party sites work through a first-party outbound redirect: a click first goes to a path on this domain, which then sends the browser on to the partner site. Stored visitor data is not shared with the partner during that redirect. Once the visitor lands on the partner's own site, that site receives the request directly from the browser and keeps its own separate record of it. This site has no control over what a partner site does with that request, and this page describes only this site's own mechanisms, not the destination's practices.
What this site does not do
There are no forms anywhere on this site, so there is nothing to submit and nothing typed by a visitor is ever collected. There is no third-party analytics service reading any of this traffic data, no advertising or tracking cookies, and no data broker or ad network ever receives anything from this domain. There are no contact channels built into the site, so no personal detail such as a name, an e-mail address, or a payment detail is ever requested, gathered, or stored. Nothing collected here amounts to a personal account or an identity: there is no login, no registration, and no user account of any kind. Because of these absences, this site does not ask for consent, does not require an account, and does not need any personal detail from a reader to function.