You are reading a small static information site, and this page explains what happens when you visit it. It describes the few things the site does, the many things it does not do, and where its responsibility ends once you follow a link elsewhere.
The site counts visits with a light first-party beacon
When you arrive from a search engine, the site records a small amount of visit information through its own first-party beacon. That record contains the page path, the type of event, the name of the referring search engine and, if you click an outbound button, the text of that button. If you reach a page some other way, this visit information is not collected.
The site uses this information to count page views and clicks on outbound buttons, as part of its own traffic counting. The record does not include your name, your e-mail address, an account identifier or payment details. The site has no login, no registration and no user account, so nothing ties a count to you as a person.
To keep a single page view from being counted twice, the site places one flag in your browser for the current session. That flag lasts only for the session and is not a persistent identifier. The site sets no other browser storage and does not use cookies.
This page describes only what the build of the site was verified to do. It does not state a retention period for the traffic counts, and it does not name an operator, a controller or a contact channel, because none of those details were verified. The site has no forms and offers no contact channel, so it never asks you for personal details, and you should not send personal data through any channel that claims to belong to it.
The confirmed absences are also why the site asks for no consent, no account and no personal detail. There is no third-party analytics service in the pages, and visitor data is not shared with advertising networks, data brokers or outside analytics services.
The hosting network and linked sites handle requests separately
The site is a set of self-contained static files served by a content delivery network. As the hosting provider, that network processes the technical data of every request your browser makes, which is a normal part of delivering any web page. This processing belongs to the hosting layer rather than to the visit counting described above.
Every file a page needs, including its fonts, comes from this same domain. The fonts are embedded locally and the pages load no external subresources. While a page is being displayed, your browser does not contact an outside host.
Some pages contain outbound links to third-party sites. When you follow one, your browser opens a separate site that receives the request directly from you and keeps its own record of it. This site does not control the privacy practices of those destinations, so read the policy of any site you visit before you share information there.
In short, a visit here involves a session flag, a narrow first-party count for search-engine arrivals and the ordinary request handling of the hosting network. Anything you do after leaving through an outbound link falls under the rules of the site you land on.