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 >90dFull clock table in Litigation Timeline
HHS OCRState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
6,730
Data types
—
Jurisdictions
1
IN
Linked filings
2
HHS OCR · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Sep 4, 2025
When the intrusion reportedly occurred, per the linked filings
Easterseals Northeast Indiana reported a data breach to the Indiana Attorney General. The breach occurred on 2025-09-04 and was reported on 2026-02-13. 6,643 Indiana residents were affected. 6,730 individuals affected in total.
Affected (this filing): 6,730
Leak >90d
🏎️INDIANAHHS OCRMost recentlinked via same-victim cross-source · 100%
Easterseals Northeast Indiana reported to HHS OCR on 2026-02-16 a Hacking/IT Incident affecting 3,158 individuals. Breached information was located on a Network Server. No business associate was identified as present. No further detail was available in the web description.
Affected (this filing): 3,158
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.