UBER TECHNOLOGIES, INC. — May 2014 breach

Clustered 3 filings across 3 jurisdictions · filing window Feb 26, 2015 → Mar 4, 2015. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

3 filings

States

Affected · reported

4,932

First → last filing

Feb 26, 2015 → Mar 4, 2015

Merge confidence

100%

incident inc_755706fcfb8c4cfb · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. Intrusion May 13, 2014, discovered Sep 1, 2014 — the first regulatory filing landed 178 days later (flagged late). 4,932 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 6-day schedule across 3 filings beginning Feb 26, 2015. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

178days

Discovered → first regulatory filing

Discovery variance

16days

Range of discovered_at dates across filings

Filing span

6days

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 · 654dFull 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.