Before you reply to anything we send

Check us yourself. Seven public checks, none of which need us.

An unsolicited email saying a problem was found on your listing is the same shape as an Amazon suspension scam, so doubt ours until you have checked it. Each check below uses something we publish, and nothing on this page asks you to trust us.

Seven checks, none of which need us

Anyone can run them, free, without contacting us.

  1. 01
    Read the standard we cited

    Every finding names a rule ID. Open it: claimsverified.org/standards/CV-DV-01/ is one of 109, with the source and the date we last checked it.

  2. 02
    Read the whole register by machine

    /standards/registry.json is every standard, version-pinned, in JSON. Compare what we told you against what we publish.

  3. 03
    Check the figures we quote

    /research/risk-index.json carries the category index with its method and date. A number that disagrees blocks the release.

  4. 04
    Check our record against ourselves

    The corrections page lists every finding we have withdrawn, the date, and who caught it first.

  5. 05
    Check what we say we cannot do

    What this audit does not tell you. A firm that will not write that page has not thought about it.

  6. 06
    Check the person who signed

    Every delivered report is signed by a licensed pharmacist. Name and licence number on every signed file you receive, checkable on the register.

  7. 07
    Check the day we ruled it

    Every ruling in our scan databases is fingerprinted into one code a day at claimsverified.org/record/. Two outsiders date it: OpenTimestamps and the Internet Archive. Pick a day there and your browser rebuilds the code from that day’s leaf hashes.

Check the finding before you check us

Settle it without us and without paying.

01
The phrase is yours

Search your own listing for it. If we quoted it wrong, we are wrong, and telling us costs you one line.

02
The rule is public

We name the authority and the document, not a private methodology.

03
The rulings are public

Every ruling we publish answers “can a supplement say X” with the standard and a rewrite, free.

04
Our mistakes are public

Withdrawn findings stay listed on the corrections page with the date.

What we will never do

Six things no message from us will ever ask or say.

Ask for a loginWe will never ask for your Seller Central login, your ad account access, or any password. Not for the free check, not during an audit. Anyone asking for marketplace credentials in our name is not us.
Put your copy in a data setFrom our privacy policy: “Your name, copy and quoted lines are never put into research or data sets; only de-identified patterns are, and never where fewer than ten brands share one.” Section 6b of the terms sets the limits. The text our AI pass sends to Anthropic’s API is not used for model training under Anthropic’s business terms.
Predict enforcementWe will never tell you enforcement is coming. Nobody knows that. We tell you what the published rules say and what remedy each one names.
Price by findingsOur fee does not change with what we find. Same price whether you pass or fail.
Report brandsWe report to the brand alone. We do not disclose what we find to Amazon, Meta, the FDA, the FTC or anyone else unless the law requires it. The one exception belongs to the reviewer: a licensed pharmacist may report a serious risk to health, and the brand hears from us first.
Name a failing brandNot in research, not in marketing, not to another client. Aggregate rates and category rankings are published. A failing brand is not.

Reach a person: audit@claimsverified.org. If you think a message you received in our name was not from us, forward it there and we will tell you plainly whether it was. Mailing addresses, for post and legal notices: 1200 Bay Street, Suite 1201, Toronto, ON M5R 2A5, Canada
228 Park Ave S, New York, NY 10003, USA

Security and data handling

How your files are handled.

What we readWhat the public can see: your live listing, product pages and published ads, plus the drafts you choose to send. We never ask for a login to your seller or ad accounts.
How files reach usThrough a private upload link made for your audit.
Who can see a client fileYou, signed in to your own dashboard. The licensed pharmacist who reviews and signs your file. Our staff. The service providers that host and process the data are named in the privacy policy.
In transitPages are served over HTTPS, and sign-in cookies are sent over HTTPS only.
Sign-inAfter 10 failed sign-ins on an account from one network in 15 minutes, further attempts on it from that network are refused until that time has passed. After 50 from all networks together, every attempt on it is refused.
How long we keep itThe periods are set out in the privacy policy, with the reason for each.

Found a security problem? Email audit@claimsverified.org. The same address is in our security.txt.

Checked us? Now check your listing.

Claims Verified

The independent standard for supplement and telehealth claims. Our AI rules a brand’s public supplement claims against 109 published standards. Each failing line is rewritten to the rules. A licensed pharmacist signs every Claims Review Report.

audit@claimsverified.org
Toronto · 1200 Bay St, Suite 1201
New York · 228 Park Ave S, NY 10003
Services How it works Free listing check Listing and Launch Clean Monitoring Listing Rescue and appeals Warning-letter response Telehealth: FDA Letter Match M&A diligence Proof on demand Request an audit Book a call
Research Research and data Claims by category Claim rulings Enforcement tracker Enforcement wire Telehealth letter index Daily record
Check our work Standards and method Sample report Corrections What this does not tell you How to verify us Our AI agents and their limits
Company About us Verify a signed file Partner program Client login Common questions Contact
© 2026 Claims Verified Privacy Terms Unsubscribe Every Claims Review Report signed by a licensed pharmacist Published from Toronto · 109 current standards · every figure recomputed from the scan databases before each deploy