Alameda-Contra Costa Transit District — April 2020 breach

Clustered 5 filings across 5 jurisdictions · filing window Mar 11, 2021 → Mar 15, 2021. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

5 filings

States

Affected · reported

38,234

First → last filing

Mar 11, 2021 → Mar 15, 2021

Merge confidence

100%

incident inc_e73e38673ba34008 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe unauthorized access. Intrusion Apr 7, 2020–Jun 16, 2020, discovered Jun 16, 2020 — the first regulatory filing landed 268 days later; 1 later filing was flagged late. 38,234 individuals reported across the linked filings. Data reported: Government ID, PII, and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

268days

Discovered → first regulatory filing

Discovery variance

202days

Range of discovered_at dates across filings

Filing span

4days

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 · 202dMaine⏱ ME AG >30d · 70dMassachusetts✓ MA credit monitoring dueFull 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.