This page describes what happens on this domain when a page is loaded and when an outbound link is followed. It covers only what the underlying build of this site actually does.
Tracks a small set of visit details for arrivals from search
When a visitor arrives from a search engine, the site records a limited set of details for its own traffic counting. Nothing here is used for any other purpose.
- The page path, the type of event, the name of the referring search engine, and the text of a clicked outbound button.
- Collection happens only for visits that arrive from a search engine; other visits do not trigger this beacon.
- Data is sent to an edge analytics endpoint and stored in the operator's own logs on the same domain — not shared with an outside analytics provider.
- The content delivery network also reports the country the request came from, and nothing more precise about location.
- A first-party cookie holds only the name of the referring search engine, is set only on a search-engine arrival, and expires after up to one hour. It exists so a later click on an outbound link can be matched to the search engine that brought the visitor here.
- A separate flag is kept in the browser for the current session only, so a single page view is counted once. It carries no identifying information and does not persist beyond the session.
Serves pages as static files and routes outbound clicks through this domain first
The site is a set of self-contained pages served as static files by a content delivery network, which handles the technical delivery of every request as the hosting layer. Fonts are embedded locally, so no font files are fetched from another host while a page displays.
- No file needed to display a page is loaded from an outside host — nothing is shared with an outside party while a page is on screen.
- Outbound links to third-party sites first pass through a path on this domain, which then redirects the browser to the partner. No stored visitor data is passed along in 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.
- This site does not control what a partner site does with that request, because the partner's practices happen entirely outside this domain.
Does not collect forms, accounts, or third-party tracking data
Several categories of collection are confirmed absent from this build. Stating them plainly explains why the site asks for no consent, no account and no personal detail.
- No forms are present anywhere on the site, so no typed input is ever collected.
- No third-party analytics service is used; all counting described above stays in the operator's own logs.
- No external subresources are loaded — every script, style and font needed by a page is served from this domain.
- No contact channels exist on the site, so no address, message or personal detail can be submitted through it.
- No names, e-mail addresses, account identifiers or payment details are collected, and no login or registration exists.
- No browser storage beyond the two items described above is set, and no persistent identifier is created.
Because these categories are absent, nothing here should be read as inviting a visitor to submit personal data through this site. Any partner site reached through an outbound link is a separate destination with its own separate handling of the request, outside what this page can describe.