Disclosures Claims Reports Entities Incidents Pulse

Feed live

DisclosureLens

Structured extracts of public breach disclosures — regulator filings (SEC, HHS, state AGs, EU DPAs) alongside threat-actor leak-site claims and press reports. SEC and HHS filings render inline from the originating regulator’s public record under the fair report privilege; other sources link out to the source URL. AI-extracted with full per-record audit trail (model, prompt version, confidence).

ai_assisted: true · Article 50 disclosure on every record

Product

Disclosures feed
Pulse · analytics
Entities
Breach notifications by state

Methodology

How extraction works
Confidence & review
About the bot

Trust

Security
Self-disclosure commitment
API documentation
API keys

v0.1.0 · coverage growing weekly

Accretive Health data breach (2012) · DisclosureLens

All incidents View linkage analytics →

Incident · single filing

Accretive Health

One linked filing — more sources may join as they report · filed Feb 6, 2012. View entity profile → Other incidents for this victim →

Confirmed breach. 14,000 individuals reported across the linked filings.

incident inc_4ed63aa3b5954585 · merge_method deterministic

Litigation Timing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

HHS OCRConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity

Affected (total reported)

14,000

Data types

Health (basic)

Jurisdictions

FEDERAL

Linked filings

all HHS OCR

Timeline

Earliest sighting first · deep chronology in Litigation Timeline

FEDERALHHS OCRFirst filing
Filed Feb 6, 2012bd_d27c22ee5d494bdd
Accretive Health reported to HHS on 2012-02-06 a Theft affecting 14000 individuals. Breached information located on a Laptop.
Affected (this filing): 14,000
HHS notified

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.