DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed4 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 4 filings

Principal Life Insurance Company — December 2019 breach

Clustered 4 filings across 4 jurisdictions · filing window Apr 8, 2020 → May 7, 2020. View entity profile → Other incidents for this victim →

✓ affected count agreeMerge100%

Determination

Confirmed

Members

4 filings

States

4

Affected · reported

20,333

First → last filing

Apr 8, 2020 → May 7, 2020

Merge confidence

100%

incident inc_066cb981c4854982 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. Intrusion Dec 9, 2019–Jan 2, 2020, discovered Mar 2, 2020 — the first regulatory filing landed 37 days later (flagged late). 20,333 individuals reported across the linked filings. Data reported: Government ID. Notifications rolled out on a 29-day schedule across 4 filings beginning Apr 8, 2020. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
37days

Discovered → first regulatory filing

Filing span
29days

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.

Regulatory clocksOregon✗ OR AG >45dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 9, 2019breach begins
Mar 2, 2020discovered
notification delay · 37 days
Apr 8, 2020first filing
May 7, 2020most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. APR 8IN AGIN AG noticefirst filing · states nationwide total 20,333day 0
  2. MAY 7OR AGOR AG noticestates nationwide total 20,333+29d
  3. MAY 7MA AGMA AG notice86 MA residents+29d
  4. MAY 7CA AGCA AG noticemost recent · no count stated+29d
  5. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 9, 2019
IN AG
Discovered
Mar 2, 2020· 84d undetected
OR AG
Data types
Government ID
MA AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

20,333

Sum of filed state slices

366· 1.8% of stated

98% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing4 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

29 days

Cadence

~1 / 9.7d

vs. multi-state median

3.6× slower

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.