Clustered 3 filings across 2 jurisdictions · filed May 16, 2025. View entity profile → Other incidents for this victim →
incident inc_6f934e7755e74ca7 · merge_method deterministic · confidence 100%
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.
Identity (basic) · Government ID · Health (basic)
IA IN
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 11, 2025
When the intrusion reportedly occurred, per the linked filings
Balance Autism reported a data breach to the Indiana Attorney General. The breach occurred on 2025-03-11 and was reported on 2025-05-16. 1 Indiana residents were affected. 3,163 individuals affected in total.
Affected (this filing): 3,163
Balance Autism (Iowa healthcare provider) reported to HHS on 2025-05-16 a ransomware attack affecting the PHI of 1,281 individuals. Breached information was located on a Network Server. PHI involved included names, dates of birth, addresses, Social Security and driver's license numbers, diagnoses/conditions, and other treatment information. The CE notified HHS, affected individuals, and the media, provided substitute notice and complimentary credit monitoring, and implemented additional administrative, technical, and security safeguards.
Affected (this filing): 1,281
Balance Autism, a healthcare sector entity reported a data breach to the Iowa Attorney General. The breach was reported on 2025-05-16.
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.