Evidence comes before the verdict
Hands-on claims come from accounts we used. Reviews name the plan, test window, platform, sample size, and limits when those details affect the result. Product documentation supports feature and policy claims. Community reports are labelled as reports rather than presented as our own findings.
Scores cannot be purchased
Vendors do not get to buy a rating, preview a verdict, or remove a documented finding. If a product relationship exists, we disclose it on the relevant review. The relationship does not change the rubric.
Corrections and updates
Software changes. When a material fact changes, we update the article, show an updated date, and revise the verdict when the evidence warrants it. A correction fixes the record. It does not silently rewrite what was tested at the time.
Images and screenshots
Screenshots are used as evidence of the tested product. Generated illustrations and infographics are identified by their context and do not stand in for product output. Sensitive account information is removed before publication.
Challenge a claim
Send the URL, disputed sentence, and supporting evidence through the contact page. We review specific evidence, not requests to make a verdict friendlier.