🦞Maine State AGFirst filing
Filed Apr 16, 2021bd_a33976649fb67369
Affected (this filing): 48
ME AG >30d · 31d
One linked filing — more sources may join as they report · filed Apr 16, 2021. View entity profile → Other incidents for this victim →
incident inc_c2d2618ffa7a4ebc · merge_method deterministic
Discovered → first regulatory filing
Not recorded for this incident
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.
Identity (basic) · Government ID
ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 30, 2019
When the intrusion reportedly occurred, per the linked filings
Mar 16, 2021
Reported by MAINE AG filing
Affected (this filing): 48
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.