🦞Maine State AGFirst filing
Filed Aug 14, 2024bd_4561f646452d14e1
Affected (this filing): 2
ME AG ≤30d · 29d
One linked filing — more sources may join as they report · filed Aug 14, 2024. View entity profile → Other incidents for this victim →
incident inc_bfa1ad7eb980423d · 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.
ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 11, 2023
When the intrusion reportedly occurred, per the linked filings
Jul 16, 2024
Reported by MAINE AG filing
Affected (this filing): 2
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.