This page describes only the technical handling of visit data on this site, covering how pages are served, what a search-engine arrival triggers, and how outbound links to other sites work.
What does this site record when someone visits?
When a visitor arrives from a search engine, this 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 through a first-party visit beacon that sends the data to an edge analytics endpoint on the same domain. That data is used for one purpose only — counting page views and clicks on outbound buttons — and is stored in the operator's own logs on this domain. Alongside this, the hosting content delivery network records the country associated with the request, without any more precise location detail. A session view flag is kept in the browser only for the current visit, so that a single page view is not counted more than once; this flag does not persist beyond the session. A separate first-party cookie is set only when the visitor arrives from a search engine, holds nothing but the name of that search engine, lasts up to one hour, and is used solely to connect a later outbound-link click back to the search engine that brought the visitor here. No other browser storage and no persistent identifier are set.
What does this site not collect or share?
- No forms are present on this site, so no typed personal details are submitted through it.
- No third-party analytics services receive any part of the visit data described above.
- No external subresources are loaded — every file a page needs, including locally embedded fonts, comes from this domain, so no outside host is contacted while a page is displayed.
- No contact channels are offered on this site.
Because of these absences, the site does not ask for consent, does not require an account, and does not request any personal detail to be viewed or used.
How do outbound links and pages actually work here?
The site is a set of self-contained, static pages served by a content delivery network, which handles the technical delivery of every request as the hosting provider. Outbound links to third-party sites are implemented as a first-party outbound redirect: a click first goes to a path on this domain, is logged for the click-counting purpose already described, and is then redirected to the destination site. No stored visitor data is passed along to that destination during this process. Once the redirect completes, the visitor's browser contacts the third-party site directly, and that site keeps its own separate record of the visit. This site has no way to describe or control what that separate site does with the request, since the connection at that point is between the visitor's browser and the third-party destination, not this domain.
What this page does not state, and what that means for you
This page only describes the mechanisms confirmed above: the visit beacon, the edge analytics endpoint, the session flag, the one-hour search-engine cookie, static self-contained pages, locally embedded fonts, the first-party redirect step, and content-delivery-network hosting. It does not describe any practice beyond these, because no other collection, cookie, retention rule, or data-sharing arrangement has been confirmed for this site. If a linked destination asks for personal details, that request is governed by whatever that separate site does with the information it receives directly, not by anything on this page. Treat this page strictly as a description of how this domain itself handles a visit, and treat any third-party site reached through an outbound link as a separate destination with its own separate handling of whatever is submitted there.