This page explains what happens on this domain when a page is loaded and when an outbound link is followed. It covers only what the site itself does, on its own files and its own logs, and nothing beyond that.
Records a visit when it arrives from a search engine
When a visitor lands on this site coming from a search engine, a first-party visit beacon sends a small record to an edge analytics endpoint on this same domain. That record holds the page path, the type of event, the name of the referring search engine, and, if an outbound button was clicked, the text of that button.
This data is used only to count page views and clicks on outbound buttons. It is stored in the operator's own logs on this domain and used for traffic counting and nothing else. The content delivery network also reports the country the request came from, with no finer location detail.
Keeps one cookie for one hour
A single first-party cookie is set only when a visitor 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 here.
Separately, a session view flag is kept in the browser for the current visit only, so a single page view is not counted twice. Neither of these leaves any other trace: no other browser storage is set, and no persistent identifier is created.
Serves pages without pulling in outside files
The pages on this site are self-contained: fonts are embedded locally, and every file a page needs, including its fonts, is served from this domain. While a page is displayed, nothing is fetched from an outside host, so no third-party analytics service or external subresource is contacted at that point.
The site itself is a set of static files served through static hosting on a content delivery network, which handles the technical delivery of every request as the hosting provider.
Routes outbound clicks through a first-party redirect
Outbound links to third-party sites do not go there directly. A click first goes to a first-party outbound redirect path on this domain, which then sends the browser on to the partner site. The stored visit data described above is not shared with that partner during this process.
Once the redirect completes, the partner site receives the request directly from the visitor's browser and keeps its own separate record of that visit. This site does not control what a partner site does with that request.
Collects no forms, no contact details, no third-party tracking
This site has no forms, so there is nothing here to fill in and submit. It has no contact channels, so no message a reader might send is received or logged. It uses no third-party analytics and loads no external subresources, so no outside service observes a page while it is being viewed.
Because of these absences, along with the narrow, first-party-only data handling described above, the site asks for no consent banner, no account, and no personal detail to be read or used.
Leaves partner sites outside this page's scope
This page describes only what happens on this domain. It cannot state what a linked partner site collects, stores, or does with a visit once the outbound redirect has completed, because that site keeps its own separate record outside this operator's logs. Readers should treat each linked destination as a separate site with its own handling of the request it receives.