Corrections policy

When we get something wrong, we fix it and say so. Accuracy matters more in security news than almost anywhere else: readers act on what we publish.

Last updated: October 20, 2026

Write to [email protected] with the link to the story and what you believe is wrong. We read every message and reply as soon as we can.

• Corrections. A factual error (a wrong name, number, date, version or affected product) is fixed in the story, and a note at the end says what was wrong and when it was corrected.
• Updates. When a story develops (a patch is released, an organization confirms a breach, numbers change) we add the new information and show the "Updated" date at the top. Significant updates are described in the story.
• Clarifications. When a story was accurate but could be misread, we add a clarification note.
• Security advice. If an error in our "What you need to do" box could lead readers to stay unprotected (a wrong fixed version, for example), we correct it first.

We do not silently change facts, and we do not remove stories because an organization would prefer they were not published.

We remove or anonymize content only:

• for legal reasons, such as a court order;
• to protect a person's safety; or
• on request, when an older story names a private individual in a minor matter and keeping their name no longer serves the public interest. We consider each request on its own merits; organizations, public officials and people in positions of trust are not covered.

To make a request, write to [email protected] with the link to the story and your reasons. When we remove or anonymize a story, we say so on the page.