Privacy

We keep the minimum needed to run a game: your email, what you chose to play, and what you called. We never sell it, never run ad trackers, and never store the text of a news article. The AI models that read the wire never see who you are.

What we store

• Account: email, the name you gave, your theme, and when you last opened the app.
• Play: your doctrine, the topics you follow and your default stance on each, your bureau and desk, every prediction with its stake, and the points ledger those produce.
• Notices: which alerts and emails you turned on, and a log of what we sent you and whether it delivered.
• Sources you submit: the feed address and your desk's name as the submitter.
• Ask the desk: your questions and the answers, kept with your account so the rail can show its history.

We store headlines with a link to the publisher. We do not store article text. One session cookie signs you in; there are no analytics or advertising cookies. If a sponsor line or ad network is ever switched on, this page changes first.

Who sees it

• Your bureau sees your desk's name, doctrine, topics, predictions and points. That is the game.
• A desk's share pages are public by link. They show desk names, points and the headlines on the board — never an email or a name.
• Operators see accounts and play to run the game, resolve disputes and keep the wire clean. Every operator action is logged.

The AI models

Verdicts, risk readings, autopilot calls, story classification and Ask-the-desk answers are produced by hosted models. Right now the code can call Claude (Anthropic), Kimi (Moonshot) and ChatGPT (OpenAI) for text, and OpenAI Images for story illustrations. They receive headlines, source names, evidence lines, a desk's name and doctrine, and the questions typed into Ask the desk. They do not receive your email or your name. Which model handles which task is an operator setting; this list is generated from the same registry the code uses, so it is current by construction.

The data-consent toggle in Settings → Bureau controls whether your anonymised record — calls and outcomes without identifiers — may be used to tune the resolution desk. Off means never.

Services that help us run it

Email is delivered by Resend. Images are stored on Cloudinary. Abuse limits use an Upstash counter keyed on a hashed request origin for ten minutes and then forgotten. Errors are reported to Sentry without personal identifiers. The database is PostgreSQL hosted on Supabase; the app runs on Vercel. Each processes data only to provide its service to us.

How long, and how to leave

Account and play data stay while your account exists. Leaving a bureau frees your seat and keeps the bureau's ledger intact, because your opponents' points depend on it. To delete your account, write to desk@wirewatchnews.com from the address on the account: we remove your identifiers within 30 days and leave anonymised ledger rows so past editions still add up. Sent-notice logs expire after 90 days.

Your choices

• Turn any notice off in Settings → Notifications. Sign-in codes are the one email that cannot be turned off.
• Change your email in Settings → Account; the change is confirmed with a code to the new address.
• Ask for a copy of what we hold at the address above. We answer within 30 days.

Last reviewed 13 September 2026. This notice is written for readers, not for cover; where the law where you live gives you more than it says, you have more. Questions go to desk@wirewatchnews.com. The rules of the game are on their own page.