Pacific Guardian Life Insurance Co. Ltd. reported a data breach to the Montana Attorney General. The breach was reported on 2020-02-17. The breach occurred on 11/4/2019. 12 Montana residents were affected.
Affected (this filing): 12
Clustered 2 filings across 2 jurisdictions · filed Feb 17, 2020. View entity profile → Other incidents for this victim →
incident inc_8eb2b2d35de540c4 · merge_method deterministic · 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.
CA MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 4, 2019
When the intrusion reportedly occurred, per the linked filings
Nov 4, 2019
Reported by CALIFORNIA AG filing
Pacific Guardian Life Insurance Co. Ltd. reported a data breach to the Montana Attorney General. The breach was reported on 2020-02-17. The breach occurred on 11/4/2019. 12 Montana residents were affected.
Affected (this filing): 12
Pacific Guardian Life Insurance Co. Ltd. notified the California Attorney General of a data security incident involving unauthorized access to an employee's email account. The company became aware of suspicious activity on November 4, 2019. An investigation confirmed that an unauthorized individual accessed the account and may have viewed or downloaded emails containing personal information, including names, Social Security numbers, and in very few cases, medical information. 1,214 California residents were identified as potentially affected. The company secured the account, engaged forensic investigators, and offered 12 months of credit and identity monitoring to affected individuals.
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.