Read this page before you assume the site tracks you the way most websites do. It does not ask you to accept cookies, create an account, or hand over any personal detail, because none of those things exist here to begin with.
What data does a visit actually generate?
When someone arrives from a search engine, the site records a small set of details through a first-party visit beacon: 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, not for every visit.
That information travels to an edge analytics endpoint and is written into the operator's own logs on the same domain. Alongside it, the content delivery network reports the country the request came from, with nothing more precise about location.
What are the cookie and session flag for?
One first-party cookie is set only when a visit arrives from a search engine. It holds nothing but the name of that search engine, lasts up to one hour, and exists so that a later click on an outbound link can be matched to the search engine that brought the visitor in.
Separately, a session view flag lives in the browser only for the current session. Its sole job is to stop a single page view from being counted more than once. Neither of these leaves a lasting trace once the browser session or the hour ends.
Why doesn't the site load anything from outside?
Every page here is self-contained, built from static files served by a content delivery network, with fonts embedded locally rather than pulled from an outside service. No outside host is contacted while a page is being displayed, so nothing about the visit is shared with a third party during that time.
This also means there are no forms, no third-party analytics, no external subresources, and no contact channels anywhere on the site. There is nothing here for a visitor to fill in and nothing that gets sent to an outside analytics provider.
What happens when an outbound link is clicked?
Outbound links to third-party sites are routed through a first-party outbound redirect: the click first goes to a path on this domain, then forwards to the partner site. The stored visit data on this domain is not shared with the partner during that redirect.
Once the browser lands on the partner site, that site receives the request directly and keeps its own separate record of it. This page describes only what happens on this domain; it makes no claim about how a linked destination handles the visit once you're there.
What can this page not tell you?
Because the site has no login, no registration, and no account system, there's no personal data of the kind associated with names, e-mail addresses, or payment details for it to collect or retain. No visitor data is shared with advertising networks, data brokers, or outside analytics services, and no third-party or advertising cookies are used. Treat any linked destination as a separate site with its own separate practices, and avoid submitting personal details anywhere you aren't sure how the information will be handled.