Privacy
What we collect. Aggregate page-view counts: which page, which day, how many times. That’s the whole analytics record — no cookies, no IP addresses, no device fingerprints, and no way to tell one reader from another. If you subscribe to the weekly digest, we store the email address you gave us and when you confirmed. The one other thing we keep is described under the API below.
What we deliberately don’t. No third-party analytics, no ad trackers, no social pixels, no cookies at all. We can’t tell who you are, and we’ve built it so we can’t start without changing this page first.
The API. The public API is rate-limited, which means counting requests per caller. For anonymous callers we store a salted, one-way hash of the IP address — never the address itself — alongside an hourly counter, and those rows are deleted once their window has passed. The hash can’t be reversed to an IP or matched against anything else we hold. If you use an API key, the counter is keyed to the key instead and no hash is computed at all.
Email. The digest is double opt-in — an address gets nothing until its owner clicks the confirmation link we send. Every email carries a one-click unsubscribe that works immediately. We never share or sell subscriber addresses.
Business contacts. To approach organisations about sponsorship or partnerships, we record contact routes they have published on their own websites — a press or partnerships address, or a contact form. We read only that organisation’s own site, we obey its robots.txt, and we never buy lists, scrape social profiles, or guess an address from someone’s name. Every stored contact carries the exact page it came from. We prefer role addresses over named people; where a page names an individual as a business contact, that is personal data the organisation itself made public, and we delete it on request like anything else here. None of this touches what we publish — see how we work with partners.
Infrastructure. The site runs on Vercel, which processes requests (including IP addresses) transiently to serve them, as any host does. We don’t retain or analyze that data.
Questions or removal. Write to editor@avgcxr.in — we’ll answer, and we’ll delete your subscriber record on request.