How TRACE measures traffic
TRACE automatically counts aggregate public page requests worldwide. Individual browser analytics is disabled. This page and its privacy controls work without JavaScript.
Basic page requests
For approved public pages, a first-party hosting proxy increments separate hourly totals for page, country, common referral domain and request category, plus separate broad device/browser/operating-system families and first-level US-state labels. It runs before the hosting page cache. These counters store no visitor identifier, full IP address, raw user agent, precise location, query string, session history or individual request record.
The aggregate-only counter has no country-based consent gate. Country summaries support worldwide country labels supplied by the hosting network; absent or untrusted geography stays unavailable. Country and US-state labels can reflect a network exit or VPN and do not identify a visitor. No city, address or coordinates are read. Other state/region labels remain unavailable. Software families are unverified claims without versions or raw user agents; historical uncollected labels are not invented.
Your choices
Global Privacy Control, Do Not Track and an explicit traffic objection stop TRACE collection. Earlier local-only “Keep analytics off” choices are carried forward when JavaScript runs on a public application page. The server cannot see unsent browser storage: the initial request, JavaScript-disabled requests and static-only visits may contribute until an objection cookie or privacy signal is sent. Use Traffic measurement preferences to exclude this browser or restore basic measurement. The controls need no account or JavaScript. Restoring aggregate measurement does not enable individual tracking.
Reporting view preferences
When you choose a dashboard view, a functional cookie remembers only that preset or calendar range for up to 30 days, scoped to /traffic. It contains no visitor identifier and is never used for traffic collection or as a consent grant. You can forget the reporting view at Traffic measurement preferences without JavaScript; this changes neither your objection nor stored counts. Refresh failures can show a clearly dated, briefly retained page-memory snapshot, never fabricated zero counts.
What a count establishes
A page request does not prove that the page rendered or that a person read it. Navigation requests, crawler claims, link previews, other automation and unknown requests remain separate. Recognized health checks, prefetches, HEAD requests, private/API/static resource requests and server-component fetches are excluded. Browser-only cache, back-forward restores, client-only navigation, objections and storage failures leave coverage gaps.
The former optional browser collector is retired. No new individual page-view or tab/session histories are collected. Basic estimated visitors are unavailable because no visitor identifier or fingerprint is used.
Retention and public reporting
Hourly counter buckets are retained for 30 days and pruned hourly in bounded runs. Separate cumulative marginal counters remain for the life of the site’s traffic record, without individual event times or cross-dimension links. Reports offer 24-hour, 7-day and 30-day windows, a UTC calendar within the retained 30 days, and cumulative totals since collection began. Selecting another range or leaving the page does not erase stored data. The all-time graph shows only the last 30 days of hourly detail; its cumulative counters cover the whole collection period. Small labeled groups are combined in public reports; individual histories and precise locations are not published. Provider security logs and backups have separate policies.
Read the Privacy Notice and October 29, 2026 analytics supplement, or view the dated public traffic reports. Traffic does not establish identity, intent or endorsement.