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

© DisclosureLens — Every breach. Every angle.Report an error / Request removalTermsPrivacy

v0.1.0 · coverage growing weekly

EqualizeRCM Systems data breach (2016) · DisclosureLens

All incidents View linkage analytics →

Merged incident · 2 filings

EqualizeRCM Systems

Clustered 2 filings across 2 jurisdictions · filing window Apr 28, 2016 → May 6, 2016. View entity profile → Other incidents for this victim →

✓ 0 discrepancies — filings agreeMerge100%

Confirmed breach. Intrusion Feb 25, 2016, discovered Feb 29, 2016 — the first regulatory filing landed 59 days later (flagged late). 3 individuals reported across the linked filings.

incident inc_653e3ee69d0e4ac1 · merge_method deterministic · confidence 100%

Litigation Timing

Notification delay

59days

Discovered → first regulatory filing

Filing span

8days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksOregon✗ OR AG >45dFull clock table in Litigation Timeline

State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced

Affected (total reported)

3

Data types

—

Jurisdictions

2

MT OR

Linked filings

2

all State AG

Timeline

Earliest sighting first · deep chronology in Litigation Timeline

Breach window
Feb 25, 2016
When the intrusion reportedly occurred, per the linked filings
Breach discoveredAG web form
Feb 29, 2016
Reported by OREGON AG filing
59 days
🦬Montana State AGFirst filing
Filed Apr 28, 2016bd_04e7049280fc2144
EqualizeRCM Systems (ERCM) reported a data breach to the Montana Attorney General. The breach was reported on 2016-04-28. The breach occurred from 2/25/2016 to 2/26/2016. 3 Montana residents were affected.
Affected (this filing): 3
🦫Oregon State AGMost recentlinked via multistate filing link · 95%
Filed May 6, 2016bd_d757cbc966e8e4ac
EqualizeRCM Systems reported a data breach to the Oregon Attorney General. The breach was reported on 2016-05-06. The breach occurred during 2/26/2016. The breach was discovered on 2/29/2016. Notice was sent on 4/28/2016.
OR AG >45d

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.