Read this before following any outbound link on this site: the page itself keeps almost nothing, and what it does keep is limited to counting visits and clicks. The rest of this page explains exactly what happens on this domain and what happens the moment you leave it.
Visit Counting Explains What Little Is Recorded
When a visitor arrives here from a search engine, the site notes the page path, the type of event, the name of the referring search engine, and the text of any outbound button that gets clicked. This happens through a first-party visit beacon that reports back to this domain only, and only when the arrival came from a search engine. The purpose is narrow: counting page views and counting clicks on outbound buttons. Nothing else is done with this information.
To stop a single page view from being counted twice, the site keeps one session view flag in the browser. This flag exists only for the current session, applies to that one visit, and does not persist as a longer-term identifier. It is not a cookie and it is not used to recognise a returning visitor.
Static Hosting Limits What the Site Can Hold
This site is a set of self-contained pages, with fonts embedded locally rather than pulled from another provider. It is served as static files through a content delivery network, which processes the technical details of each request in its role as the hosting provider. Because every file a page needs comes from this domain, there is no sharing of data with an outside host while a page is being displayed, and no external subresources are loaded from elsewhere.
No forms exist anywhere on the site, so there is nothing to submit and nothing to send. There are also no contact channels of any kind on this site, and no third-party analytics service is used alongside the first-party counting described above.
Outbound Links Work Through a Redirect on This Domain
Outbound links to third-party sites are set up as a first-party outbound redirect: the link points first to a path on this domain, which then sends the visitor on to the partner site. This step is why stored visitor data is not shared with the partner at the moment the link is followed — the redirect itself does not hand over any record kept here. Once the visitor's browser reaches the partner site, that site receives the request directly and keeps its own separate record of it. This site has no control over what a partner site does with that request, and this page describes only what happens up to the point of redirect.
No Accounts or Storage Means No Personal Data
There is no login, no registration, and no user account anywhere on this site, which is why no personal data such as a name, an e-mail address, an account identifier or payment details is ever collected. The site sets no cookies, stores nothing in other browser storage, and assigns no persistent identifier to visitors. It does not retain personal information about individual visitors, and it does not share visitor data with advertising networks, data brokers, or outside analytics services. These absences are the direct result of how the site is built, not a separate policy layered on top of it: a static, self-contained set of pages with no forms and no contact channels has no mechanism through which personal data could be gathered in the first place.