Our pages distinguish vendor documentation from editorial judgment. If you find a factual error, send it to editor@shieldusers.com. James Whitaker reviews the source and the wording against the published methodology.
What to send
Include the Shield Users page URL, the exact passage or table cell, and a link to a current primary source. For a price or quota, identify the plan, billing period, unit and feature gate. For an API field, include the product, platform and documented version. A screenshot without a source URL can help us locate a change, but does not establish the current public terms by itself.
How we review it
We compare the cited material with the claim on the page. A confirmed change can update the product fact, its context and the page date. We may keep the earlier interpretation if the new source does not alter the buyer question. A source review date marks when the documentation was read; it does not claim hands-on testing.
Suggestions for new coverage
To propose a tool, describe its collection method, output and relevant user-protection workflow. Link product documentation and public access terms if available. We use the same published questions to decide whether it belongs in the comparison, a review or a protection hub.
Commercial questions
Questions about promotional links or collaboration belong with partnerships@shieldusers.com. They do not replace the source review for a disputed fact. The editorial policy explains how the site labels the ShieldLabs welcome offer.