Visits
This site records a small set of visit details when someone arrives from a search engine: 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 information is used only to count page views and clicks on outbound buttons, and for nothing beyond that. The records are kept in the operator's own logs on this domain, not passed to any outside analytics service.
Alongside this, the content delivery network that serves the site's files reports the country associated with each request. Nothing more precise about a visitor's location is collected. This happens as part of normal request handling by the hosting provider, not as a separate tracking step.
Storage
Two small pieces of browser storage support the counting described above:
- Search-referral cookie — set only when a visit arrives from a search engine, kept for up to one hour, and holding nothing but the name of that search engine. It is used to connect a later click on an outbound link back to the search engine that brought the visitor here.
- Session view flag — kept only 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. Once these two items expire or the session ends, nothing remains behind to identify a returning visitor.
Boundaries
The pages on this site are self-contained: every file a page needs, including its fonts, is served from this domain rather than pulled from an outside host while the page displays. Fonts are embedded locally rather than loaded from a third-party font service. The site itself is a set of static files delivered through a content delivery network, which is why no server-side processing of personal data happens here.
Outbound links to partner sites work through a first-party redirect: the link first points to a path on this domain, then forwards the visitor to the partner. This step lets the outbound-click count described above happen, but it does not hand any stored visitor data to the partner. Once the redirect completes, the partner site receives the request directly from the visitor's browser and keeps its own separate record of that visit. This page describes only what happens on this domain; it has no view into and no control over what a linked site does with a visit once the visitor lands there.
Absences
Several things that other sites often rely on are absent here, and that absence is part of why this page can stay short. There are no forms anywhere on the site, so there is no way to submit a name, an email address, or any other personal detail through it. There is no third-party analytics service reading visit data — everything described above stays in the operator's own first-party logs. There are no external subresources, meaning no scripts, fonts, or embeds are fetched from other domains while a page loads. And there are no contact channels built into the site, so no message, request, or personal detail can be sent to anyone through it.
Because there is nothing to submit and nothing collected beyond anonymous counting tied to search-engine arrivals, this site does not ask for consent, does not require an account, and does not build a profile of any individual visitor.
Reading this
Treat this page as a description of this domain only. If a linked destination asks for personal or financial information, that request is governed by whatever practices that separate site follows, not by anything written here. Readers should avoid entering personal data anywhere it is not clearly required, and should not assume that a link from this site carries any of the limited, anonymous visit-counting described above onto the destination it leads to.