Life Line Screening of America, Ltd. reported a data breach to the Montana Attorney General. The breach was reported on 2019-12-30. The breach occurred from 8/1/2019 to 8/31/2019. 39 Montana residents were affected.
Affected (this filing): 39
Clustered 2 filings across 2 jurisdictions · filed Dec 30, 2019. View entity profile → Other incidents for this victim →
incident inc_1a74ae45261c4944 · 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.
Health (basic) · Identity (basic)
MT TX
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 1, 2019
When the intrusion reportedly occurred, per the linked filings
Life Line Screening of America, Ltd. reported a data breach to the Montana Attorney General. The breach was reported on 2019-12-30. The breach occurred from 8/1/2019 to 8/31/2019. 39 Montana residents were affected.
Affected (this filing): 39
Life Line Screening of America, Ltd. (TX) reported to HHS on 2019-12-30 a Hacking/IT Incident affecting 2,802 individuals. The covered entity's business associate was the victim of a cyber-attack that compromised ePHI including names, diagnoses, lab results, and treatment information, stored on a Network Server. The CE notified HHS and affected individuals, discontinued the BA relationship, and OCR initiated a compliance review of the BA.
Affected (this filing): 2,802
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.