This page describes only what this site's build actually does when a visitor loads a page or clicks a link. It does not describe any outside practice, and it does not cover the sites that outbound links lead to.
Visit Data And Search Arrivals
When a visitor arrives from a search engine, this site records a small set of details: the page path, the type of event, the name of the referring search engine, and the text of any outbound button that gets clicked. This happens only for search-engine arrivals, not for every visit. The data is stored in the operator's own logs on this domain and is used only to count page views and clicks on outbound buttons — nothing else. Alongside this, the content delivery network reports the country associated with the request, with no more precise location captured.
Cookie And Session Flag
- Search-referral cookie: set only when a visitor arrives from a search engine, holds nothing but the name of that search engine, lasts up to one hour, and exists so a later outbound-link click can be matched to the search engine that brought the visitor here.
- Session view flag: a temporary marker kept in the browser for the current session only, used to make sure a single page view is not counted more than once.
Neither of these stores a persistent identifier, and no other browser storage is set by this build.
How Pages Are Served
This site is a set of static, self-contained files served by a content delivery network. Each page loads its own fonts locally rather than pulling them from an outside source, and no other file needed to display a page comes from an outside host. The content delivery network processes the technical details of every request in its role as hosting provider, which is standard for this kind of static delivery and separate from the visit-counting described above.
Outbound Links
This site links out to third-party destinations. When one of these links is followed, the click first passes through a path on this domain and is then redirected to the partner site. No stored visitor data is passed to the partner through that redirect — the partner site receives the request directly from the visitor's browser once the redirect completes, and it keeps its own separate record of that visit. This site has no control over what a partner site does with that request or what it stores about it.
What Is Not Present
This build has no forms, so there is no channel here for a visitor to type in a name, an e-mail address, or any other personal detail. There is no third-party analytics service reading this site's traffic, and no external subresource is loaded while a page displays. There is also no contact channel on this site. Together with the absence of any login, registration, or account system, this is why the site asks for no consent, no account, and no personal detail: there is nothing built into it that collects, stores, or requests personal information beyond the limited, search-referral traffic counting described above. Readers should avoid submitting personal data anywhere on this domain, since no channel here is built to receive it, and any partner site reached through an outbound link operates under its own, separate record-keeping.