This page explains what happens on this domain when a page loads, when an outbound link is followed, and nothing beyond that. It describes only the mechanisms that were confirmed to exist in this build.
Visits
A first-party visit beacon records a small set of details each time it is triggered, and it only fires for a visitor arriving from a search engine.
- Data recorded: the page path, the type of event, the name of the referring search engine, and the text of a clicked outbound button.
- Trigger: arrival from a search engine, or a subsequent click on an outbound button during that visit.
- Purpose: counting page views and outbound button clicks for the operator's own traffic figures, and nothing else.
- Storage: sent to an edge analytics endpoint and kept in the operator's own logs on this domain, alongside the country the content delivery network reports for the request. No more precise location is collected.
Cookie and session flag
Two small, short-lived markers support the counting described above. Neither identifies an individual visitor.
- A first-party cookie is set only when a visit arrives from a search engine, holds nothing but the name of that search engine, lasts up to one hour, and is used to link a later outbound click back to the search engine that brought the visitor here.
- A session view flag lives in the browser only for the current session, so a single page view is not counted more than once.
- No other browser storage is set, and no persistent identifier is created.
Pages and links
The pages themselves are built to avoid pulling in outside material, and outbound links are handled through a redirect on this domain before they leave it.
- Self-contained pages and locally embedded fonts mean every file a page needs comes from this domain; nothing is fetched from an outside host while a page is displayed.
- Outbound links to third-party sites first pass through a first-party outbound redirect on this domain, then send the visitor's browser directly to the partner site.
- The partner site receives that request directly from the visitor's browser and keeps its own separate record of it; this operator does not share the stored visit data with the partner, and does not control what the partner site does with the visit.
- The site is served as static files by a content delivery network, which processes the technical data of each request as the hosting provider.
What is absent
Several common collection points are confirmed absent from this build, which is why the site does not ask for consent, an account, or personal detail.
- No forms are present anywhere on the site.
- No third-party analytics or advertising cookies are used, and no visitor data is shared with advertising networks, data brokers, or outside analytics services.
- No external subresources are loaded; nothing needed to display a page comes from another domain.
- No contact channels are offered, and there is no login, registration, or user account, so no personal data such as a name, e-mail address, account identifier, or payment detail is collected, stored, or retained about any visitor.
Scope of this page
This page describes only the mechanisms verified for this domain's own pages. It says nothing about what happens after an outbound link carries a visitor to a partner site, since that site receives the request directly and keeps its own separate record, outside this operator's knowledge or control. Readers should treat any partner site reached through an outbound link as a separate destination with its own practices, and should not assume this page's description extends beyond this domain.