Read this before treating the site as a data collector
The most useful thing to know upfront is that this site has almost nothing to protect, because it collects almost nothing. What follows describes only the mechanisms actually present on this domain. It does not describe the practices of any site reached by clicking an outbound link, because those destinations run under separate control and receive requests directly from the visitor's browser rather than through this one.
Understand what is counted when a visit is logged
When a visitor arrives here from a search engine, the site records a small set of details: 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 search-engine arrivals; visits from other sources are not logged in this way. The data is used only to count page views and clicks on outbound buttons, and it is stored in the operator's own logs on this same domain rather than passed to an outside analytics service. Alongside this, the site notes the country the content delivery network reports for the request, with nothing more precise about where the visitor is located.
Two small technical mechanisms support this counting. A first-party cookie is set only when a visit arrives from a search engine, lasts for up to one hour, and holds nothing but the name of that search engine. Its only purpose is to let a later click on an outbound link be matched back to the search engine that brought the visitor here. Separately, a flag is kept in the browser for the current session so that a single page view is counted only once rather than multiple times as the page loads or reloads. Neither of these stores a persistent identifier, and no other browser storage is set.
Know what happens when you follow a link off this site
Outbound links to third-party sites do not go straight to the partner. They first pass through a path on this domain and are then redirected onward. This first-party redirect step is part of how the click gets counted, but no stored visitor data is shared with the partner as part of that redirect. Once the redirect completes, the destination site receives the request directly from the visitor's browser and keeps its own separate record of that visit, entirely outside the reach of this page. This site has no way to describe, and does not attempt to describe, what a linked destination does with that request.
While a page on this site is being displayed, every file it needs — including its fonts — is served from this same domain rather than pulled from an outside host. The site itself is a set of static files delivered through a content delivery network, which handles the technical delivery of each request as the hosting layer. No separate resource is loaded from another provider while a page is open.
Recognise why so little is asked of you
There are no forms anywhere on this site, so there is no field asking for a name, an email address, or any other personal detail. There is no third-party analytics service reading traffic here, no external subresource loaded from another provider, and no contact channel of any kind. Together with the absence of any login, registration, or account system, this is why the site does not collect names, email addresses, account identifiers, or payment details, and does not retain personal data tied to an individual visitor. Visitor data is not shared with advertising networks, data brokers, or outside analytics providers, and no third-party or advertising cookie is used.
Because none of that infrastructure exists, this page has nothing further to disclose about accounts, transactions, or stored personal records. If a linked destination ever asks for personal information, that request belongs entirely to that separate site, and it is worth treating it with the same caution you would apply to any unfamiliar destination reached from a search result.