Envision Credit Union reported a data breach to the Montana Attorney General. The breach was reported on 2022-01-28. The breach occurred from 8/5/2021 to 8/7/2021. 12 Montana residents were affected.
Affected (this filing): 12
Clustered 2 filings across 2 jurisdictions · filed Jan 28, 2022. View entity profile → Other incidents for this victim →
incident inc_97858ea28b4b42af · merge_method human · 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.
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 5, 2021
When the intrusion reportedly occurred, per the linked filings
Jan 18, 2022
Reported by MAINE AG filing
Envision Credit Union reported a data breach to the Montana Attorney General. The breach was reported on 2022-01-28. The breach occurred from 8/5/2021 to 8/7/2021. 12 Montana residents were affected.
Affected (this filing): 12
Envision Credit Union reported an external system breach that impacted 55,694 individuals. The breach occurred on August 5 and August 7, 2021, and was discovered on January 18, 2022. The compromised data included names and financial account numbers along with security codes, access codes, passwords, or PINs. Affected individuals were notified on January 28, 2022, and offered 12 months of identity theft protection services through Experian.
Affected (this filing): 55,694
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.