D8F81A37Public record case file · Updated Sep 17, 2026
Accountability file
A public-record case file for tracking data-broker, privacy, consumer-finance, civil enforcement, complaint-data, retail-fraud, recall, breach, communications-enforcement, and healthcare-transparency source lanes. It treats enforcement actions, warning letters, complaint databases, recall records, breach lists, and investor-protection programs as separate public records rather than proof that any named company or person committed misconduct outside the cited record.
Original editorial artwork generated for Hugin.
D8F8 1A37 1CA2This 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.
These are the standards every anchor on this file must clear.
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.
Every public-record role in this file, grouped by kind. Open a role to read its dossier — its public-record status, what it is, and the exact records that name it. A shared record naming two roles is not a finding about conduct beyond that record.
Pick a role to see its public-record status, what it is, and the exact records that name it. A shared record is not a finding about conduct.
No single record names more than one role in this file yet.
Official CFPB database of consumer financial product and service complaints, with browser exploration, exports, and API access.
Official CFPB enforcement-action portal with court documents and related materials for Bureau actions.
CMS Open Payments data portal and API for publicly accessible payment, ownership, and transfer-of-value records reported by drug and medical-device companies.
CPSC page documenting REST access to machine-readable recall data for publicly available product recall information visible on cpsc.gov.
DOJ record announcing coordinated non-prosecution agreements with Alibaba and AUS Merchant Services that resolve defined FDCA-related marketplace and payment-processing conduct with $600 million in combined penalties and forfeitures.
Official DOJ Civil Division press-room index for enforcement, fraud, consumer, and civil-action public records.
Import sources create source-run packets, document inventories, and review tokens. They do not publish accusations or graph relationships until the case-file evidence rules are satisfied.
An expanded recall covers about 6,000 Tylö Halmstad and Kiruna Hybrid saunas after the previous bench repair proved ineffective.
Recall record read September 20; reported incidents are not a court determination of liability. The unit count may overlap the earlier recall.official recordCPSC recall 26-778: JKMAX heated blankets and padsU.S. Consumer Product Safety CommissionAbout 195,000 heated blankets and pads are recalled for overheating, fire and burn hazards.
Agency recall notice read September 20. Incident counts are reports attributed to the company, not independently adjudicated findings.official recordFTC PADFAA data-broker warning lettersFederal Trade CommissionFTC press release warning 13 data brokers about obligations under the Protecting Americans' Data from Foreign Adversaries Act.
Warning letters and compliance reminders are official records; they do not establish that a specific recipient violated the law without a later enforcement record.civil enforcement recordFTC Kochava sensitive location-data settlementFederal Trade CommissionFTC announced a proposed order resolving litigation over alleged sale and disclosure of sensitive location data.
Use the record as FTC civil-enforcement posture; preserve words like alleged, proposed order, settlement, and consent before summarizing.official recordEntered stipulated order in FTC v. Kochava, Inc.U.S. District Court for the District of Idaho, posted by the Federal Trade CommissionThe signed Stipulated Order for Injunction and Other Relief in FTC v. Kochava, Inc., No. 2:22-cv-00377-BLW (D. Idaho), Document 138, filed June 25, 2026. It is the operative order and supersedes the May 4, 2026 proposed order as the current posture of the matter.
This is the entered order, not the proposal, so the desk must stop labeling the Kochava resolution proposed; it remains a negotiated stipulation in which the defendants neither admit nor deny the complaint's allegations, so its provisions are enforceable obligations rather than judicial findings of fact against anyone. The FTC case page indexes this filing under June 26, 2026 while the document itself is stamped and signed June 25, 2026; cite the document's own date.public record repositoryFTC privacy and security enforcement indexFederal Trade CommissionFTC topic page collecting privacy and data-security enforcement records, including orders, settlements, and current consumer-protection updates.
Index pages are discovery tools; each enforcement record needs its own posture and document links before publication.public record repositoryCFPB Consumer Complaint DatabaseConsumer Financial Protection BureauOfficial CFPB database of consumer financial product and service complaints, with browser exploration, exports, and API access.
Complaint rows are consumer reports and response-status records; they are not adjudicated findings or statistical samples.official recordCFPB notice on consumer complaint system integrityConsumer Financial Protection BureauCFPB newsroom notice in which the Bureau states it cannot rely on its own consumer complaint portal data as a reliable reflection of market conditions or consumer experiences, and describes the credit-reporting volume distortion and response-coding inconsistency behind that position.
This is the issuing agency withdrawing confidence in a dataset the desk already cites, so it governs every aggregate built from the CFPB complaint database. It is an agency statement about data quality and planned remediation, not a finding against any consumer reporting agency, credit-repair company, influencer, technology provider, or consumer.public record repositoryCFPB Enforcement ActionsConsumer Financial Protection BureauOfficial CFPB enforcement-action portal with court documents and related materials for Bureau actions.
Enforcement rows need status labels such as pending litigation, post order, post judgment, expired, terminated, or dismissed.baselineClaim rows are derived from timeline events and source anchors. They are evidence-status labels, not accusations or final truth claims.
Release requests are lawful public-record asks. They identify source gaps, review gates, and privacy constraints; they are not evidence that a specific person committed wrongdoing.
Deliberate gaps in the public record — open until the underlying records are released or reviewed, not questions we have skipped.
D8F8 1A37 1CA2Connections 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.
Consumer-protection desk for FTC, CFPB, DOJ, SEC, state enforcement, recall, breach, communications, healthcare transparency, complaint-data, and privacy-sensitive source review.
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.
These are not loose TODOs anymore. Each lane below is computed from the case file's source tiers, then joined to matching sources, timeline events, role nodes, and release-roadmap requests.
Index FTC warning letters, complaints, settlements, final orders, legal-library records, dates, respondents, and posture labels.
Join SEC working-group, litigation-release, complaint, final-judgment, and investor-alert rows with explicit legal posture.
Preserve product, company-response, publication-delay, privacy, and non-statistical-sample caveats before using complaint data.
Index payment-year, reporting entity, covered-recipient type, amount, nature of payment, ownership rows, dispute context, and API/export links.
Join Recalls.gov, CPSC, NHTSA, FDA, and openFDA rows by agency, product type, hazard, remedy, status, date, and official release URL.
Index covered entity, state, affected-count band, breach type, submission date, and business-associate status while suppressing patient details.
Block private identifiers, consumer narratives, precise location details, account data, and medical/financial identifiers from public snippets.
Index CFPB action status, respondent, product, filed date, complaint/order documents, and legal posture.
Preserve FCC document type, released date, order/notice/consent posture, proceeding number, and consumer-facing issue area.
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.
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.
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.
Queue a public source for review.Sanitized queue view: Hugin shows the public URL, lane, status, and why a source has not been promoted. Submitter identifiers are not shown.
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.
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.
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.
Audit feed for source anchors, queue decisions, privacy-review jobs, and hashes. It explains the process without turning leads into claims.
Extract document index and source metadata first.
Next: Metadata extraction includes publisher, URL, document family, and date.0c08aace2d93Extract document index and source metadata first.
Next: Metadata extraction includes publisher, URL, document family, and date.8b3b6367c2f5Extract document index and source metadata first.
Next: Metadata extraction includes publisher, URL, document family, and date.fb13d936fbc9Extract document index and source metadata first.
Next: Metadata extraction includes publisher, URL, document family, and date.d0ab6a277602Extract document index and source metadata first.
Next: Metadata extraction includes publisher, URL, document family, and date.c6e955b6db61Extract document index and source metadata first.
Next: Metadata extraction includes publisher, URL, document family, and date.a9aa58eb5d20Extract document index and source metadata first.
Next: Metadata extraction includes publisher, URL, document family, and date.b154351b0e7eExtract document index and source metadata first.
Next: Metadata extraction includes publisher, URL, document family, and date.19394b42963aMirrors can compare this hash to verify the same case file bundle.
Next: Compare the short hash in the UI with this machine-readable ledger.d8f81a371ca2This binds document mirroring and privacy-triage rules.
Next: Compare the short hash in the UI with this machine-readable ledger.e6fcfa65b0ac