This page explains what happens to visit data on this forum. The site is built as a set of static files delivered through a content delivery network, and the notes below describe exactly what that build does and does not do. Nothing here is a promise about a company, a legal jurisdiction, or a way to contact anyone; it is a plain account of the mechanisms present in the site.
Visit Counting: Search Arrivals Only
When a visitor arrives from a search engine, the site records a small set of details through a first-party visit beacon sent to an edge analytics endpoint on this domain: the page path, the type of event, the name of the referring search engine and, if applicable, the text of a clicked outbound button. This happens only for that search-engine arrival case, not for every visit. The data is used solely to count page views and clicks on outbound buttons; the brief is explicit that this is its only purpose. No log or record described here is used for advertising, profiling or identification.
To support this counting, two small mechanisms operate in the browser:
| Mechanism | What it holds and how long |
|---|---|
| First-party search-referrer cookie | Set only when the visit comes from a search engine. Holds nothing but the search engine's name. Kept for up to one hour, then gone. Used only to match a later outbound-link click to that search engine. |
| Session view flag | Kept only for the current browser session. Its sole job is to stop a single page view being counted more than once. |
The site also notes the country that the content delivery network reports for a request, with nothing more precise about location. All of this visit data is stored in the operator's own logs, on this same domain — it is not passed to an outside analytics service.
Pages and Links: Self-Contained Delivery
Every page here is self-contained: the files a page needs — including its fonts, which are embedded locally rather than pulled from another server — all come from this domain. No outside host receives anything while a page is being displayed. That means simply loading and reading a page does not send data to a third party.
The site does contain outbound links to third-party sites. When such a link is followed, it first passes through a first-party outbound redirect on this domain before continuing to the partner. That redirect step is what lets the site match a click to the search engine that brought the visitor here, using the short-lived cookie described above. Once the visitor lands on the partner's own site, that partner receives the request directly from the visitor's browser and keeps its own separate record of it. Nothing stored by this site is handed to that partner, and this page has no basis to describe how that separate site handles data — it operates outside this build and outside this page's knowledge.
What Is Not Present: No Collection Beyond This
Several things are confirmed absent from this site, and they shape everything above. There are no forms anywhere on the site, so there is no channel for a visitor to type in a name, an email address or any other personal detail. There is no third-party analytics service of any kind — all counting happens in the operator's own logs, as described. There are no external subresources: nothing on a page is fetched from another server while it loads. And there are no contact channels built into the site.
Together, these absences are why the site asks for no consent banner, no account and no personal detail: there is nothing built to collect, and no third-party service to disclose it to. If you use one of the outbound links to reach a partner site, treat that destination as a separate service with its own separate practices, unrelated to anything described on this page.