Lifesprk LLC reported a data breach to the Montana Attorney General. The breach was reported on 2020-03-17. The breach occurred from 11/5/2019 to 11/7/2019. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Mar 17, 2020. View entity profile → Other incidents for this victim →
incident inc_ff6839e7c0bd496e · 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.
MN MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 5, 2019
When the intrusion reportedly occurred, per the linked filings
Lifesprk LLC reported a data breach to the Montana Attorney General. The breach was reported on 2020-03-17. The breach occurred from 11/5/2019 to 11/7/2019. 1 Montana residents were affected.
Affected (this filing): 1
Lifesprk reported to HHS on 2020-03-17 a Hacking/IT Incident affecting 9000 individuals. Breached information located on Email. Two employees were victims of an email phishing scheme exposing PHI including names, medical record numbers, SSNs, and health/financial data. Lifesprk notified HHS, individuals, and media, offered credit monitoring, sanctioned employees, and implemented security safeguards.
Affected (this filing): 9,000
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.