Corrections Policy
We get things wrong sometimes. When we do, we fix it in the open rather than quietly editing the page and hoping nobody noticed. This page explains how we classify errors, how quickly we act, what a corrected article looks like, and how you can ask us to correct something.
Our commitment
Accuracy matters more to us than looking infallible. Every correction we make is visible on the article itself. We do not delete an article to make an error disappear, and we do not edit a published claim without telling readers it changed.
How we classify changes
| Type | When it applies | What readers see |
|---|---|---|
| Correction | A factual error: wrong figure, wrong name, wrong CVE, wrong affected version, wrong attribution. | A dated Correction note at the foot of the article stating what was wrong and what it now says. The dateModified field is updated. |
| Clarification | The facts were right but the wording was ambiguous or could reasonably mislead. | A dated Clarification note explaining what has been made clearer. |
| Update | Nothing was wrong; new information has emerged since publication. | A dated Update block, usually at the top for developing stories. |
| Minor edit | Typo, broken link, formatting. No change to meaning. | Fixed silently. No note, because nothing substantive changed. |
| Retraction | The central claim of the article does not hold up. | The article stays online with a prominent retraction notice at the top explaining what went wrong and why. Headline and body are struck through or clearly marked, not deleted. |
How fast we act
- Serious errors that could cause harm, such as incorrect patch guidance, misidentified indicators of compromise, or a wrongly named victim, are addressed as soon as we are made aware, day or night.
- Ordinary factual corrections are made within 24 hours of verification.
- Clarifications and updates are made within two working days.
How to request a correction
Email [email protected] with the subject line CORRECTION, or call +91 63670 98233. Please include:
- the URL of the article;
- the exact sentence or claim you believe is wrong;
- what the correct information is;
- a source we can verify it against, where one exists;
- your name and role, and whether you are the affected party or their representative.
We acknowledge correction requests within two working days. Where staffing allows, the request is reviewed by an editor who was not involved in the original story.
If we conclude the original reporting was accurate, we will tell you so and explain our reasoning and the sourcing behind it. Where the dispute is about interpretation rather than fact, we will offer to add your response to the article instead, under our right-of-reply practice.
Requests to remove an article
We do not take down accurate, lawfully published journalism because a subject finds it unflattering, and we do not accept payment to remove or de-index an article. Any such offer is declined and may itself be reported.
We will consider removal or redaction in narrow circumstances:
- the article contains personal data that creates a genuine safety risk to an identifiable individual;
- it names a victim of crime, a minor, or a source who did not consent to being identified;
- the central claim has been retracted and leaving the material accessible causes ongoing harm that a retraction notice cannot address;
- we are legally required to act.
Where we redact rather than remove, we note on the article that a redaction was made and why, without republishing the removed detail.
Technical handling
When an article is corrected we update its dateModified value in structured data and in the sitemap, so search engines and news aggregators see the revision. The original publication date is never altered to make an article appear newer than it is.
Reporting a pattern, not just a fact
If you believe our coverage of a subject is systematically unfair rather than factually wrong on a single point, write to us with the subject line COMPLAINT. Complaints of this kind go to a co-founder for review, and we will respond with our findings.