Clustered 2 filings across 2 jurisdictions · filing window Sep 3, 2025 → Sep 9, 2025. View entity profile → Other incidents for this victim →
incident inc_108c0b00d2674a48 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
PII
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.
CA TX
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 20, 2025
When the intrusion reportedly occurred, per the linked filings
Jun 20, 2025
Reported by CALIFORNIA AG filing
Jul 14, 2025
Reported by TEXAS AG filing
Zions Bancorporation, N.A. disclosed that on June 20, 2025, an employee inadvertently emailed an internal document containing customer names and deposit account numbers to an unauthorized third party. The bank contained the incident, took action regarding the employee, enhanced internal controls, and provided one year of identity theft protection to affected customers.
Zions Bancorporation, N.A. based in Salt Lake City, Utah, a financial services entity reported a data breach to the Texas Attorney General. The breach was discovered on 2025-07-14 and reported on 2025-09-09. 467 Texas residents were affected. 2,894 individuals affected in total. Types of information involved: Name of individual;Address;Financial Information (e.g. account number, credit or debit card number). Consumers were notified via U.S. Mail.
Affected (this filing): 467
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.