Editorial policy & red lines
This page is a short status and red-lines summary. The full reader-facing rules live on Editorial guidelines.
Status badges
| Badge | Meaning |
|---|---|
| Unconfirmed | One source or leaker. No independent confirmation yet. |
| Corroborated | At least two independent sources or documentary evidence (filing, listing, certification), but no official confirmation. |
| Confirmed | The company, agency or person involved has confirmed it, or it shipped. |
| Debunked | Officially denied with evidence, or shown to be false. We keep the story up and say so. |
Every story must have
- The real X post where the leak surfaced, with its real engagement counts and the time we read them (UTC), when a suitable post exists.
- Between one and five linked sources, including the origin post when we have one.
- A check against other outlets, plus a "what would confirm it" note.
- An original image. We never reuse leaked imagery we don't have the rights to.
Red lines: we never publish
- Hacked or stolen personal data, or links to breach dumps, paste sites or ransomware leak sites.
- Leaked private or intimate images, or anything involving minors.
- Doxxing: addresses, phone numbers or identities of private people.
- Stolen source code, credentials, keys, builds, ROMs or malware.
- Classified documents. We only describe what major outlets have already reported.
- Pirated pre-release content (episodes, screeners, footage, music) or links to it.
- Allegations about named people unless a credible outlet reports them. Those are attributed, marked "alleged", and include any response.
- Invented quotes, numbers, accounts or engagement figures.
Leaker track records
Each leaker in our index has a page that counts how their leaks we covered turned out. Impersonator and suspended accounts are never used as sources.
Times
All times are UTC. Publish times are the real time a story went live. The time a leak surfaced is shown separately.