What does this site record when someone visits?
This site is a set of static files served by a content delivery network. A first-party visit beacon sends a small amount of data to an edge analytics endpoint on the same domain whenever a visitor 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 is used only to count page views and clicks on outbound buttons, and for nothing else. The content delivery network also reports the country the request came from, with no more precise location detail. That visit data is stored in the operator's own logs, on the same domain, as part of running the hosting infrastructure.
What does the cookie and session flag actually do?
- Search-engine cookie — set only when a visit arrives from a search engine, kept for up to one hour, holding just the name of that search engine. It exists so that a later click on an outbound link can be tied to the search engine that brought the visitor here. After an hour it expires on its own.
- Session view flag — kept only for the current browser session, so a single page view is counted once instead of multiple times while the page is open.
Neither of these holds a persistent identifier, and no other browser storage is set beyond them.
How do outbound links to partner sites work?
Pages on this site are self-contained: every file a page needs, including locally embedded fonts, is loaded from this domain, so no outside host is contacted while a page is displayed. Outbound links to third-party sites use a first-party outbound redirect — the link first goes to a path on this domain, which then sends the browser on to the partner. Once that redirect happens, 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 how this domain handles that redirect step; it has no visibility into, and makes no claim about, what the destination site does afterward.
What is missing from this site, and why does that matter?
There are no forms anywhere on this site, so nothing is typed in and submitted. There is no third-party analytics service reading visit data, and no external subresources are loaded on any page, meaning fonts, scripts and other assets all come from this domain rather than from outside providers. There are also no contact channels built into the site. Together these absences are why the analytics described above stays limited to a page path, an event type, a referring search engine name, and outbound button text, stored on this domain, rather than growing into anything broader.
Why doesn't this site ask for consent or an account?
Because the only data collected is the search-engine-triggered analytics and the one-hour cookie described above, and because there are no forms, no account system and no contact channel, this site has nothing that would require a visitor to register, log in, or agree to a data-sharing arrangement before reading it. If a reader chooses to follow an outbound link to a partner site, they are leaving this domain and entering a separate site with its own request handling, and any information a reader might consider giving out is a matter between that reader and the destination they have navigated to, not something this static page collects, forwards or holds.