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

DNA Diagnostics Center, Inc. — May 2021 breach

Clustered 8 filings across 8 jurisdictions · filing window Nov 29, 2021 → Dec 15, 2021. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

8

Affected · reported

2,102,436

First → last filing

Nov 29, 2021 → Dec 15, 2021

Merge confidence

100%

incident inc_f5ef0594db7d4d5c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe unauthorized access. Intrusion May 24, 2021–Jul 28, 2021, discovered Aug 6, 2021 — the first regulatory filing landed 115 days later (flagged late). 2,102,436 individuals reported across the linked filings. Data reported: Government ID, Genetic / health-sensitive, PCI, and 3 more. Notifications rolled out on a 16-day schedule across 8 filings beginning Nov 29, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
115days

Discovered → first regulatory filing

Discovery variance
84days

Range of discovered_at dates across filings

Filing span
16days

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 clocksWashington✗ WA AG >90dCalifornia✗ CA 60-day late · 84dMaine⏱ ME AG >30d · 31dMassachusetts✓ MA credit monitoring dueOregon✓ OR AG ≤45dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

health_geneticidentity_government

Incident timeline

May 24, 2021breach begins
Aug 6, 2021discovered · members disagree
notification delay · 115 days
Nov 29, 2021first filing
Dec 15, 2021most 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. NOV 29MA AGMA AG noticefirst filing · 1,048 MA residentsday 0
  2. NOV 29IN AGIN AG noticestates nationwide total 2,102,436day 0
  3. NOV 29ME AGME AG noticestates nationwide total 2,102,436day 0
  4. NOV 29WA AGWA AG notice4,278 WA residentsday 0
  5. NOV 29CA AGCA AG noticeno count statedday 0
  6. DEC 6NH AGNH AG notice176 NH residents+7d
  7. DEC 9OR AGOR AG noticeno count stated+10d
  8. DEC 15SC AGSC AG noticemost recent · 1,649 SC residents+16d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 24, 2021
IN AG
Discovered
Aug 6, 2021WA AG + CA AG + NH AG +1Oct 29, 2021ME AG + OR AGfilings disagree on discovery
Data types
Financial account · Genetic / health-sensitive · Identity (basic) · Government ID · PCI · PII
MA AG + WA AG + CA AG +3
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)

2,102,436

Sum of filed state slices

12,247· 0.6% of stated

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

US2,102,436
IN4,871
WA4,278
SC1,649
MA1,048
ME225
NH176

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

16 days

Cadence

~1 / 2.3d

vs. multi-state median

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