Understand What Happens When You Visit
When you land on this site from a search engine, a first-party visit beacon sends a small record to an edge analytics endpoint: the page path, the type of event, the name of the referring search engine, and, if you click one, the text of that outbound button. This happens only for arrivals from a search engine, and the data is used solely to count page views and outbound button clicks for this site's own traffic figures.
A single first-party cookie supports this counting. It is set only on a search-engine arrival, holds nothing but the name of the referring search engine, and expires within an hour. Alongside it, a session view flag lives briefly in your browser so a single page view is not counted twice. Neither item carries a persistent identifier, and nothing else is written to browser storage.
Know What Is Not Collected or Shared
This site has no forms, so there is nothing for you to submit and nothing entered by hand for it to store. There are no contact channels here either, which means no name, e-mail address, or message ever passes through this page.
There is no third-party analytics running alongside the first-party beacon described above, and no external subresources load while a page is displayed: fonts are embedded locally and every file the page needs comes from this domain. No visitor data is shared with advertising networks, data brokers, or outside analytics services, and no third-party or advertising cookies are used.
Recognise the Limits of This Explanation
What follows applies specifically to the mechanisms above and to nothing beyond them. The country your request appears to come from, as reported by the content delivery network hosting these static files, is logged as part of ordinary technical processing; nothing more precise about your location is recorded. No names, account identifiers, or payment details are ever part of this picture, because none of those fields exist on this site.
Follow an Outbound Link With This in Mind
Outbound links here use a first-party outbound redirect: the link first opens a path on this domain, then forwards you to the third-party site. That first-party step does not hand your stored visit data to the destination; the partner site instead receives your request directly from your browser once you land there, and keeps its own separate record of that visit. This page has no influence over what that destination does with your data, and you should treat anything you enter there as governed by that site's own practices, not by anything described here.