You are reading a description of how this site behaves technically when you visit it. Nothing here asks you to sign up, log in, or hand over any personal detail, and the paragraphs below stay close to what the build of this site actually does.
Visit Recording: Search Arrivals
When you arrive here by clicking through from a search engine, the site notes a small set of details: the page path you landed on, the type of event that happened, the name of the search engine you came from, and the text of any outbound button you click. This happens only for that search-engine arrival case — visits that begin another way do not trigger this recording. The data is used only to count page views and outbound-button clicks, nothing more. It is kept in the operator's own logs on this same domain, not sent anywhere else. Alongside this, the content delivery network that serves the site notes the country your request appears to come from, and nothing more precise about your location.
Cookie And Session Flag: Short-Lived
To tell which search engine a later outbound click came from, the site sets one first-party cookie, but only when your visit began at a search engine. It holds nothing but the name of that search engine, lasts no longer than one hour, and is not used for anything beyond linking a click back to the referring search engine. Separately, a flag is kept in your browser for the current session only, so that a single page view is counted once rather than several times. Neither of these mechanisms stores a persistent identifier, and no other browser storage is set.
Page Delivery: Static And Self-Contained
The site is a set of static, self-contained pages served by a content delivery network, with fonts embedded locally rather than pulled from another host. Because of this, no outside server is contacted while a page is being displayed — everything a page needs, including its type styling, comes from this same domain. The content delivery network itself processes the technical details of every request as the hosting provider, which is a normal part of serving files this way, not a separate collection made by the site.
Outbound Links: Redirected And Separate
Some links on this site point to third-party destinations. When you follow one, it first goes to a path on this domain and is then redirected onward — this first-party redirect step is what allows an outbound click to be counted, as described above. No stored visitor data is passed to the destination as part of that redirect. Once you land on the outside site, that site receives your request directly from your browser and keeps its own separate record of it. This site has no visibility into and no control over what that destination does with your visit, and this page describes only this domain, not any site you reach by following a link from it.
What Is Not Collected: Confirmed Absences
This site has no forms, so there is no field anywhere on it for you to type a name, an email address, or any other personal detail into. It uses no third-party analytics service — the counting described above happens entirely in the operator's own first-party logs. It loads no external subresources, meaning no script, image, or style file is fetched from another domain while a page renders. And it offers no contact channel of any kind on this domain. Together, these absences are why the site does not need to ask for your consent, does not create an account for you, and does not ask you to submit any personal information in the first place. If you ever find yourself on a form or a contact field while browsing from a link that started here, know that you have already left this domain and are dealing with a separate site's own practices, not this one's.