Cleveland School District reported a data breach to the Indiana Attorney General. The breach occurred on 2024-09-28 and was reported on 2025-03-03. 1 Indiana residents were affected. 1,217 individuals affected in total.
Affected (this filing): 1,217
Clustered 2 filings across 2 jurisdictions · filed Mar 3, 2025. View entity profile → Other incidents for this victim →
incident inc_33e88fd572c54d77 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
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.
IN NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 28, 2024
When the intrusion reportedly occurred, per the linked filings
Oct 4, 2024
Reported by NEW HAMPSHIRE AG filing
Cleveland School District reported a data breach to the Indiana Attorney General. The breach occurred on 2024-09-28 and was reported on 2025-03-03. 1 Indiana residents were affected. 1,217 individuals affected in total.
Affected (this filing): 1,217
Cleveland School District (MS) notified the NH AG of a data security incident discovered on Oct 4, 2024, where an unknown actor accessed employee personal information. Two NH residents were affected. CSD engaged forensic experts, hardened its network, and offered credit monitoring via IDX.
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.