This page sets out what happens on this domain when a page is requested, what small amount of visit data is recorded, and how outbound links to other sites are handled. It covers only the mechanisms built into this site, not the practices of any partner site a reader might reach from here.
Understand What Is Recorded on Arrival
A first-party visit beacon fires when a visitor arrives from a search engine. It sends the page path, the type of event, the name of the referring search engine, and the text of a clicked outbound button to an edge analytics endpoint. This data is used for the operator's own traffic counting: how many times a page was viewed and how many times an outbound button was clicked. It is recorded in the operator's own logs on the same domain. Alongside this, the content delivery network reports only the country associated with a request, with no finer location detail.
Know What the Session Flag and Fonts Do
- Session view flag: a marker kept in the browser only for the current visit, so that a single page view is counted once rather than repeatedly. It does not persist beyond the session.
- Self-contained pages: each page is built to load its own files from this domain, so nothing is fetched from an outside host while the page is displayed.
- Locally embedded fonts: the typefaces used on the page are bundled with the site itself rather than pulled from an external font service.
- Static hosting on a content delivery network: the site is a set of static files served by the network, which handles the technical delivery of every request.
Follow How Outbound Links Are Handled
Outbound links on this site point first to a path on this same domain, which then redirects the visitor on to the third-party destination. This first-party outbound redirect step is where the text of the clicked button is captured for the traffic count described above. Once the redirect completes, the destination site receives the request directly from the visitor's browser and keeps its own separate record of that visit; this page has no part in what happens after that point and cannot describe it.
See What This Build Does Not Include
This site has no forms, so there is no field where a reader is asked to type in personal details. There is no third-party analytics service reading visit data, and no external subresources are loaded from other domains while a page is shown, which is why the self-contained pages point above holds. There are also no contact channels built into the site, so no message, request, or personal detail can be submitted through it. Readers should not attempt to send personal information through this site, since no channel exists to receive it. Any exchange of personal information happens only on the third-party destination after an outbound redirect, under whatever practices that separate site applies to requests it receives directly.