Intealth reported a data breach to the Indiana Attorney General. The breach occurred on 2024-04-26 and was reported on 2025-04-10. 14 Indiana residents were affected. 1,750 individuals affected in total.
Affected (this filing): 1,750
Clustered 2 filings across 2 jurisdictions · filing window Apr 10, 2025 → Apr 16, 2025. View entity profile → Other incidents for this victim →
incident inc_fbf90d817d0943b9 · 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 ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 26, 2024
When the intrusion reportedly occurred, per the linked filings
Feb 11, 2025
Reported by MAINE AG filing
Intealth reported a data breach to the Indiana Attorney General. The breach occurred on 2024-04-26 and was reported on 2025-04-10. 14 Indiana residents were affected. 1,750 individuals affected in total.
Affected (this filing): 1,750
Intealth, a non-profit organization, reported a data breach affecting 3 Maine residents. The breach, which occurred between April 26, 2024, and May 6, 2024, was discovered on February 11, 2025. The incident was categorized as an external system breach (hacking). Intealth offered one year of credit monitoring and identity theft protection services through Equifax to the affected individuals.
Affected (this filing): 3
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.