Corrections

How to report an error

Use the contact form and pick "Report an error or outdated information", or email contact@itsecureops.com. Every article also has a "Report it" link in its footer that opens the form with the page filled in.

Tell us three things, and the fix usually takes minutes rather than days:

• The page and the exact sentence or table row.
• What it should say instead.
• A source we can check: a vendor page, documentation, release note, advisory or announcement.

What we do next

• We check the claim against the source you send and the vendor's own current pages.
• If it is wrong, we fix it, update the page's "Updated" date, and add a line to the page's update log.
• If the change alters a verdict, a score or a recommendation, we say so in that update log entry.
• If we cannot verify the claim, we tell you what we found and leave the page as it is.

We aim to answer reports within five working days, and faster for prices, security advisories and anything marked as a safety issue.

For vendors

Vendors are welcome to send documentation, release notes and pricing updates, and we treat them like any other source: we check them and publish what the evidence supports. Vendors do not see pages before publication and cannot buy rankings, scores or verdicts. We do not remove accurate, sourced criticism, and we do not accept payment to change a verdict. Requests for coverage go through the same queue as everything else.

What counts as a correction

• Factual errors: wrong price, plan, limit, date, certification, platform or feature gate.
• Outdated facts: anything the vendor has since changed. We date every price and feature check.
• Missing context: a resolved incident still described as open, or a plan that now includes a feature we said was gated.

Differences of opinion are not corrections. If you disagree with a verdict, tell us which criterion you think we scored wrongly and why, and we will look at the evidence again. Our research methodology explains how pages are scored.

Bigger mistakes

If an error is serious enough to change a buying decision, we add a dated correction note at the top of the affected page rather than editing quietly, and we fix the same error anywhere else on ITSecureOps it appears.