This page describes how this site handles visit data, based only on how the site is actually built. It covers what is measured, what is stored, what is deliberately absent, and how outbound links to partner sites are handled.
How visits from search engines are counted
When a visitor arrives at this site from a search engine, a first-party visit beacon 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 on that arrival path. The purpose is narrow: counting page views and clicks on outbound buttons for this site's own traffic figures. Nothing beyond that counting purpose is done with this information.
What the session flag does
- A single session view flag is kept in the browser for the current browsing session only.
- Its only job is to stop one page view from being counted more than once while that session lasts.
- It does not identify a visitor and does not persist beyond the session.
Why the pages are self-contained
Each page on this site is self-contained: the fonts are embedded locally and every file a page needs is served from this domain rather than fetched from an outside host while the page is displayed. 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 forms are present anywhere on the site, so there is no field for a visitor to type personal details into in the first place.
How outbound links to partner sites work
- Outbound links first pass through a first-party redirect hosted on this domain before continuing to the partner site.
- That redirect step does not hand the partner any visit data collected on this site; the link simply continues on to the destination.
- Once the visitor lands on the partner site, that separate site receives the request directly from the visitor's browser and keeps its own record of the visit, under its own practices.
- This page describes only the mechanics on this domain; it makes no claim about what a partner site does with a visit once the visitor arrives there.
What is not present on this site
There are no third-party analytics scripts running here, no external subresources loaded from other domains, and no contact channels such as forms or messaging tools built into the site. Combined with the absence of forms, this means the site has no built-in way to receive a name, an e-mail address, an account identifier or a payment detail from a visitor, and nothing of that kind is asked for. Because the only data handling described above is the narrow, first-party counting of page paths, event types, referring search engine names and clicked button text, there is nothing else to disclose beyond what is described on this page.