Privacy

What is collected

Usage analytics

Page views and in-page interactions are measured with PostHog, Google Analytics, and Vercel’s Web Analytics and Speed Insights: pages visited, referring site, browser and device class, page-performance timings, and approximate (city-level) location derived from IP address. These measurements show which pages researchers use. The analytics configuration uses no advertising identifiers or cross-site tracking, and this data is not shared for marketing; Google Signals and ads personalization are disabled.

Session replay

PostHog additionally records every session as a reconstruction of the pages you saw and the clicks, scrolls, and console output within them. Anything you type into a form is masked in the replay, and network request bodies are not recorded, so the contents of the subscription and suggestion forms do not appear in it. Replays show where a page confuses people.

Cookies

Three first-party cookies persist between visits: two set for Google Analytics (up to thirteen months) and one for PostHog (up to twelve months). They distinguish returning browsers for the analytics above, and PostHog mirrors its identifier in local storage for the same purpose; nothing else reads them.

Programmatic-access telemetry

Calls to the MCP server and agent fetches of machine-readable surfaces are logged with the tool or path invoked, the client name and version it announces, latency, and status. Identity is represented by a one-way hash or the bot family name, never by a stored raw address tied to a profile.

What you submit

The email subscription form stores the address you enter, used only to send the updates you asked for; write to the contact below to be removed. The data-correction suggestion form stores what you submit for editorial review. Neither is shared.

Transient operational data

Rate limiting keeps per-address request counters for minutes. Infrastructure providers also retain standard hosting logs.