Heritage Health Care reported a data breach to the Indiana Attorney General. The breach occurred on 2024-09-17 and was reported on 2025-01-08. 2 Indiana residents were affected. 13,657 individuals affected in total.
Affected (this filing): 13,657
Clustered 2 filings across 2 jurisdictions · filing window Jan 8, 2025 → Jan 13, 2025. View entity profile → Other incidents for this victim →
incident inc_6f941189e1544496 · 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 17, 2024
When the intrusion reportedly occurred, per the linked filings
Oct 3, 2024
Reported by NEW HAMPSHIRE AG filing
Heritage Health Care reported a data breach to the Indiana Attorney General. The breach occurred on 2024-09-17 and was reported on 2025-01-08. 2 Indiana residents were affected. 13,657 individuals affected in total.
Affected (this filing): 13,657
Heritage Health Care reported a data security incident affecting one New Hampshire resident. Suspicious activity was discovered on October 3, 2024, on the management company's network. An unauthorized third party gained access to systems on September 17, 2024, acquiring documents containing personal information. The company engaged forensic investigators, contained the incident, notified law enforcement, and offered credit monitoring.
Affected (this filing): 1
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.