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

DELTA DENTAL OF CALIFORNIA — May 2023 breach

Clustered 11 filings across 8 jurisdictions · filing window Dec 14, 2023 → Mar 18, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

8

Affected · reported

6,928,932

First → last filing

Dec 14, 2023 → Mar 18, 2024

Merge confidence

100%

incident inc_b829029e68d846cc · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe unauthorized access. Intrusion May 27, 2023–May 30, 2023, discovered Jun 1, 2023 — the first regulatory filing landed 196 days later (flagged late). 6,928,932 individuals reported across the linked filings. Data reported: Government ID, Financial account, Identity (basic), and 3 more. Notifications rolled out on a 95-day schedule across 11 filings beginning Dec 14, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
196days

Discovered → first regulatory filing

Discovery variance
35days

Range of discovered_at dates across filings

Filing span
95days

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 clocksVermont✗ VT AG >45 bdayWashington✗ WA AG >90dMaine✗ ME AG >90d · 176dMassachusetts✓ MA credit monitoring dueHawaii✓ HI CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 27, 2023breach begins
Jun 1, 2023discovered · members disagree
notification delay · 196 days
Dec 14, 2023first filing
Mar 18, 2024most 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. DEC 14MA AGMA AG noticefirst filing · 24 MA residentsday 0
  2. DEC 14OR AGOR AG noticeno count statedday 0
  3. DEC 14VT AGVT AG noticeno count statedday 0
  4. DEC 14MT AGMT AG notice48,026 MT residentsday 0
  5. DEC 14WA AGWA AG notice106,098 WA residentsday 0
  6. DEC 29ME AGME AG noticestates nationwide total 6,928,932+15d
  7. JAN 30WA AGWA AG notice1,186 WA residents+47d
  8. FEB 7MT AGMT AG notice1 MT residents+55d
  9. FEB 7WA AGWA AG notice844 WA residents+55d
  10. MAR 15NH AGNH AG notice12,783 NH residents+92d
  11. MAR 18HI AGHI AG noticemost recent · 8,553 HI residents+95d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 27, 2023 – May 30, 2023
VT AG
Discovered
Jun 1, 2023VT AG + MT AG + WA AG +1Jul 6, 2023ME AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
MA AG + VT AG + MT AG +4
Attack vector
Unauthorized Access
VT 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)

6,928,932

Sum of filed state slices

175,487· 2.5% of stated

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

US6,928,932
WA106,098
MT48,026
NH12,783
HI8,553
MA24
ME3

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 filing11 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
Reviewed
operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
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

95 days

Cadence

~1 / 9.5d

vs. multi-state median

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