If you only want the short version, keep your personal details to yourself. This site never asks for them, and nothing on it needs them to work. The sections below explain the small amount of visit information the site does handle, and where its responsibility ends.
What does this site record when I visit?
The site uses a first-party visit beacon, which runs only on this domain and reports only to this site. It is triggered only when you arrive from a search engine. In that case it records four things:
- the path of the page you opened
- the type of event, meaning a page view or a click
- the name of the search engine that referred you
- the text of an outbound button, if you click one
This information is used solely to count page views and clicks on outbound buttons. It serves the site's own traffic counting and nothing else. The traffic counting is handled entirely by the site itself. For you, this means the site can tell that a page was viewed and a button was pressed, but it cannot tell who did it.
To keep that count accurate, the site places a single session view flag in your browser. Its only job is to make sure one page view is counted once rather than every time the page reloads. It lasts only for your current browsing session. The site keeps no other browser storage and no persistent identifier, so there is nothing that recognises you on a later visit.
Why am I never asked for consent, an account or my details?
There is simply nothing here that would need them. The site has no forms, no login, no registration and no user account. It also offers no contact channels, so there is no route through which you could hand over a name, an e-mail address or payment details.
The pages are also self-contained. Every file a page needs, including its locally embedded fonts, is delivered from this domain. The site loads no external subresources, so no outside host is contacted while you read a page.
This page describes only the mechanisms confirmed when the site was built. Anything not named here is outside what it can speak to.
Who else handles my request?
The site is a set of static files hosted on a content delivery network. Like any hosting provider, that network processes the technical data that comes with every request your browser makes, because it is needed to deliver the page to you. That handling is part of serving the files. It is separate from the visit beacon described above.
What happens when I follow a link to another site?
Some buttons and links lead to third-party sites. When you follow one, your browser opens a separate site, and that site receives the request directly from your browser. It keeps its own record of your visit under its own practices, which this site does not control.
Before you share anything there, especially personal or payment details, read that destination's own privacy information. On this site, the only trace of that click is the button text counted by the visit beacon, and only if you arrived from a search engine.