Visit Counting
Read this before following any link on the site: nothing here asks you to type in a name, an email address or any other personal detail, and there is no page that stores what you submit, because no page collects submissions at all. What follows describes only what the underlying files actually do when a page loads.
When a visitor arrives from a search engine, the site records a small amount of visit information: 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 only for arrivals from a search engine — browsing here directly or from another kind of link does not trigger it. The purpose is narrow: counting page views and clicks on outbound buttons, and nothing beyond that. This information is not used to build a profile of any individual, and it is not shared with advertising networks, data brokers or outside analytics services.
To stop a single page view being counted more than once, the site keeps one flag in the browser for the current session. That flag does not identify a visitor, does not persist once the session ends, and is not a cookie. No other browser storage is set, and no persistent identifier is created. Once the session ends, that flag is gone.
The pages themselves are self-contained: everything a page needs to display — including the fonts, which are embedded locally rather than pulled from an outside service — comes from this domain. No outside host is contacted while a page is being shown, so nothing about a visit is handed to a third party simply by viewing a page. The whole site is a set of static files served from a content delivery network, and that network necessarily processes the technical details of every request in its role as the hosting provider, in the same way any web host does.
Outbound Links
Some pages contain outbound links to third-party sites. Following one of these links does not send any stored visitor data to the destination: the link first passes through a path on this domain, which then redirects the browser to the partner site. The partner does not receive whatever was recorded here — it only receives the request that the visitor's own browser sends directly to it at the moment the link is followed, and it keeps its own separate record of that request. This site has no visibility into, and no control over, what the partner site does with that record, because it is a separate destination with its own practices once the redirect completes.
Beyond the mechanisms above, there is nothing else to describe. The site has no forms, so there is no field anywhere that captures typed input. It uses no third-party analytics service, so no outside company receives behavioural data from this domain. It loads no external subresources, so nothing on a page phones home to another host while that page is open. And it offers no contact channel, so no message, query or personal detail can be sent to the site through it. Together, these absences are why the site does not ask for consent, does not require an account, and does not need any personal detail from a reader to function. There is nothing to opt into and nothing to sign up for.
Any personal information a reader chooses to share happens only after leaving this domain, on a separate site that this page cannot speak for. Treat that destination's own practices, and its own record-keeping, as entirely distinct from what is described above.