Confirmed breach. Intrusion Jun 24, 2020–Jul 1, 2020, discovered Jul 1, 2020 — the first regulatory filing landed 85 days later. 21 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 >30d · 85dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
21
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
Jun 24, 2020 → Jul 1, 2020
When the intrusion reportedly occurred, per the linked filings
sdf reported an unspecified data breach that occurred between June 24, 2020, and July 1, 2020. The breach was discovered on July 1, 2020, and affected 21 residents of Maine. The compromised information included individuals' names and Social Security numbers.
Affected (this filing): 21
ME AG >30d · 85dME resident >60d · 89d
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.