Our corrections policy
Some of what we publish will turn out to be wrong. This page sets out how to tell us, how quickly we fix each class of error, and what we do when a reported mistake cannot be confirmed. It applies to every review, ranking, and comparison on this site.
Why this page exists
AI tools change their pricing, their limits, and their feature sets constantly. A plan that was accurate on the day we published can be wrong a month later, and a claim can be wrong the moment it goes live because a vendor updated a page while we were writing about it.
We hold vendors to their own documentation. The same standard has to apply to us, which means fixing our errors in public, with a date, instead of editing them away quietly. Accuracy beats being right the first time.
Correction levels and response times
We sort corrections into four levels. The level decides how fast we act and how visible the fix is. For material and verdict-affecting errors, target windows run from the point we confirm the error, not from the moment a report reaches us.
| Level | Covers | Target response | Shown as |
|---|---|---|---|
| S1 — Minor | Typos, broken links, formatting | Within 72 hours | Silent fix |
| S2 — Material | Price, feature, date, availability errors | Within 24 hours of confirmation | Dated correction note on the page |
| S3 — Verdict-affecting | Facts that change a score or recommendation | Same day as confirmation | Prominent note + updated verdict |
| S4 — Ethical/legal | Misattribution, conflict-of-interest, data issues | Immediate review | Editor's note; retraction if warranted |
A silent fix at S1 means we correct the page without a note, because nothing about the substance changed. Everything from S2 upward is dated and stated on the page itself.
How to request a correction
Email info@aitoolspolice.com. Anyone can report an error: readers, vendors, and people who work on a competing product. Every report is checked the same way, whoever sends it.
Include:
- — The page URL, and where on the page the claim sits.
- — The claim as we published it, quoted.
- — The correct information, with a source we can open: a live pricing page, official documentation, a policy or legal page, or a public filing.
A report without a checkable source still gets read, but it takes longer to resolve, and we do not change a published claim on assertion alone.
What happens next
We check the reported claim against primary sources first. That means the vendor's live pricing page, the official documentation, or the relevant legal text. Independent user reports often tell us where to look, but they do not on their own establish what a plan costs or what a feature does.
If the error is confirmed, we fix it inside the target window for its level and date the fix on the page. From S2 upward, the note says what was wrong and what the correct information is, so you can see what changed instead of trusting that something did.
If we cannot confirm the error, the original stands. Where the disagreement is material, we note on the page that the claim is disputed and say who disputes it. We would rather publish a labeled disagreement than delete a finding or present a contested claim as settled. Either way, we reply to whoever reported it.
The final call on a correction is a human editorial decision. Mucahit Kaya founded and edits AI Tools Police and is accountable for what stays on the page.
What vendors can and cannot do
Vendors are welcome to report factual errors in our coverage of their product, and those reports get exactly the same treatment as a reader's.
What vendors can do
Flag a factual error at any time after publication, with a source we can check. That includes a price change, a renamed or retired plan, a deprecated feature, a new usage limit, or a policy update we have not caught yet. If a vendor believes we have read their documentation wrong, they can say so and point at the passage.
What vendors cannot do
No vendor sees a draft before it is published. No vendor edits our wording or signs off on a verdict. This holds for free coverage and for paid submissions equally: an expedited review buys a place at the front of the queue, a sponsored placement buys a slot that is labeled as sponsored wherever it appears, and neither buys a score or a ranking position.
A correction changes a verdict only when the underlying evidence changes. If a price or a limit we published turns out to be wrong, the assessment moves with the corrected number. Disagreement with our conclusion, unaccompanied by new evidence, does not.
Update discipline
We record the date each review was first published, and that date never changes. The date shown on a page is its last-updated date, recorded separately from the original publication date.
The last-updated date moves only when something material changed on the page: a price, a usage limit, a feature, a verdict, a ranking position. Copy-editing and formatting do not reset it. A fresh date on a page whose facts have not been rechecked is a false signal, and we treat it as one.
Material updates are dated on the page itself. That way you can see when the facts were last checked, rather than inferring it from the design.