All incidents View linkage analytics →Get the evidence package — $7.99 what’s inside →

Confirmed7 filings · 5 statesUnverified claimConfirmedEnforcedcritical sensitivity

Merged incident · 7 filings

CodeMetro — April 2020 breach

Clustered 7 filings across 5 jurisdictions · filing window Jun 16, 2020 → Jun 19, 2020. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

7 filings

States

Affected · reported

62,807

First → last filing

Jun 16, 2020 → Jun 19, 2020

Merge confidence

100%

incident inc_aa7a15d0680f4ff2 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings. Intrusion Apr 20, 2020–Apr 21, 2020, discovered Apr 21, 2020 — the first regulatory filing landed 56 days later. 62,807 individuals reported across the linked filings. Data reported: Government ID, Minor, PHI, and 6 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

56days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

3days

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 OK · 38dMassachusetts✓ MA credit monitoring dueHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

No cross-filing comparison data available for this incident.

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.