This page describes only the data mechanisms that were verified when this site was built. It does not describe any practice beyond what is listed here, and it does not ask for personal detail, consent, or an account.
Visit counting: search arrivals
When a visitor arrives from a search engine, a first-party visit beacon records 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 only fires for search-engine arrivals, not for every visit. The data travels to an edge analytics endpoint kept on the same domain and is used solely to count page views and clicks on outbound buttons for the operator's own traffic figures. Alongside this, a first-party cookie is set only for a search-engine visit, holds nothing but the name of the search engine, lasts up to one hour, and exists only so that a later outbound-link click can be matched to the search engine that brought the visitor in.
Session behaviour: single count
A session view flag is kept in the browser for the current session only. Its single purpose is to make sure one page view is counted once rather than multiple times while that session lasts. It does not persist beyond the session and does not identify the visitor.
Page delivery: self-contained files
Each page on this site is self-contained: everything a page needs to display loads from this domain, including locally embedded fonts, rather than pulling files from outside hosts while the page is shown. The site itself is a set of static files served by a content delivery network, which handles the technical delivery of every request and, as part of that hosting role, sees the country associated with the request. No more precise location detail is collected.
Outbound links: redirect step
Some links on this site point to third-party sites. Before reaching the partner, an outbound link passes through a first-party outbound redirect hosted on this domain. That redirect step is how a click can be tied to the search engine recorded earlier. Once the redirect completes, the destination site receives the visitor's request directly from their browser and keeps its own separate record of that visit — this page has no part in what happens after that point.
Confirmed absences: no collection
This site has no forms, so there is no field for a visitor to type a name, address, or any other detail into. It does not load third-party analytics and does not use third-party or advertising cookies. It does not pull in external subresources from other hosts while a page is on screen. It has no contact channel of any kind — no address, no submission point, nowhere to send a message. These absences are why the mechanisms above exist as they do: there is no account system, no login, and no stored profile behind them.
Scope of this page: what remains unstated
Beyond the mechanisms and absences listed above, this page makes no further claim. It does not describe what happens on a linked destination once a visitor leaves this domain, and it cannot speak for how a partner site handles a request it receives directly. Anyone following an outbound link is moving to a separate site with its own separate handling of that visit, outside anything this page can confirm.