Know What This Page Draws On
The statements below come only from the confirmed build behaviour of this site. Nothing here describes a plan, an intention, or a general industry practice — each line reflects a mechanism that was actually checked before publication.
- Claims are limited to what the build verified: a visit beacon, an analytics endpoint, a session flag, self-contained pages, locally embedded fonts, and outbound links routed through a first-party redirect.
- Anything not listed here — such as forms, third-party analytics, or contact channels — is confirmed absent, not merely unmentioned.
- If a reader reaches a third-party site through an outbound link, that destination is separate and is not described by this policy.
See How a Visit Is Recorded
When someone arrives at this site from a search engine, a first-party beacon sends a small set of details to an edge analytics endpoint hosted on this same domain. The endpoint only counts activity; it does not build a profile of the visitor.
- What is sent: the page path, the type of event, the name of the referring search engine, and the text of any outbound button that gets clicked.
- When it triggers: only for visits that arrive from a search engine — direct visits or other referral paths do not trigger it.
- What it is used for: counting page views and outbound-button clicks, and nothing beyond that traffic count.
- Where it is kept: in the operator's own logs, on the same domain, with no sharing to outside analytics services.
- Location detail: only the country reported by the content delivery network is recorded — nothing more precise.
Understand the Cookie and Session Flag
Two small, short-lived markers support the counting described above. Neither is used for advertising, profiling, or identifying a person across visits.
- A first-party cookie is set only when a visit arrives from a search engine. It holds nothing but the search engine's name, lasts up to one hour, and exists so a later outbound-link click can be matched to that search engine.
- A session view flag lives in the browser only for the current session, ensuring a single page view is counted once rather than repeatedly.
- No other browser storage is set, and no persistent identifier is created. Once the hour passes or the session ends, these markers are gone.
See How Pages and Links Are Served
The site is a set of static, self-contained pages served by a content delivery network, with fonts embedded locally rather than pulled from another host. This means no outside server is contacted while a page is being displayed.
- The content delivery network processes the technical details of each request as the hosting provider, including the country used for the location detail above.
- Outbound links to third-party sites first pass through a first-party redirect path on this domain before continuing to the partner. Stored visit data is not shared with the partner during this step.
- Once a link is followed, the partner site receives the request directly from the visitor's browser and keeps its own separate record. This page does not describe or control what happens there.
Know What Is Not Collected
Several categories of data collection are confirmed absent from this build, which is why the site asks for no consent, no account, and no personal detail.
- No forms exist anywhere on the site, so there is no channel through which a visitor's typed information could be submitted.
- No third-party analytics tools are used, and no third-party or advertising cookies are set.
- No external subresources are loaded — every file a page needs, including fonts, comes from this domain.
- No contact channels are offered on this site, and no names, e-mail addresses, account identifiers, or payment details are collected, stored, or retained.
Because there is no form and no contact channel here, readers should avoid entering personal details into any field that is not part of this site, and should treat any third-party destination reached through an outbound link as a separate site with its own separate record-keeping.