This site is a set of static files served by a content delivery network, and the pages are self-contained: everything a page needs to display comes from this domain, with no external subresources loaded from anywhere else. What follows describes only the mechanisms that were verified when this site was built.
Visits
When a visitor arrives from a search engine, a first-party visit beacon fires and sends a small amount of data to an edge analytics endpoint hosted on this same domain: 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 only happens for search-engine arrivals — visits that come from anywhere else do not trigger this collection. The data is used solely to count page views and clicks on outbound buttons for the operator's own traffic counting, and for nothing else. It is stored in the operator's own logs on this domain. The only location detail collected is the country the content delivery network reports for the request; nothing more precise about a visitor's whereabouts is captured.
Storage
A session view flag is kept in the browser for the current session only, so that a single page view is counted once rather than multiple times as the page is used. Separately, one first-party cookie is set, but only for a visit arriving from a search engine. It holds nothing but the name of that search engine, lasts for up to one hour, and is used only to tell which search engine a later click on an outbound link came from. No other browser storage is set, and there is no persistent identifier tracking a visitor across visits.
Fonts and links
Fonts on this site are locally embedded, meaning they are served from this domain rather than fetched from an outside font provider. Outbound links to third-party sites work through a first-party outbound redirect: a click first goes to a path on this domain and is then redirected to the partner site. That means the partner receives the click request directly from the visitor's browser and keeps its own separate record of it — stored visitor data on this domain is not shared with the partner when a link is followed. This operator has no control over what a partner site does with a visit once the redirect completes, and following any outbound link opens a separate site with its own practices.
What is not collected
This site has no forms, so there is no channel here for a visitor to submit names, e-mail addresses, or any other personal detail. There are no third-party analytics services, no advertising or tracking cookies, and no sharing of visit data with advertising networks or data brokers. There is no login, registration, or user account, and no contact channel operated from this page. Because of these absences, nothing here asks for consent, an account, or a personal detail — there is simply no mechanism collecting anything beyond the search-engine-triggered visit counting described above. If a reader follows an outbound link and reaches a form or a contact channel on another site, that exchange is between the reader and that separate site, governed by whatever practices it keeps on its own.
Summary
- Visit counting: page path, event type, referring search engine, clicked button text — search-engine arrivals only
- Session flag: browser-only, current session, prevents duplicate view counts
- Search-engine cookie: up to one hour, holds only the search engine name
- Country-level location from the content delivery network, nothing more precise
- No forms, no third-party analytics, no external subresources, no contact channels