Confirmed breach. Intrusion Dec 12, 2019–Jan 2, 2020, discovered Mar 2, 2020 — the first regulatory filing landed 66 days later (flagged late). 20,333 individuals reported across the linked filings.
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.
Regulatory clocksOregon✗ OR AG >45dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
20,333
Data types
—
Jurisdictions
2
CA OR
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Dec 12, 2019 → Dec 16, 2019
When the intrusion reportedly occurred, per the linked filings
Principal Life Insurance Company reported a data breach to the Oregon Attorney General. The breach was reported on 2020-05-07. The breach occurred during 12/12/2019 - 12/16/2019. The breach was discovered on 3/2/2020. 20,333 individuals were affected. Notice was sent on 1/1/0001.
Affected (this filing): 20,333
OR AG >45d
🐻California State AGMost recentlinked via multistate filing link · 100%
Principal Life Insurance Company reported a data breach to the California Attorney General. The incident occurred between December 12, 2019, and January 2, 2020. The provided source document contains only the filing metadata and an empty attachment placeholder; no narrative details regarding the nature of the breach, data types affected, or number of individuals impacted are available in the text.
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.