Skip to content
Hugin
Public record case file

Consumer Protection Enforcement Accountability file

Official records, court dockets, oversight reports, release reviews, and civil or state updates joined without converting association or incomplete records into misconduct claims.

254 source leads20 verified anchors12 timeline events10 public-record rolesFile fingerprint fcd396c77d46
Connection map
timeline backed12
source links20
role links18
open queues0

Fingerprint = the first 12 characters of this file's SHA-256 content hash, used by mirrors to verify the same JSON bundle.

Connection map

How the public record connects

Graph JSON

This shows the case file's most significant public-record connections only — see the Role Web and Timeline tabs for the full set. A line means a record connects two points; it is not a finding about conduct.

Connection map

How the public record is joined

Graph JSON
timeline backed12
source links20
role links18
open queues0
Source groups
9 sourcespublic record repository9 linked recordsFTC privacy and security enforcement index / CFPB Consumer Complaint Database / Recalls.gov federal recall portal
8 sourcescivil enforcement record8 linked recordsFTC Kochava sensitive location-data settlement / CFPB Enforcement Actions / SEC Litigation Releases
Timeline joins
Feb 9, 2026 / officialFTC warns data brokers about PADFAA obligations1 linked recordWarning letters are compliance records and do not prove any recipient violated the law.
May 4, 2026 / officialFTC announces proposed Kochava location-data order1 linked recordUse settlement and allegation language exactly; do not generalize beyond the proposed order record.
Role joins
civil enforcement authorityFederal Trade Commission Bureau of Consumer Protection3 linked recordsFTC source rows must keep warning-letter, complaint, settlement, order, and guidance posture separate.
civil enforcement authorityConsumer Financial Protection Bureau2 linked recordsComplaint data is not an adjudicated finding and must be separated from enforcement documents.

Connections are navigation aids. They show where a record, event, or role is sourced; they do not convert association, correspondence, testimony requests, or document appearance into misconduct findings.

source leads254
automated probes341
verified anchors20
review backlog161
scout targets540
first-pass scout516
credential queue24
connectors45
keyless APIs264
free-key targets24
public search216
official pages36
POST templates0
CourtListener Search API / keyless apiGDELT DOC API / keyless apiFederal Register API / keyless apiGovInfo public document search / public searchRegulations.gov public search / public searcheCFR public search / public searchDOJ News API / keyless apiFOIA.gov government website search / public searchFBI Vault search / public searchNational Archives Catalog API / free key requiredData.gov CKAN catalog API / free key requiredCongress.gov public search / public search

Consumer-protection desk for FTC, CFPB, DOJ, SEC, state enforcement, recall, breach, communications, healthcare transparency, complaint-data, and privacy-sensitive source review.

Source lanesconsumer-protection, market-integrity, regulatory-anchors, public-record-discovery, federal-recalls, health-data-breach, communications-enforcement, healthcare-transparency
Sharing stateautomatic sharing disabled
Next actionPromote only posture-labeled agency records and aggregate complaint-data context after privacy review.
keyless apiCourtListener Search APIFTC data broker, privacy, warning-letter, and settlement updatesLegal search across opinions, dockets, RECAP data, judges, and arguments.
keyless apiGDELT DOC APIFTC data broker, privacy, warning-letter, and settlement updatesCoverage-index discovery for fresh public reporting rows.
keyless apiFederal Register APIFTC data broker, privacy, warning-letter, and settlement updatesOfficial rule, notice, and agency-document discovery.
public searchGovInfo public document searchFTC data broker, privacy, warning-letter, and settlement updatesFree public search across official publications from all three branches of the U.S. federal government.
FTC data broker, privacy, warning-letter, and settlement updatesCFPB complaint database and enforcement-action posture checksDOJ Civil Division fraud and consumer-protection press recordsSEC retail-fraud working group and litigation-release updatesRecalls.gov, CPSC, NHTSA, FDA, and openFDA recall and safety-alert recordsHHS OCR breach portal health-data privacy rows with patient-detail suppressionFCC enforcement orders, notices, consent decrees, robocall, and accessibility recordsCMS Open Payments API and healthcare payment-transparency disclosure rowsstate attorney general privacy, data broker, and consumer enforcement recordsconsumer complaint aggregate caveats and privacy-sensitive rowsFTC legal-library and final-order document joinsSEC, CFPB, FTC, DOJ, and GDELT coverage cross-checks

Source leads and automated probes are review inventory. They become verified anchors only after Hugin can attach the public record, legal posture, and no-allegation guardrails.

Evidence standard

Publishing limits

Jul 18, 2026, 5:00 PM
Minimum source tierofficial-record, civil-enforcement-record, state-enforcement-record, public-record-repository, coverage-index
Living peopleFor living people, publish only source-backed roles, legal posture, and exact record relationships; do not infer intent or liability.
Victim protectionDo not expose private consumer narratives, account details, medical/financial identifiers, precise location data, or personal complaint details unless an official record makes narrow quotation necessary.
Social leadsSocial posts can point to a source queue, but consumer-protection claims require official agency, court, complaint-data, or enforcement records.
Association firewall

No guilt by proximity

A company, adviser, broker, lender, platform, or data broker appearing in a complaint database, warning letter, or enforcement index is a public-record relationship only.

Public utility

Help grow the source queue

Hugin accepts public records, not accusations. A submitted URL lands in a review lane, gets source-validated, and only becomes a case anchor after the evidence rules and privacy gates are satisfied.

Review posture

What this case can prove right now

Fact-check desk
publishable claims8
source repair0
known anchors20
lead quarantine0
scout targets540
first-pass scout516
credential queue24
scout connectors45
rankhigh656 priority score
readyReady for first-pass public review8 publishable claim rows / 20 source anchors / 516 first-pass source rows
actions6 start-here rows9 total workbench action rows
blockers1 launch checks24 source-scout rows require free operator keys

Fact-check status is a review posture, not a verdict. Source-scout rows are leads until a reviewer joins them to publishable anchors; claim-ledger rows are timeline-derived and still require source validation plus no-allegation guardrails before promotion.

Source intake

Queue a public record

Public queue

Paste an official or public-record URL. Hugin classifies the lane first, keeps lead-only material quarantined, and requires source validation before anything reaches the case file.

Use an official or public-record page. Local, private, leaked, or credentialed URLs are rejected.
Queue a public source for review.
Visible queue

Latest submitted public URLs

Sanitized queue view: Hugin shows the public URL, lane, status, and why a source has not been promoted. Submitter identifiers are not shown.

Public queue loaded.Live queue connectedQueue hash 7f00fe297b79
No public submissions in this snapshot.When someone submits a source, this board will show the URL, lane, status, hold reason, and next review step before anything can become part of the case file.
known sources20
publishable anchors20
atlas sources4
keyless feeds3
release asks7
document jobs20
privacy triage9
lead quarantine0
01Submit URLPublic URL, label, and context enter the source queue.
02Classify laneOfficial, court, legislative, civil, state, repository, or lead quarantine.
03Validate sourcePublisher, date, scope, privacy, and duplicate checks run before promotion.
04Promote anchorOnly source-backed, privacy-cleared records can join timeline or role surfaces.
Contribution guide

Submit sources, not claims

A source is a public URL someone else can inspect. A claim is an interpretation. Hugin queues sources first and keeps claims out until a reviewed public record supports the exact wording.

Accepted

Official agency pages, court dockets, congressional releases, civil records, state updates, and public repositories with source URLs.

Publisher, date, record family, and why the URL belongs in this file.

Source URLs first. Context is welcome, but claims do not publish from submissions alone.

Not accepted

Private tips, survivor identifiers, sealed or leaked material, graphic details, and private contact data.

Screenshots or social posts without a public source URL.

Misconduct labels for living people unless the exact cited public record supports that exact statement.

What changed

Case change ledger

Audit feed for source anchors, queue decisions, privacy-review jobs, and hashes. It explains the process without turning leads into claims.

Change ledger loaded.Ledger hash bbf34785f27cCase hash fcd396c77d46
Safety posture

Locked to public records and bounded intake

Post throttleSource intake is DB-rate-limited to 6 submissions per minute per network key before a record is written.
Public URL onlyLocalhost, private networks, URL credentials, unsupported protocols, malformed URLs, and overlong fields are rejected.
No paid callsThe data export links render deterministic public-record payloads. They do not call LLMs or paid upstream APIs.
Identity minimizedSubmitter material is converted to a server-side HMAC hash, and the public queue does not return raw IPs or user agents.