What does this site actually collect from a visit?
This page describes only the mechanisms that were verified when this site was built. This site is a set of static files served by a content delivery network, which handles the technical delivery of every request as the hosting provider. When a visitor arrives from a search engine, a first-party visit beacon sends a small amount of information to an edge analytics endpoint on the same domain: the page path, the type of event, the name of the referring search engine, and the text of any clicked outbound button. This happens only for arrivals from a search engine, not for every visit. The data is used solely to count page views and clicks on outbound buttons, and for nothing else. It is stored in the operator's own logs on this domain, alongside the country the content delivery network reports for the request — nothing more precise about location is collected.
Two small browser-side mechanisms support this counting. A first-party cookie is set only when a visit arrives from a search engine, holds nothing but the name of that search engine, lasts up to one hour, and exists only so a later click on an outbound link can be linked to the search engine that brought the visitor here. Separately, a session view flag is kept in the browser for the current visit so that a single page view is counted once rather than multiple times. Neither of these stores a persistent identifier, and no other browser storage is set.
What does this site not do with visitor information?
This site has no forms, so there is no field for a name, an email address, or any other personal detail to be typed in. It uses no third-party analytics service, so no visit data is passed to an outside measurement provider. It loads no external subresources: every file a page needs, including its fonts, is self-contained and locally embedded, so nothing is fetched from another host while a page is displayed. There is no contact channel on the site, meaning no submission point of any kind is offered to visitors. Because of these absences, no personal data such as names, account identifiers, or payment details is collected, no login or account system exists, and no visitor data is shared with advertising networks, data brokers, or outside analytics services. No third-party or advertising cookies are used. Together, these absences are why the site does not ask for consent, does not require an account, and does not request any personal detail to be used.
What happens when a link leads away from this site?
The pages here include outbound links to third-party sites. Following one of those links opens a separate site that receives the request directly from the visitor's browser and keeps its own record of it. This page describes only what happens on this domain; it makes no claim about what a linked destination collects, stores, or does with a visit, since that is outside what this build verified. Anyone visiting a linked site should treat it as a separate destination with its own practices, and should be cautious about submitting personal data anywhere its handling has not been confirmed.