Confirmed breach. Intrusion Sep 30, 2024, discovered Sep 30, 2024 — the first regulatory filing landed 301 days later (flagged late). 6,978 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 clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
6,978
Data types
—
Jurisdictions
2
IN NH
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Sep 30, 2024
When the intrusion reportedly occurred, per the linked filings
Edwardsburg Public School reported a data breach to the Indiana Attorney General. The breach occurred on 2024-09-30 and was reported on 2025-07-28. 879 Indiana residents were affected. 6,978 individuals affected in total.
Affected (this filing): 6,978
Leak >180d
⛰️New Hampshire State AGMost recentlinked via multistate filing link · 100%
Edwardsburg Public Schools notified the New Hampshire Attorney General of unauthorized network access occurring on or around September 30, 2024. The incident compromised the names and Social Security numbers of approximately two New Hampshire residents. The school offered one year of complimentary credit monitoring via Experian IdentityWorks and advised residents on fraud alerts and security freezes. Notification to residents began July 28, 2025.
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.