Plain notice. No theater.

We distinguish between identifier-free page counts and preference-controlled visitor analytics. For the Agentic AI and Collective pages, we count eligible page requests even if you decline analytics. These separate count records contain only the page, hour and a known-bot classification. They contain no IP address, visitor or session identifier, fingerprint, location, referrer or campaign data. They cannot tell us who visited, how many unique people visited or how long anyone read. We do not set cookies for these counts.

Separately, unless you have declined visitor analytics, our server proxy and first-party visit log can record basic page-visit signals to evaluate engagement and protect the site: path, timestamp, referrer, basic device/browser user-agent signals, and optional UTM campaign parameters. We store an anonymous session identifier and a keyed HMAC of client IP — never the raw IP address — alongside coarse location headers (country / region / city). Declining suppresses that visitor log and client engagement beacons. We do not collect precise GPS or retain raw proxy header dumps.

When you explicitly accept cookies, we also enable client-side first-party engagement beacons, campaign attribution persistence, and Vercel Analytics for aggregate visit counts. You can change or revoke your preference at any time using the controls below.

• Cookie consent preference - remembers whether you accepted or declined telemetry so you are not prompted repeatedly.
• Attribution cookie - only set if you accept cookies on campaign landing; remembers UTM parameters for 30 days so subsequent page visits reflect the campaign source.
• Session door markers - short-lived markers to prevent double-counting visits during an active reading session.
• Operator markers - only if this practice intentionally marks a browser to keep operator and test traffic separate from client traffic.