What we collect
When you subscribe, we store the email address you type, an optional "source" tag recording which page you subscribed from (for our own understanding of what's working — never shown to anyone outside the studio), and the timestamp you subscribed. We also generate a random unsubscribe token for your row. Every subscribe request — including ones we reject — also logs your IP address in a short-lived table used only to rate-limit abuse (capping how many attempts one address can make in a short window); see Retention below for how long that log lives. We do not use cookies, and we do not collect anything about you if you never submit the subscribe form — see Analytics below for what, if anything, runs in your browser.
Analytics
There are none. This site loads no analytics script and no third-party tracker of any kind — you can verify it by viewing the page source. If that ever changes, this paragraph changes with it in the same deploy: it is generated from the same setting that would switch a beacon on, so it cannot go stale.
Server error logs
When something breaks, the site writes one line to Cloudflare's log for that request: the time, the request method, the path (with anything identifier-shaped replaced by :id), the response status, and the error's name and message. Email addresses and long tokens are stripped out of that message before it is written. Request bodies, cookies and query strings are never logged. It exists so a broken subscribe form is noticed by us rather than by you.
How we use it
Your email is used for exactly two things: a one-time confirmation email when you subscribe, and a notification email when a new playbook ships. That's the entire mailing program — no drip sequences, no third-party marketing, no selling or renting the list to anyone. Your IP address is used solely for the rate limit described above; it's never linked to your email or used to identify you. We do not use your email for anything besides operating this mailing list.
Email delivery
Outbound email is sent through a transactional email provider (Resend). When that provider isn't configured, subscribe requests still succeed and are recorded, but no email goes out — nothing about that state is visible to you as a subscriber; it's an internal operating detail.
Retention
We keep your email and subscription record until you unsubscribe or ask us to remove it. Unsubscribing deletes your row outright — it is not a soft flag, and re-subscribing later creates a fresh record. The separate IP address log used for rate limiting is kept for at most about a day: it's pruned on a best-effort basis on every subscribe attempt, independent of and outlasting the 10-minute rate-limit window itself.
Unsubscribing
Every email we send includes an unsubscribe link built from a random per-subscriber token — no login required. Clicking it removes your email from the list immediately and permanently. You can also email us at bnwill32@gmail.com and we'll remove you by hand.
Who can see the list
The subscriber list is not public. It's readable only through an admin-only, key-gated endpoint used by the studio to operate the mailing list — no other party has access.
Contact
Questions about this policy or your data — email bnwill32@gmail.com.