Confirmed breach. Intrusion Jan 12, 2022, discovered Jan 22, 2022 — the first regulatory filing landed 125 days later (flagged late). 54 individuals reported across the linked filings.
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 clocksMaine✗ ME AG >90d · 125dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
54
Data types
2
Identity (basic) · Government ID
Jurisdictions
1
ME
Linked filings
1
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jan 12, 2022
When the intrusion reportedly occurred, per the linked filings
DD, a healthcare organization, reported a data breach affecting 54 Maine residents. The breach, which occurred on January 12, 2022, was an inadvertent disclosure of names and Social Security numbers. The company discovered the breach on January 22, 2022 and notified affected consumers on February 22, 2022.
Affected (this filing): 54
ME AG >90d · 125d
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.