You are reading a static page served from a content delivery network, and what follows describes only what actually happens when you visit it. Nothing here is inferred or assumed beyond the mechanisms built into the site.
What gets counted: visit data
When you arrive at 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 the text of any outbound button you click. This only fires for search-engine arrivals, not for every visit. The data is used solely to count page views and clicks on outbound buttons, and it is stored in the operator's own logs on this domain. The content delivery network also reports the country your request came from, with no finer location detail than that.
To avoid counting the same page view twice, a session view flag is kept in your browser for the current visit only. Separately, a first-party cookie is set — but only when you arrive from a search engine — holding nothing except the name of that search engine. It lasts up to one hour and exists only so that a later click on an outbound link can be matched back to the search engine that brought you here. No other browser storage and no persistent identifier are set.
Pages and links: source and destination
The pages themselves are self-contained: fonts are embedded locally and no file needed to display a page is pulled from an outside host, so nothing is shared with a third party while a page loads. Outbound links to third-party sites work through a first-party redirect — the link first passes through a path on this domain before sending you onward. That redirect does not carry any stored visitor data to the partner site; once you land there, that separate site receives your request directly from your browser and keeps its own record of it, under its own practices, which this page cannot describe or control.
| On this site | On a linked destination |
|---|---|
| Visit data logged only from search-engine arrivals | Handled entirely by that separate site |
| One short-lived first-party cookie | Not covered by this cookie or this page |
There are no forms, no third-party analytics, no external subresources, and no contact channels on this site. Nothing beyond the traffic counting described above is collected, so no names, account details, or payment information are ever gathered or retained here.