Clustered 2 filings across 2 jurisdictions · filed Dec 4, 2020. View entity profile → Other incidents for this victim →
incident inc_34e2dc7bdeaf49f2 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Government ID · Financial account
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
CA ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 30, 2020 → May 4, 2020
When the intrusion reportedly occurred, per the linked filings
Jul 1, 2020
Reported by CALIFORNIA AG filing
Jul 17, 2020
Reported by MAINE AG filing
Angeion Group reported an unauthorized access to an email account occurring between March 30 and May 4, 2020, discovered on July 17, 2020. The breach affected 67,677 individuals, including 34 Maine residents. Compromised data included names and financial account numbers. Angeion provided 12 months of credit monitoring and ID theft recovery services.
Affected (this filing): 67,677
Angeion Group reported a data breach occurring between March 30, 2020, and May 4, 2020. An unknown third party accessed an employee's corporate email without authorization. The email contained personal information of claimants, including names, SSNs, driver's license numbers, and financial account data. The company notified law enforcement, launched an investigation, and offered free identity theft protection services to affected individuals.
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.