When you visit this site, only a limited amount of technical activity is recorded, and only under specific conditions. This page sets out exactly what is gathered, what triggers it, and what is never collected at all.
Visit Tracking: Search Arrivals Only
A first-party visit beacon sends a small record to an edge analytics endpoint, but only when you arrive here from a search engine. That record can include the page path, the type of event, the name of the referring search engine, and the text of any outbound button you click. It exists solely to count page views and clicks on outbound buttons, and it is stored in the operator's own logs on the same domain. The content delivery network that serves this site also reports the country a request came from, with nothing more precise about your location. A session view flag is kept in the browser only for the current visit, so that a single page view is not counted twice; it does not persist beyond that session. A separate first-party cookie is set only for search-engine arrivals, holds nothing but the name of that search engine, and expires within an hour, used only to match a later outbound click to the search engine that brought you here.
Page Delivery: Self-Contained Files
Every page here is self-contained, with locally embedded fonts and no external subresources loaded from other hosts. The site itself is a set of static files served by a content delivery network, which handles the technical delivery of each request as the hosting provider. Because nothing on the page pulls from outside domains, no outside party receives data simply from a page being displayed.
| Present on this site | Not present on this site |
|---|---|
| First-party visit beacon (search arrivals only) | Third-party analytics |
| Session view flag | Persistent identifiers or other browser storage |
| Locally embedded fonts | External subresources |
| Outbound links to third-party sites | Forms or contact channels |
Outbound Links: Redirect Mechanics
Outbound links on this site pass first through a path on this same domain before redirecting to the third-party destination. Stored visit data is not shared with that partner as part of this redirect. Once you follow the link, the destination site receives your request directly from your browser and keeps its own separate record of that visit; this site has no control over what that partner site does with it. There are no forms here and no contact channels, so nothing you might otherwise type into a message or a submission field is collected, because no such field exists. No personal details, names, or identifiers are gathered at any point, and none are retained for individual visitors. If you reach a third-party site through an outbound link, treat it as a separate destination with its own separate practices.