Clustered 3 filings across 3 jurisdictions · filing window Mar 11, 2024 → Apr 8, 2024. View entity profile → Other incidents for this victim →
incident inc_382d067c02844be2 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
IN VT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 6, 2024
When the intrusion reportedly occurred, per the linked filings
Mar 6, 2024
Reported by VERMONT AG filing
Kenneth Young Center is a community-based non-profit, comprehensive provider of mental health and senior citizens' support services. Kenneth Young Center corporate office is located in 1001 Rohlwing Rd, Elk Grove Village, Illinois, 60007, United States and has 200 employees.
Mar 12, 2024
Reported by Leak Site filing
Kenneth Young Center notified Vermont AG of a March 6, 2024 data breach where an unauthorized actor accessed systems and potentially viewed employee data including SSNs, driver's licenses, financial accounts, passports, and medical info. Investigation ongoing. Center engaged outside assistance, notified federal law enforcement, enhanced security controls, and offered 24 months of credit monitoring via Experian.
Kenneth Young Center reported a data breach to the Indiana Attorney General. The breach occurred on 2024-03-06 and was reported on 2024-04-08. 6 Indiana residents were affected. 850 individuals affected in total.
Affected (this filing): 850
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.