This page explains what happens to information when you read this site, based only on what was confirmed when the site was built. It covers the small visit count the site keeps, the single marker it places in your browser, how pages are delivered, and what happens when you follow a link elsewhere.
Visits
The site sends a small first-party visit beacon to itself, and only when you arrive from a search engine. The beacon records the page path, the type of event, the name of the referring search engine and, if you click an outbound button, the text on that button.
This data is used only to count page views and clicks on outbound buttons. It serves the site's own traffic counting and nothing else. It is not shared with advertising networks, data brokers or outside analytics services, and no third-party analytics run on these pages.
The beacon does not collect names, e-mail addresses, account identifiers or payment details. The site does not retain personal data about any individual visitor.
Browser
To avoid counting one page view twice, the site keeps a single flag in your browser for the current session. It holds no personal data and ends with your browsing session.
Apart from that flag, the site sets no other browser storage and no persistent identifier, and it does not use cookies. There is no login, no registration and no user account. The site also has no forms and no contact channels, so it never asks you to type in personal details. Because nothing about you is requested or stored, the site has no reason to ask for your consent, an account or any personal detail.
Delivery
The site is a set of static files served by a content delivery network. As the hosting provider, that network processes the technical data that comes with every request your browser makes.
Each page is self-contained, and its fonts are embedded locally. Every file a page needs comes from this domain, so no external subresources load and no outside host receives information while a page is displayed.
Some pages carry outbound links to third-party sites. Following one opens a separate site that receives the request directly from your browser and keeps its own record of it. This site does not control how those destinations handle your information, so review their own practices before sharing anything with them.
Limits
This page describes only the mechanisms confirmed during the build. It does not publish an operator identity or any practice beyond those listed above. It also does not state a retention period for the aggregate traffic counts.
Because the site offers no forms and no contact channels, there is no route here for sending personal information. If a page elsewhere claims to collect details on this site's behalf, treat it as unverified and do not submit personal data through it.