DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed17 filings · 13 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedshinyhuntershigh sensitivity
Merged incident · 17 filings

ALLIANZ LIFE INSURANCE COMPANY OF NORTH AMERICA — July 2025 breach

Clustered 17 filings across 13 jurisdictions · filing window Jul 25, 2025 → Oct 2, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

17 filings

States

13

Affected · reported

1,497,036

First → last dated filing

Jul 25, 2025 → Oct 2, 2025

Merge confidence

100%

incident inc_d21a1cea2fd149fc · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 17 regulatory filings. Intrusion Jul 16, 2025–Jul 17, 2025, discovered Jul 16, 2025. 1,497,036 individuals reported across the linked filings. Data reported: Government ID, PII, and Identity (basic). Notifications rolled out on a 69-day schedule across 15 dated filings beginning Jul 25, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
1days

Range of discovered_at dates across filings

Filing span
69days

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.

Regulatory clocksTexas✗ TX AG >30dMaine⏱ ME AG >30d · 75dOregon✓ OR AG ≤45dWashington✓ WA AG ≤30dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 16, 2025breach begins
Jul 16, 2025discovered · members disagree
Jul 25, 2025first dated filing
Oct 2, 2025most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. JUL 1IL AGIL AG noticefiling day not on record · no count stated—
  2. JUL 1IL AGIL AG noticefiling day not on record · no count stated—
  3. JUL 25CA AGCA AG noticefirst filing · no count statedday 0
  4. JUL 25ME AGME AG noticeno count statedday 0
  5. JUL 25IA AGIA AG noticeno count statedday 0
  6. JUL 25OR AGOR AG noticestates nationwide total 250day 0
  7. JUL 25WA AGWA AG notice22,983 WA residentsday 0
  8. JUL 25MA AGMA AG notice1 MA residentsday 0
  9. JUL 28NH AGNH AG noticeno count stated+3d
  10. AUG 1DE AGDE AG noticeno count stated+7d
  11. AUG 1IN AGIN AG notice1 IN residents+7d
  12. SEP 9RI AGRI AG noticeno count stated+46d
  13. SEP 29MT AGMT AG notice4,409 MT residents+66d
  14. SEP 30ME AGME AG noticestates nationwide total 1,497,036+67d
  15. OCT 1CA AGCA AG noticeno count stated+68d
  16. OCT 1NH AGNH AG notice8,106 NH residents+68d
  17. OCT 2TX AGTX AG noticemost recent · states nationwide total 1,497,036+69d
  18. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 16, 2025
CA AG
Discovered
Jul 16, 2025DE AG + MT AG + CA AGJul 17, 2025IL AG + ME AG + IA AG +5filings disagree on discovery
Data types
Identity (basic) · Government ID · PII
IL AG + IA AG + WA AG +8
Attack vector
Unauthorized Access
ME 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)

1,497,036

Sum of filed state slices

158,800· 10.6% of stated

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

US1,497,036
TX115,898
WA22,983
NH8,106
ME7,402
MT4,409
MA1
IN1

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

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 filing17 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

69 days

Cadence

~1 / 4.9d

vs. multi-state median

11.5× 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.