This page explains what happens to visit data on this site, described only in the terms confirmed for this build. The site is a set of static files served by a content delivery network, which acts as the hosting provider and processes the technical details of every request it delivers.
Search Arrivals: Visit Signals
When a visitor arrives from a search engine, this site records a small set of details tied to that visit: the page path, the type of event, the name of the referring search engine, and the text of any clicked outbound button. This information is collected only under that search-arrival condition, not on every visit. It is used solely to count page views and clicks on outbound buttons, for the operator's own traffic counting, and for nothing else. The data is stored in the operator's own logs on the same domain. Alongside this, the content delivery network reports only the country associated with the request, with no more precise location detail collected.
Cookie And Session Flag: Short Retention
A single first-party cookie is set, but only when a visit arrives 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 match a later click on an outbound link back to the search engine that brought the visitor here. Separately, a session view flag is kept in the browser for the current session so that a single page view is counted once rather than multiple times. No other browser storage is set, and no persistent identifier is created by either mechanism.
| Mechanism | Purpose And Duration |
|---|---|
| First-party visit beacon / edge analytics endpoint | Records page path, event type, referring search engine, and outbound button text; used only for traffic counting; triggered only on search-engine arrivals |
| Search-engine cookie | Holds only the search engine name; lasts up to one hour; links a later outbound click to that search engine |
| Session view flag | Kept for the current session only; ensures one page view is counted once |
Outbound Links: Redirect Path
The pages on this site are self-contained, with locally embedded fonts, so nothing needs to be fetched from an outside host while a page is displayed. Outbound links to third-party sites use a first-party outbound redirect: the link first goes to a path on this domain before sending the visitor on to the partner site. This site does not share any stored visitor data with the partner during that redirect. Once the visitor lands on the partner site, that site receives the request directly from the visitor's 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 nothing about a partner's practices.
Missing Elements: No Collection
Several things are confirmed absent from this site, and together they explain why no consent request, account, or personal detail is ever asked for. There are no forms anywhere on the site, so nothing a visitor types is collected. There is no third-party analytics service reading visit data, and no external subresources are loaded from other domains, which is why every file a page needs comes from this same domain. There are no contact channels built into the site. The site does not collect names, e-mail addresses, account identifiers, or payment details, has no login or registration, and does not retain personal data about any individual visitor. It does not share visitor data with advertising networks, data brokers, or outside analytics services, and it uses no third-party or advertising cookies. Readers should not submit personal data through any channel connected to this site, since none is provided for that purpose, and should treat any partner site reached through an outbound link as a separate destination with its own separate record-keeping, outside what this page can describe.