Corrections
When we get something wrong, we fix it and say so. Here's how to report an error and what happens when you do.
Threat Vectr publishes fast-moving security news produced by an automated, AI-assisted pipeline (see our editorial policy). Speed and automation make errors possible — a misread advisory, an out-of-date detail, a source that later revised its own reporting. We take fixing them seriously.
Our commitment
We correct errors of fact promptly once we're aware of them. We don't quietly rewrite history: corrected stories carry a visible “Updated” timestamp, and material errors are acknowledged in the story itself.
How to report an error
Spotted a mistake — a wrong CVE number, a misattributed source, a detail the original reporting has since walked back? Tell us via the contact page and use the subject line “Correction” so it's triaged first. Include:
- a link to the story;
- what you believe is wrong;
- a source that supports the correction, if you have one.
A human reviews every correction report.
What happens next
- The story text is corrected. The inaccurate detail is fixed in the body of the story.
- A visible “Updated” timestamp appears on the story so readers can see it has changed since first publication.
- Material errors are acknowledged in-story — where an error changed the substance of a story, the correction is noted in the story itself, not just silently patched.
Scope
This policy applies to every story published on Threat Vectr, regardless of topic, age, or how the story was produced. If it carries our byline, it's covered.