DisclosureLens
UnknownHigh

UBER TECHNOLOGIES, INC.

bd_8cb0530a7d7281d1 · schema v1 · pii pii-v1

Severity

High

Discovered

Nov 14, 2016

Filed

Nov 21, 2017

To disclose

12 months

Affected

600,000

Linked

6 filings

Confidence

95%
Full breach record for UBER TECHNOLOGIES, INC. →10 incidents on file

Uber Technologies, Inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2017-11-21. The breach occurred during 10/13/2016 - 11/15/2016. The breach was discovered on 11/14/2016. 600,000 individuals were affected. Notice was sent on 11/22/2017.

Oregon clock✗ OR AG >45d12 months discovery → filing
⚠ AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.

Incident timeline

undetected · 32 days
discovery → filing · 12 months / 372 days

Oct 13, 2016

Begins

Nov 14, 2016

Discovered

Nov 21, 2017

Filed

This filing is one of 6 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (5) · sorted by filing gap

Show 1 more filing ↓up to 7d gap

Filing propagation · 6 filings · 6 states

View merged incident ↗
New Hampshire State AGNov 21 · first
Montana State AGNov 21 · first
Washington State AGNov 21 · first
California State AGNov 21 · first
Oregon State AGNov 21 · first · this page
Massachusetts State AG+7d

Pattern: first filing Nov 21 (NH), last Nov 28 (MA) — a 7-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.