Visit Counting: search arrivals
When a visitor arrives on this site by following a link from a search engine, a small amount of visit data is recorded: the path of the page viewed, the type of event, the name of the referring search engine, and the text of any outbound button that gets clicked. This information is used only to count page views and outbound button clicks. It is not used for anything beyond this traffic counting, and it is not collected at all for visits that do not come from a search engine.
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 to make sure one page view is not recorded twice while a visitor is browsing. It does not identify the visitor, does not persist after the session ends, and no other browser storage or persistent identifier is set anywhere on the site.
Page Delivery: self-contained files
The site is built as a set of static, self-contained pages, with fonts embedded locally rather than pulled in from outside sources. These pages are served through a content delivery network, which handles the technical delivery of every request in its role as hosting provider. Because every file a page needs is loaded from this domain, no outside host receives anything while a page is being displayed, and there are no external subresources of any kind.
This also means there are no forms on the site and no third-party analytics tools running in the background. What is described above — path, event type, referring search engine, and button text, counted only on arrival from search — is the full extent of what this site observes about a visit.
Outbound Links: partner destinations
Some pages include outbound links to third-party sites. Following one of these links first passes through a path on this domain, which then redirects the visitor to the partner site. This first-party redirect step does not carry any stored visitor data or personal data along with it to the partner. Once the redirect completes, the partner site receives the request directly from the visitor's browser and keeps its own separate record of that visit. This site has no visibility into and no control over what a partner site does with that request, because the partner's practices belong entirely to that separate site.
No visitor data or personal data collected here is shared with advertising networks, data brokers, or outside analytics services, and none is shared with a partner site at the moment an outbound link is followed. The site does not use cookies to track visitors. It does not collect names, e-mail addresses, account identifiers, or payment details, and it has no login, no registration, and no user account. As a result, it does not store or retain personal information about individual visitors. There are also no contact channels built into the site itself.
Because there is no personal data collection, no account system, and no persistent identifier on this site, there is nothing here that requires a visitor's consent or personal detail to browse. Any information a reader chooses to enter on a linked partner site is handled under that site's own practices, not under anything described on this page. Readers should treat this page strictly as a description of how this static site itself behaves, separate from what happens after an outbound link leads elsewhere.