This page describes only what this site's build actually does when a visitor loads a page, and it covers this domain alone, not the destinations that outbound links lead to.
How a visit is counted
When someone arrives from a search engine, the site logs a small set of details tied to that single visit.
- Page path and event type — which page was viewed or which outbound button was clicked.
- Referring search engine name — recorded only when the visit originates from a search engine.
- Clicked button text — the label of an outbound button, if one is clicked.
- Country from the content delivery network — a coarse location value; nothing more precise is collected.
This information is used only to count page views and outbound clicks. It is stored in the operator's own logs on this domain and is not shared with advertising networks, data brokers, or outside analytics services.
What the cookie and session flag do
Two small mechanisms support that counting, and both are limited in scope and lifespan.
- First-party search-referral cookie — set only when a visit arrives from a search engine, holds nothing but that search engine's name, lasts up to one hour, and is used to match a later outbound-link click to the search engine that brought the visitor here.
- Session view flag — kept in the browser only for the current session, so a single page view is not counted more than once.
No other browser storage is set, and no persistent identifier is created. Once these expire, nothing on this domain links a return visit back to the earlier one.
How pages are built and served
The site is a set of static, self-contained pages served through a content delivery network.
- Static hosting on a content delivery network — the CDN delivers the files and handles the technical data of each request as the hosting provider.
- Locally embedded fonts — fonts are packaged with the site rather than pulled from an outside host.
- No external subresources — every file a page needs while it displays comes from this domain, so no outside host receives data during that display.
What happens when an outbound link is followed
Outbound links use a first-party redirect before leaving this domain.
- First-party outbound redirect — a click first goes to a path on this domain, then forwards to the partner site.
- Outbound links to third-party sites — once the redirect completes, the partner site receives the request directly from the visitor's browser and keeps its own separate record of it.
Stored visitor data on this domain is not shared with the partner as part of that redirect. This site does not control what the partner site does with the request it receives.
What this site does not collect or offer
Several things that other sites often include are absent here by design.
- No forms — there is no way to submit text, files, or personal details through this site.
- No third-party analytics — traffic counting stays in the operator's own logs.
- No external subresources — nothing loads from another host while a page displays.
- No contact channels — this page names no address, form, or route for reaching anyone.
Because of these absences, the site does not collect names, e-mail addresses, account identifiers, or payment details, does not run logins or accounts, and does not retain personal data tied to an individual visitor. This is also why the site asks for no consent banner beyond what is described above and requests no account: there is nothing here that needs one. Do not submit personal data to this site or to any linked destination on the assumption that this page governs it — a partner site reached through an outbound link keeps its own separate record, outside anything described here.