What we found
On 9 September 2026 the Federal Trade Commission announced it had rescinded its 2021 Policy Statement on Breaches by Health Apps and Other Connected Devices, saying the 2024 update to the Health Breach Notification Rule already covers health apps and connected devices such as fitness trackers. The same release repeats the agency's standing notice that the FTC "will never demand money, make threats, tell you to transfer money, or promise you a prize," and points consumers to ReportFraud.ftc.gov to report scams. Our harvested material describes no scam, no victim, no loss amount and no contact method — it is an agency housekeeping notice, and the impersonation wording in it is boilerplate that appears on FTC releases generally. We do not know whether anyone is using this policy withdrawal, health apps or breach notices as a pretext to contact consumers, and nothing in the harvested row says so. Treat any demand that you send or transfer money from someone claiming to speak for a federal agency as a scam: end the contact before any money moves, and check the agency through a number or address you looked up yourself. LIVEFRAUD ALERTS is independent and not affiliated with the Federal Trade Commission or any agency named here; this alert was assembled only from the single harvested item cited above.
- Only one harvested row, and it is an agency policy-withdrawal notice rather than a fraud advisory.
- No incident, complaint, victim group, dollar figure or contact channel appears anywhere in the harvested text.
- The only fraud-relevant wording is standard boilerplate carried on FTC releases, not a warning issued about a specific active scheme.
- Reviewed by 4 models, 3 from independent houses.
THE RULE
Low immediate risk: the harvested item reports an agency policy change, not an active scheme; the money-demand warning inside it is standing guidance and is repeated here for that reason alone.
What we don’t know
- Whether any impersonation of the FTC is currently in circulation.
- How any such impersonator would make contact — call, text, email or otherwise.
- What payment method any impersonator would request.
- Whether users of health apps or connected devices face any elevated contact risk from this change.
The bench — who voted
4 INDEPENDENT AI MODELS REVIEWED THIS. ALL 4: LOW RISK.
The card names a count. Here are the seats behind it, with what each one said.
ANTHROPICclaude-opus-5 · LOW
The finding presents a verbatim quotation — the FTC "will never demand money, make threats, tell you to transfer money, or promise you a prize" — and a specific referral URL (ReportFraud.ftc.gov) as appearing in the release. Neither the quoted string nor the URL appears anywhere in evidence row [1]. The row's limitation note refers only generically to 'fixed boilerplate' consumer-protection language; that supports the existence of some boilerplate, not the exact wording or the reporting pointer. Direct quotation marks assert word-for-word fidelity the harvested material does not establish.
DISSENT, PRESERVEDEverything that could have caused reader harm here is correctly disclaimed: the finding states plainly that no scam, victim, loss or contact method is in the material, flags it as housekeeping, marks confidence low, and lists the right unknowns. The only defect is sourcing hygiene on a quotation, not overreach about danger.
DISSENT, PRESERVEDI would question whether this item merited a consumer fraud alert at all. Framing a regulatory withdrawal notice as a fraud alert — even a heavily hedged one — risks leaving an ordinary reader with the impression that health-app breach notices are being used as a scam pretext, which the finding itself says is unknown. The generic 'never send money to a caller claiming federal authority' advice is sound but unconnected to this source.
DISSENT, PRESERVEDIf the quotation and URL can be verified against the actual release text and added as an evidence row, my verdict would move to 'holds' without further change.
GOOGLEgemini-flash-latest · LOW
The finding attributes specific verbatim text ('will never demand money, make threats, tell you to transfer money, or promise you a prize') and cites ReportFraud.ftc.gov, but neither the specific wording nor the URL appears in Evidence Row 1, which only generically references 'consumer-protection language is fixed boilerplate' in its limitation note.
GROQopenai/gpt-oss-120b · LOW
The evidence only notes that the release contains fixed boilerplate consumer‑protection language, but it does not explicitly quote or confirm the specific standing notice that the FTC "will never demand money, make threats, tell you to transfer money, or promise you a prize." The finding asserts that exact wording is repeated, which stretches beyond what the source directly states.
OPENROUTERopenrouter/free · LOW
The finding specifies the exact wording of the FTC's standing warning and mentions ReportFraud.ftc.gov, but the evidence row only states that the release contains 'fixed boilerplate' consumer-protection language without quoting it or listing the URL.
DISSENT, PRESERVEDThe evidence row's description of 'fixed boilerplate' consumer-protection language is consistent with the standard FTC warning and reporting URL, so the finding is a reasonable elaboration even though the evidence row is not fully explicit. The core of the finding — that the release is a housekeeping notice describing no scam — is supported.
Reviewed by 4 independent models; all judged the finding to go beyond the evidence.
▼ Protocol & challenge record
Objection (high): Framing overclaim by packaging, not by sentence. Every sentence is hedged, but the artifact is still shipped as a fraud alert: an 'ATTENTION: EVERYONE' banner, watch_icons of 'bank', 'person' and 'link', and a money-transfer warning paragraph. None of those three icons is supported by anything in the harvested row — there is no bank, no impersonated person, no link/URL lure in the source. A reader who scans the banner and icons will take away 'there is an FTC-related money scam going around,' which the body then has to spend two sentences undoing. The correct disposition for a regulatory-housekeeping press release whose only fraud content is a fixed footer is to publish nothing, not to publish a hedged alert.
Resolved: Substantially mitigated in the prose: two explicit limitation sentences state there is no scam, victim, loss amount or contact method; the risk_line says 'Low immediate risk'; confidence is 'low' with three accurate reasons; the disclaimer disavows affiliation. The residual problem is the banner, icons and the existence of the alert at all, which the prose cannot fully undo.
Objection (high): callout_options and directive_options reintroduce exactly the unsupported targeting the pipeline just stripped. targeting_dropped correctly removed 'caller', 'claiming' and 'authority' under §11 Rule 2 because no harvested source describes those groups — yet the surviving options offer 'ATTENTION: VETERANS', 'ATTENTION: ANYONE TOLD TO TRANSFER MONEY', 'ATTENTION: ANYONE PROMISED A PRIZE', 'Send this to any executive you know' and 'Forward this to the consumers in your life.' Veterans, executives, people told to transfer money and prize-promise recipients appear nowhere in the row; the only 'transfer money'/'prize' words in the source are inside the FTC's generic footer describing what the FTC itself will never do. Selecting any of these would assert a targeted victim class from a source that names none. The option lists should be reduced to 'ATTENTION: EVERYONE' with no share directive at all.
Resolved: Partly handled: share_directive is null, so no directive ships, and targeting_dropped documents three correctly removed groups. The unremoved option lists are the live defect.
Objection (medium): Source-to-claim omission that changes the story. The release gives two reasons for the rescission: the 2024 Rule update, and a Presidential executive order directing agencies to eliminate obsolete guidance documents. The finding reports only the first. It also silently adopts the source's own contested framing — the claim line calls the statement 'obsolete' and the release calls it 'controversial' and says it 'purported to' apply the Rule. Stating 'obsolete' as fact in the claim rather than as the agency's characterisation launders a deregulatory framing through a neutral-sounding alert. Either attribute the characterisation ('a policy statement the FTC describes as obsolete') or include the executive-order context so the reader sees why it was withdrawn.
Resolved: Partly pre-empted: the finding does not assert that the withdrawal weakens consumer protection, and the risk_line correctly characterises the item as a policy change. The omission and the unattributed 'obsolete' remain unfixed.
Objection (medium): Unsourced generalisation inside a limitation. 'the impersonation wording in it is boilerplate that appears on FTC releases generally' is a claim about FTC releases in the plural, drawn from a corpus of exactly one row, in an artifact that closes by asserting it 'was assembled only from the single harvested item cited above.' That is an internal contradiction. The safe formulation is confined to what the row shows: the wording sits in the release's standard closing block alongside the mission statement and consumer.ftc.gov / ReportFraud.ftc.gov links, and is not tied to any incident described in the release.
Resolved: Partly mitigated: the sentence is tagged role='limitation' with empty row_ids, so it is not presented as sourced. It still asserts a cross-corpus fact the harvest cannot support and contradicts the closing disclaimer.
Objection (medium): The advice sentence is over-broad and, read literally, wrong. 'Treat any demand that you send or transfer money from someone claiming to speak for a federal agency as a scam' would have readers treat a genuine IRS balance notice, a court fine or a customs duty as fraud. The defensible version is method- and channel-specific: no federal agency will demand payment by gift card, wire transfer, crypto or payment app, or demand immediate payment over an unsolicited call, text or email — and the verification step (look up the number yourself) is what does the real work. Tighten it or the alert teaches a rule the reader will have to unlearn.
Not resolved — preserved on the record.
Objection (low): Date provenance is thinner than the sentence implies. '9 September 2026' comes from the feed's pub timestamp, not from any date stated in the harvested body text; the body says only that the Commission 'rescinded' the statement, with no effective date. 'On 9 September 2026 the FTC announced' is a fair reading of a press-release timestamp, but the alert should not be read as establishing the date the rescission took effect. Also worth a currency check at publication time: nothing here confirms the 2024 Health Breach Notification Rule update remains in force as described, and the alert asserts current coverage of health apps and fitness trackers on the strength of one press release's summary of its own rulemaking.
Resolved: Mitigated by the unknowns list and by confidence='low', which flag that no incident timing or contact channel is established. The specific pub-timestamp-vs-body-date gap is not addressed.
Objection (low): Domain/entity check is asserted rather than shown. The URL is given as 'https://ftc.gov/news-events/news/press-releases/2026/09/ftc-withdraws-obsolete-policy-statement' — plausible and consistent with an FTC press release path, and the 202-326-2180 Office of Public Affairs number matches the agency. But the row is labelled 'official' by the harvester, and nothing in the check independently confirms the fetch resolved to the genuine ftc.gov host rather than a mirror or scraper copy. For an artifact whose entire subject is agency impersonation, the host verification should be explicit.
Not resolved — preserved on the record.
Preserved dissent
ON THE RECORDMy position is that this item should not be published. The harvested row is a regulatory housekeeping notice. Its only fraud-relevant content is the fixed closing block that the FTC appends to its press releases. Building a consumer fraud alert on that block means the alert's subject is a footer, not an event. The draft handles this honestly in prose — the limitations and confidence reasons are among the better-written parts of this artifact — but honesty in the body does not repair a headline, an 'ATTENTION: EVERYONE' banner, and bank/person/link icons that together tell a scanning reader there is a money scam in circulation. There is no scam in this material. Publishing a hedged alert is worse than publishing nothing, because it spends reader trust and attention on a non-event and trains the audience to discount the next alert that does describe a real scheme.
ON THE RECORDI also object to the option lists on the record. 'ATTENTION: VETERANS' has no connection of any kind to this press release — not a word, not a tag, not a referenced population. Its presence as a selectable callout for a health-app policy rescission indicates the option generator is not constrained by the evidence, and the same generator produced 'ANYONE TOLD TO TRANSFER MONEY' and 'ANYONE PROMISED A PRIZE' by lifting phrases out of the FTC's description of its own conduct and reattributing them to a nonexistent victim class. The targeting_dropped block shows the §11 Rule 2 check works when it runs; it evidently did not run against callout_options or directive_options. That is a pipeline defect, not a wording preference, and I would hold the artifact until it is fixed even if the Desk decides to publish on the merits.
ON THE RECORDFinally, on the record: stating in the claim line that the 2021 policy statement was 'obsolete' adopts the withdrawing agency's own characterisation as neutral fact, in a release that also calls the statement 'controversial' and says it merely 'purported to' apply the Rule. Whatever the merits of the rescission, an independent outlet should attribute that language rather than repeat it, and should mention the executive order the release itself cites as the driver. Reporting one of the two stated reasons and none of the contested framing is not neutrality.
The sources
Official sourceFTC Withdraws Obsolete Policy Statement2026-09-09
On 9 September 2026 the Federal Trade Commission announced it had rescinded its 2021 Policy Statement on Breaches by Health Apps and Other Connected Devices, saying the 2024 update to the Health Breach Notification Rule already covers health apps and connected devices such as fitness trackers.
Authority: official. Retrieved 2026-09-10.
Limitation: The release is about regulatory housekeeping; its consumer-protection language is fixed boilerplate and it identifies no scheme, no affected group and no reported losses.
Open the original source →Other checks
Published under standing founder pass (A9) — every claim source-mapped by the machine.
▼ What the machine checked
- ✓ Not a community submission.
- ✗ Draws on an FTC enforcement release, which names a defendant: "FTC Withdraws Obsolete Policy Statement".
- ✓ All 2 material sentence(s) map to FTC.
- ✗ anthropic returned "overstated"; google returned "overstated"; groq returned "overstated"; openrouter returned "overstated" — published on the receipt, not blocking (A9 amendment).
- ✓ No audience band is set.
No human affirmed these. They were verified by the classifier described in Amendment A9, on 2026-09-10.
Something wrong here? Tell us and we'll correct it — corrections are published, not quietly edited.
Phishy? Send it → sharelivefraud.com/squire-it
Not affiliated with any government agency, credit bureau, bank, platform, or law-enforcement agency. Informational only — not legal or financial advice.
Naming a source is not an endorsement, and being named here is not an accusation against any company.
Powered by SquireIt™
Verify this receipt at squireit.com