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 · 31dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
3
Data types
1
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 discovered
Jul 1, 2022
Reported by MAINE AG filing
Breach window
Jul 2, 2022
When the intrusion reportedly occurred, per the linked filings
d, a financial services entity, reported an incident involving the physical theft or loss of a device. The breach, which occurred on July 2, 2022, and was discovered a day prior, affected 3 individuals in Maine. The compromised data included Social Security Numbers. Written notifications were sent to the affected individuals on July 8, 2022.
Affected (this filing): 3
ME AG >30d · 31d
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.