Corrections & Retractions

This site curates and re-publishes publicly-reported cybersecurity developments. Accuracy is the core product: stories are source-linked, rated for source reliability, and fact-checked as part of the monthly edition process. When we get something wrong, we fix it and disclose the correction in place rather than silently editing.

Types of correction

• Fix — a straightforward factual error (wrong date, name, figure, sector, or severity) corrected in the affected story or digest, with the change noted.
• Clarification — a point that was technically correct but misleading; expanded or re-worded, with a note.
• Retraction — a story that should not have been published or that was based on a source that has since been withdrawn; the story is marked retracted and the reason stated, rather than silently removed (we treat the digest archive as an immutable record).

How we decide

Every correction request is assessed against the primary source and, where relevant, the source's own correction. We weight official/first-party statements over secondary reporting. When sources disagree, we state both rather than guess. Corrections are logged with the date applied and (for retractions) the reason.

How to ask for a correction

Email the details to the disclosure contact. Include the page/link, the disputed claim, and your source. We respond to well-founded requests; anonymous or baseless requests are noted and not acted on.

Publishing policy

The daily digest database and wiki are append-only by design. Individual story cards link to their live source so readers can verify; if a source is later corrected or taken down, we add a correction note to the affected story card rather than rewriting history.