Visit Data Collected: Search Arrivals Only
This page describes only what this site's build actually does when a page loads. It does not describe every possible way a website could collect data, and it does not describe the practices of any site reached by following an outbound link from here. Those are separate destinations with their own records of the visit, kept outside this domain.
This site collects a small amount of visit data, but only when a visitor arrives from a search engine. That data includes the page path, the type of event recorded, the name of the referring search engine, and the text of a clicked outbound button. It is gathered through a first-party visit beacon sent to an edge analytics endpoint that this domain controls, and it is used only to count page views and clicks on outbound buttons. The content delivery network that serves this site's static files also reports the country associated with the request, and nothing more precise about where a visitor is located. None of this is used for anything beyond the operator's own traffic counting.
A session view flag is kept in the browser only for the current visit, so a single page view is not counted twice. A first-party cookie is set only when a visitor arrives from a search engine; it holds nothing but the name of that search engine, lasts up to one hour, and is used solely so that a later click on an outbound link can be matched to the search engine that brought the visitor here. No other browser storage and no persistent identifier are set.
Site Structure: Static And Self-Contained
The following points describe how this site is built and what that means for a reader:
- Self-contained pages — every file a page needs, including locally embedded fonts, is served from this domain, so nothing else loads from an outside host while a page is being displayed.
- Static hosting on a content delivery network — the site is a set of static files served by a content delivery network, which processes the technical data of each request in its role as hosting provider.
- First-party outbound redirect — an outbound link first goes to a path on this domain before it is redirected to the partner site, so this site does not hand its own stored visitor data directly to that partner at the moment of the click.
- Outbound links to third-party sites — once a redirect completes, the destination site receives the request directly from the visitor's browser and keeps its own separate record of it. This site does not control what that destination does with the visit.
Alongside these mechanisms, several things are confirmed absent from this build. There are no forms anywhere on the site, so no visitor is asked to type in a name, an address, or any other personal detail. There is no third-party analytics service reading this traffic, no external subresources loaded from outside domains, and no contact channel offered on the site. There is no login, no registration, and no user account. No personal data such as names, e-mail addresses, account identifiers, or payment details are collected, stored, or retained about any individual visitor, and no visitor data is shared with advertising networks, data brokers, or outside analytics services. These absences are the reason the site does not ask for consent, does not require an account, and never requests a personal detail. Because there is no channel for submitting information here, a reader should not attempt to send personal data through this site expecting it to be received, stored, or acted upon.