Privacy · Updated October 2026
What this site collects. The short version.
This is a personal site that publishes essays and books talks. It runs Google Analytics 4 to count readers in aggregate, and it has one form, which subscribes you to my newsletter on Substack. There are no ads, no retargeting pixels, and nothing for sale here, so there is nothing to sell about you either.
What this site collects
Two things, and that is the whole list. Google Analytics 4 records aggregate traffic: which pages get read, roughly where readers are, which link they clicked to get here, and which buttons they press. It sets cookies in your browser to do that. I use it to decide what to write next, not to identify you.
The subscribe form posts your email address to Substack, which runs the newsletter and holds that address under its own privacy policy. Nothing else on this site asks for or stores personal information. There is no contact form here, no account to create, and no payment of any kind.
What this site does not do
No advertising pixels. No retargeting. No session recording or heatmaps. No data broker, no email append, no selling or renting anyone's information, ever. The only third parties that see anything are Google Analytics, Substack when you subscribe, and YouTube when you play an embedded video. Videos load through youtube-nocookie.com, which withholds the tracking cookie until you press play.
How to opt out
Browser-level controls work here and I will not fight them: Do Not Track, blocking cookies for this domain, or any content blocker will stop analytics from loading. Google also publishes an opt-out add-on at tools.google.com/dlpage/gaoptout. Nothing on this site breaks when analytics is blocked.
To leave the newsletter, use the unsubscribe link in any issue, which removes you immediately. To ask what is held about you or to have it deleted, reach me through the contact page and say so plainly. I will handle it myself.
Logs and security
The site runs on Vercel, which keeps short-lived request logs (IP address, user agent, URL) to serve traffic and block attacks. That is standard hosting infrastructure, not a product I built on top of. Security researchers: the disclosure contact is in /.well-known/security.txt.