DisclosureLens
All incidentsView linkage analytics →
HHS OCRHHS OCR enforcementState AGEnforced9 records · 7 statesLifecycle stage 3 of 3: EnforcedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 9 records

Ambry Genetics Corporation — January 2020 breach

Clustered 9 records across 8 jurisdictions: 8 filings and 1 enforcement record · filing window Mar 22, 2020 → Apr 20, 2020 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Enforced

Members

9 records

States

7

Affected · reported

232,772

First → last dated filing

Mar 22, 2020 → Apr 20, 2020

Merge confidence

100%

incident inc_0232cd63455e4380 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings and 1 enforcement record. Intrusion Jan 22, 2020–Jan 24, 2020, discovered Jan 22, 2020. 232,772 individuals reported across the linked filings. Data reported: Genetic / health-sensitive, Government ID, Health (basic), and 3 more. Notifications rolled out on a 29-day schedule across 7 dated filings beginning Mar 22, 2020. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance
2days

Range of discovered_at dates across filings

Filing span
29days

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 clocksCalifornia✗ CA 60-day late · 182dWashington⏱ WA AG >30dHIPAA✓ HHS notifiedMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 22, 2020breach begins
Jan 22, 2020discovered · members disagree
Mar 22, 2020first dated filing
Apr 20, 2020most 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 and enforcement record in this incident

  1. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. MAR 22HHS OCRHHS OCR noticefirst filing · states nationwide total 225,370day 0
  3. APR 17IN AGIN AG noticestates nationwide total 232,772+26d
  4. APR 17CA AGCA AG noticeno count stated+26d
  5. APR 17MA AGMA AG notice5,437 MA residents+26d
  6. APR 17MT AGMT AG notice608 MT residents+26d
  7. APR 17WA AGWA AG notice2,152 WA residents+26d
  8. APR 20NH AGNH AG notice675 NH residents+29d
  9. SEP 17HHS OCR enforcementHHS OCR enforcement noticemost recent · no count stated+2370d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 22, 2020
IN AG
Discovered
Jan 22, 2020IL AG + WA AG + NH AGJan 24, 2020CA AG + MT AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + WA AG + NH AG +3
Attack vector
Unauthorized Access
HHS OCR

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)

232,772

Sum of filed state slices

12,139· 5.2% of stated

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

US232,772
MA5,437
IN3,267
WA2,152
NH675
MT608

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 filing9 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Sep 29, 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

29 days

Cadence

~1 / 4.8d

vs. multi-state median

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