Visit Counting
When a visitor arrives at this site from a search engine, the page records a small set of details tied to that visit: 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 information is used only to count page views and clicks on outbound buttons. It is used for that traffic-counting purpose and for nothing else described here.
Session Flag
To avoid counting the same page view more than once, the site keeps a single flag in the browser for the current session. That flag exists only for the duration of the session and its only function is to mark that a page view has already been counted.
Page Delivery
This site is a set of static, self-contained pages. Fonts used on the pages are embedded locally rather than pulled from an outside font service, and every file a page needs is loaded from this domain while the page is displayed. The site is served by a content delivery network, which handles the technical delivery of each request as the hosting provider for these static files.
Outbound Links
Some pages contain outbound links to third-party sites. Following one of these links first passes through a path on this domain, which then redirects the visitor to the partner site. 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 page describes only how the redirect on this domain works; it does not describe or vouch for what happens on the destination site afterward, since that is a separate system outside this page's scope.
Comparison
| Present on this site | Absent from this site |
|---|---|
| Visit beacon triggered from search-engine referrals | Forms of any kind |
| One session-scoped view flag | Third-party analytics services |
| Self-contained pages with local fonts | External subresources loaded while a page displays |
| First-party redirect before outbound links | Contact channels |
Scope Of This Page
This page describes only the mechanisms confirmed in this site's build: the first-party visit beacon, the session view flag, the self-contained pages with locally embedded fonts, the first-party redirect used before outbound links, the outbound links themselves, and the static hosting on a content delivery network. There are no forms on this site, no third-party analytics scripts, no external subresources loaded into a page, and no contact channels of any kind. Readers should treat this page as information about how these specific pages are built and delivered, not as a statement about any other system. Anything that happens after an outbound link leads to a partner site is outside what this page can describe, since that destination is a separate site receiving requests directly once the redirect completes.