This page explains what limited visit counting happens here
This site records a small amount of visit information, and only under one specific condition: when a visitor arrives from a search engine. The purpose is narrow and stays that way.
- What is collected: the page path, the type of event, the name of the referring search engine, and the text of a clicked outbound button.
- When it triggers: only when the visit originates from a search engine referral.
- What it is used for: counting page views and clicks on outbound buttons, and nothing beyond that.
- How long it lasts: a single flag is kept in the browser for the current session, so one page view is counted once per visit; it does not persist beyond that session.
- What this means for the reader: no profile is built, no identifier follows a visitor between sessions, and the count exists purely as a traffic tally.
How the site is built and served
The pages themselves are static files, and the way they are built shapes what can and cannot happen when a page loads.
- Self-contained pages: each page carries what it needs without pulling in outside files while it is being displayed.
- Locally embedded fonts: fonts are packaged with the site itself rather than loaded from an outside font service, so no separate request for typography leaves the domain.
- Static hosting on a content delivery network: the files are distributed through a content delivery network, which processes the technical details of every request as the hosting provider handling that delivery.
- No external subresources: because every file a page needs comes from this domain, nothing is fetched from a third party while a page is on screen.
What happens when an outbound link is followed
Some pages link to outside destinations. The mechanism behind that link works in a specific, limited way.
- First-party outbound redirect: an outbound link first goes to a path on this domain, which then redirects the browser onward to the partner site.
- Outbound links to third-party sites: once redirected, the browser lands on a separate site that receives the request directly and keeps its own record of that visit.
- What is not shared: no stored visitor data is passed to the partner as part of this redirect.
- What this means for the reader: the destination site is a different operation with its own practices, which this page has no part in and no oversight of.
What this site does not do
Several common data-collection mechanisms are simply absent from this build. Stating them plainly is part of describing the site accurately.
- No forms: there is nowhere on the site to type in a name, an email address, or any other detail.
- No third-party analytics: the traffic counting described above stays first-party; no outside analytics service receives visitor data.
- No external subresources: nothing loads from another host while a page is displayed.
- No contact channels: there is no address, form, or account system through which a visitor could submit personal information to this site.
Because none of these mechanisms exist, the site has nothing to ask consent for beyond the limited, session-scoped counting described above. There is no account to create, no payment detail to enter, and no personal detail this page requests. Readers should not attempt to submit personal information through this site, since no channel here is built to receive it, and any personal data entered on a linked destination is a matter between the visitor and that separate site.