Clustered 3 filings across 2 jurisdictions · filing window Nov 23, 2021 → Jan 6, 2022. View entity profile → Other incidents for this victim →
incident inc_9f31f31b6f23461a · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
ME MT
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
all State AG
per-filing reported counts
State AGs report only their own residents; bars show per-filing counts.
Earliest sighting first · deep chronology in Litigation Timeline
Oct 11, 2021
When the intrusion reportedly occurred, per the linked filings
Oct 11, 2021
Reported by MAINE AG filings
TriValley Primary Care reported an external system breach (hacking) on 10/11/2021 affecting 57,596 individuals, including 10 Maine residents. SSNs and names were compromised. Notification was sent on 11/24/2021, offering 1 year of credit monitoring via Sontiq.
Affected (this filing): 57,596
TriValley Primary Care reported a data breach to the Montana Attorney General. The breach was reported on 2021-11-23. The breach occurred on 10/11/2021. 6 Montana residents were affected.
Affected (this filing): 6
TriValley Primary Care, a healthcare organization, experienced an external system breach on October 11, 2021. The breach was discovered the same day and compromised the names and Social Security numbers of 122,806 individuals, including 6 residents of Maine. Affected individuals were notified on January 7, 2022, and offered 12 months of credit monitoring and identity theft protection services. This notification is a supplement to an original notice filed on November 23, 2021.
Affected (this filing):
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.