Privacy & your data

What this website stores for sign-in, voting, release alerts, topic suggestions, newsletter subscriptions and contact requests.

What we collect

An email address is used for magic-link sign-in. We store account creation time, hashed session tokens, votes, debate release alerts and your submitted suggestions. A release alert records the debate, request time and notification time. Contact forms store the name, email, subject and message you provide. Newsletter records store your email, opt-in source, consent version, confirmation time and subscription status.

Where it is processed

Application records are stored in Cloudflare D1. Uploaded public images are stored in Cloudflare R2. Cloudflare Workers processes requests, and Cloudflare Email Service sends service messages. Cloudflare Turnstile helps protect public forms. Data location depends on the Cloudflare services and account configuration; this site does not promise India-only storage.

Cookies, measurement and third parties

Essential HttpOnly cookies keep your sign-in session and protect form submissions. Optional audience measurement is delivered through Cloudflare Zaraz and remains off until you allow its Analytics purpose in the consent panel. You can reopen Cookie preferences from the footer at any time. No Google tag or Google Tag Manager is hardcoded into this site, and form contents are not intentionally sent to analytics. YouTube is not contacted by the embedded player until you choose to load it. Visiting YouTube, Reddit, X or Instagram is subject to those services’ policies.

Email choices

Sign-in does not subscribe you to a newsletter. Voting or using the bell adds one signed-in account alert for that debate and sends one service email when it is published; the alert can be removed from your watchlist. Newsletter signup uses a separate confirmation email. Each subscriber has a signed unsubscribe link; unsubscribe does not require signing in. The admin can review or export subscribers; this release does not send bulk newsletter campaigns.

Retention and deletion

Sign-in links expire after 15 minutes and sessions after 30 days. Administrator access requires a sign-in within the last 12 hours. Expired tokens and rate-limit records are cleaned by the scheduled job. Sent email payloads are cleared after provider acceptance; outbox records are removed after 30 days. Closed contact messages are removed after 180 days; unconfirmed newsletter signups after 30 days. Account deletion removes your account, votes, release alerts, suggestions, related subscriber record and matching contact records. Provider inbox copies, security logs and backups follow their separate retention settings.

Contact and corrections

Use the contact form for data questions, correction requests or newsletter issues. This notice describes the included implementation; the operator must review its accuracy against the actual deployment before public launch.