Privacy policy · the paid Booth tier · the waitlist capture
The data the desk keeps on paid readers. And the vendors who touch it.
The paid-product disclosure. BrickbatDesk keeps a waitlist email, a Stripe billing email and last 4 digits of the card, and the reading lens + section-length preference — that is the entire field inventory for paying readers and waitlisted readers. Three processors touch the data: Stripe for payments, the email service for every recap and brief send, and the waitlist form for the pre-launch capture. Below: the fields, the purpose, the processors, the Illinois-only operating boundary, and the contact path.
What we collect · the paid Booth + waitlist
Four fields the desk keeps on paid readers.
The full inventory is on this page — the waitlist email, the Stripe billing email + last-4, and the reading lens + section-length preference. Anything outside that set is not held at all. Nothing more gets sent, nothing more gets stored.
Waitlist email address
/signupThe single address the desk keeps on the pre-launch waitlist. Collected at /signup, used to qualify nightly recap dispatch eligibility and to notify you the morning Booth checkout opens.
Stripe billing email + card-on-fingerprint
Stripe Checkout · $4.99 / monthThe billing email you enter at Stripe Checkout ($4.99 / month The Booth) and the last 4 digits of the card you charge. Stripe routes card data directly to Stripe; the desk receives only the billing email and the last 4 digits via the payment webhook, used for shipped invoices and the /account self-service surface.
Reading lens + section-length preference
/signup + /accountThe Bulls-heavy / Sox-heavy / Balanced knob and the short / medium / long recap-depth knob that shape the recap wire. Set at /signup, changeable at /account. The desk holds no analytics on what you actually read — the choice is the only signal kept.
Nothing else
nowhereNo cookies, no third-party analytics, no fingerprinting, no read receipts, no tracking pixels in any recap. The row is keyed to the address you dropped at /signup or to the Stripe billing email; nothing else rides along.
Why we collect it · the Booth nightly digest
Three purposes. Every field earns its row.
Every field earns its row. The Booth nightly digest is the only required purpose for paying readers — the waitlist rerun and the Booth MP4 video recap dispatch ride on the same address the desk already holds.
Booth nightly digest delivery
The single required purpose for paying readers. The Stripe billing email is the address the Booth nightly digest ships to — the same body The Booth renders, every dispatch morning. Cancel at /account and the address stops getting the Booth digest the same day; the free Wire recap is unaffected either way.
Booth video recap delivery
If you’re a paid Booth subscriber, the gated MP4 video recap lands in your inbox the morning the desk ships it. The last 4 digits of the card let the desk display a masked payment method on /account so you can confirm the card on file without re-entering it.
Nightly-digest eligibility
If you’re still on the waitlist, the address you dropped at /signup qualifies you for the nightly recap dispatch the moment the desk ships and notifies you the morning Booth checkout opens. No card on file is required — the row is keyed to the address alone.
Processors · the three parties who touch the data
Three processors. No fourth party.
The data the desk holds flows through exactly three parties — Stripe for the paid checkout, the email service for every recap and brief send, and the waitlist form for the /signup capture. No analytics vendor, no retargeting pixel, no third-party tracker in any recap.
Stripe
The payment processor that routes card data directly to Stripe at checkout. The desk receives only the billing email and the last 4 digits of the card from the payment webhook — used for shipped invoices and /account self-service. No card data ever touches the desk’s own infrastructure.
Email service
The authenticated transport for every recap, brief, and Booth render send. An authenticated transport sits between the desk and the underlying email vendor — the desk does not integrate with a vendor directly, and no vendor API key is held by the desk.
Waitlist capture
The waitlist form the /signup and /subscribe pages post to. Captures the waitlist email address and dispatches a confirmation email through the same email service. The waitlist form is the only writer to the waitlist row.
Illinois only · the operating boundary
The desk operates exclusively in Illinois.
BrickbatDeskships Chicago-local recaps for Illinois-resident readers. The paid Booth tier, the waitlist capture, and the free recap wire all stay inside the Illinois jurisdiction — the desk’s editorial coverage, source ledger, and disclosure obligations all live in the same regulatory frame.
BrickbatDesk operates exclusively in Illinois. The Monday Betting Brief ships only to Illinois-resident readers; the wagering guidance (21+, 1-800-GAMBLER) lives on /legal/privacy and the disclosure banners on the betting-trends products. The Booth MP4 video recap, the Booth nightly digest, and the free recap wire are all built and dispatched from Chicago for Illinois readers.
The full editorial-mission context lives on /about. The Illinois-specific regulatory copy the Monday Betting Brief ships alongside lives on /faq#illinois. The focused free-Wire disclosure lives on /legal/privacy.
Contact · ask the desk a privacy question
Ask the desk. The contact form is on /contact.
The same form the desk uses for everything else takes a privacy question too. Drop it on the contact form, the desk replies within one business day, and the row the question concerns stays untouched unless the reader asks for it to go.
The desk’s contact form lives on /contact →. The form lands in the desk’s inbox within one dispatch cycle. Prefer email? Mail brickbatdesk@polsia.app and the desk will reply the same way.
Last updated · 2026-08-07
Questions about your data? The desk replies.
This page is the source of truth on what the desk holds, why, and through which processors. Updates ship here with a fresh “last updated” line. If a change ever affects a row that’s already on the desk, the change ships with a one-tap opt-out in the next dispatch.
Contact the desk: brickbatdesk@polsia.app
Free-Wire disclosure: /legal/privacy →
Illinois regulatory block: /faq#illinois →