Confirmed breach. Intrusion Jun 11, 2024–Jun 12, 2024, discovered Jun 12, 2024 — the first regulatory filing landed 490 days later (flagged late). 782 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksMaine✗ ME AG >90d · 490dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
782
Data types
2
PII · Government ID
Jurisdictions
2
IN ME
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jun 11, 2024
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Jun 12, 2024
Reported by MAINE AG filing
490 days
🏎️Indiana State AGFirst filinglinked via multistate filing link · 100%
Grand Traverse County Michigan reported a data breach to the Indiana Attorney General. The breach occurred on 2024-06-11 and was reported on 2025-10-15. 8 Indiana residents were affected. 782 individuals affected in total.
Grand Traverse County, Michigan discovered unauthorized system activity in its network environment on June 12, 2024. A digital forensic investigation determined that personal information (names and Social Security numbers) in compromised network locations could have been accessed by an unauthorized third party. 782 individuals were affected in total, with 1 Maine resident. Notification letters were sent October 9, 2025. CyberScout credit monitoring services were offered to affected individuals.
Affected (this filing): 1
ME AG >90d · 490d
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.