HCF of Fairview Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2024-09-17 and was reported on 2025-01-08. 1 Indiana residents were affected. 3,866 individuals affected in total.
Affected (this filing): 3,866
Clustered 2 filings across 2 jurisdictions · filing window Jan 8, 2025 → Jan 9, 2025. View entity profile → Other incidents for this victim →
incident inc_48840db4705a4c45 · 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
Sep 17, 2024
When the intrusion reportedly occurred, per the linked filings
Nov 19, 2024
Reported by MAINE AG filing
HCF of Fairview Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2024-09-17 and was reported on 2025-01-08. 1 Indiana residents were affected. 3,866 individuals affected in total.
Affected (this filing): 3,866
HCF of Fairview, Inc., a healthcare organization, reported a data breach affecting one Maine resident. The breach occurred on September 17, 2024, and was discovered on November 19, 2024. Affected individuals were notified in writing and offered 12 months of identity theft protection services through Experian. The specific details of the breach and the types of information compromised were not specified in the notice.
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.