Corrections
When we publish a factual error and fix it, we record what was wrong, what’s right now, and why — in plain language. The list is reverse-chronological so the most recent change is at the top.
Log
No corrections to date.
We expect this list to grow as we publish more, and we’ll keep it visible when it does. Public corrections are a feature of how we work, not a sign we got something wrong — they’re proof we’re willing to fix it openly.
Spot an error? Tell us →
How Corrections Work
Our publishing process when we get something wrong
- You report it. Use the contact form, the “Spotted an error?” link on any review, or email us. The most useful reports include the page URL and the specific wording that’s off.
- We verify. The editorial team checks the claim against primary sources. If the fact is wrong, we move to step 3. If it’s our wording that’s ambiguous, we move to step 3 anyway — clarity is part of accuracy.
- We update the page. The corrected wording goes live, with the page’s
dateModifiedbumped. - We log it here. Original wording, corrected wording, and the reason in plain language. The log entry is permanent.
- We notify the reporter when we have an email address to reach.
We do not silently rewrite history. If a published claim was wrong, the wrongness is part of the record — that’s the point of a public log. The only edits we make without a log entry are formatting, typos that don’t change meaning, and updates to live data (pricing, availability) that the page already presents as time-sensitive.
Related
- About Silent Security.net — the longer story behind the site
- Our Methodology — how we score and what we test
- Editorial Team — who writes and reviews
- Report an Error — pre-fills the correction form