You are reading a static information page. It explains, in plain terms, how this site is built and what happens on a technical level when you visit it.
Visit Counting: search arrivals
When a visitor arrives at this site by clicking through from a search engine, a first-party visit beacon records a small set of technical details: the path of the page that was opened, the type of event, the name of the referring search engine, and the text of any outbound button that was clicked. This happens only for visitors coming from a search engine — it is not triggered for other types of arrivals. The purpose of this beacon is limited to counting page views and outbound button clicks for this site's own traffic figures.
Session Flag: single count
To avoid counting the same page view more than once, the site keeps a single flag in the browser for the duration of the current session. This flag exists only so that one visit registers as one view rather than several. It is tied to the browsing session and is not designed to identify a person or to persist as a long-term identifier.
Page Delivery: self-contained files
Every page on this site is a self-contained file: the text, layout and fonts needed to display a page are all part of that page, with fonts embedded locally rather than fetched from an outside source. The whole site is hosted as static files on a content delivery network, which serves these files to your browser and, in doing so, processes the basic technical details of each request as any hosting infrastructure does. No separate outside host is contacted while a page is being displayed, because nothing on the page depends on a third-party subresource.
Outbound Links: redirect path
Some pages contain outbound links to third-party sites. When you follow one of these links, the click first goes through a first-party outbound redirect on this domain before sending you on to the partner site. That redirect step is what allows the outbound-click count described above to be recorded. Once you land on the partner's site, that site receives your request directly from your browser and keeps its own separate record of your visit, under its own practices, which this page has no part in and does not describe.
Data Practices: confirmed absences
This site has no forms of any kind, so there is nothing to fill in and nothing that could be typed in and submitted. It uses no third-party analytics service — the only counting described above happens through the first-party beacon and session flag on this domain. It loads no external subresources, meaning nothing on a page is pulled in from another company's server while you browse. It offers no contact channel, so there is no address, form or account through which a visitor could send personal details in the first place.
Because there are no forms and no contact channel, there is no interface on this site through which you would be asked to type in a name, an email address, or any other personal detail. If you ever encounter a request for that kind of information while browsing, treat it as belonging to whatever outside destination presented it, not to this site, and avoid entering personal data into channels you cannot verify.
Scope: this page only
What is written here describes this site's own static pages and the mechanisms listed above — nothing more. It does not speak for the partner sites reached through outbound links, and it does not describe or endorse how those separate destinations handle any data they receive once you arrive there. Each linked destination operates under its own separate practices, outside the scope of this page.