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 · 6dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
2
Data types
—
Jurisdictions
1
ME
Linked filings
1
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach discovered
Jul 1, 2020
Reported by MAINE AG filing
Breach window
Jul 5, 2020
When the intrusion reportedly occurred, per the linked filings
money, a financial services company, reported a data breach affecting two Maine residents. The breach, which occurred on July 5, 2020, and was discovered on July 1, 2020, involved an external system breach (hacking), insider wrongdoing, and an internal system breach. Affected individuals were notified in writing on January 2, 2020.
Affected (this filing): 2
ME AG ≤30d · 6d
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.