Overview
This series examines Uber’s reported 2018–2022 use of software to monitor driver behaviour and customer reviews, then temporarily or permanently deactivate accounts for suspected fraud or low ratings. The Dutch AP and CNIL describe no human assessment before the account action and link blocking to lost rides and platform income. The series follows the path from signal to account state, tests Article 22’s three cumulative conditions, uses the CJEU’s SCHUFA judgment to locate practical decision power, and examines exceptions, information rights, meaningful intervention, review design, and organizational responsibility. It explains why a label such as “status” does not settle legal significance while distinguishing regulator characterizations from a final court ruling. The AP said Uber stopped the violations and appealed the €824,990,000 fine; the public record here does not resolve that appeal or every system detail.
Learning outcomes
- Uber’s reported deactivations were tied directly to lost rides and platform income, not merely an internal status.
- Article 22 requires an individualized outcome to be a decision, solely automated, and legally or similarly significantly affecting.
- SCHUFA supports following practical decision power beyond formal labels, but its credit-scoring facts do not establish Uber’s facts.
- An exception or human review needs evidence of a qualifying route, informed judgment, and a real ability to change the outcome.
Keywords
Preview every chapter · Unlock full text, audio, and video from chapter 4
PlansFAQ
When does Uber driver deactivation become a GDPR Article 22 decision?
Uber driver deactivation becomes an Article 22 decision when it is an individualized outcome made solely by automated processing and it legally or similarly significantly affects the driver. The reported process strongly supports those three features, but the AP’s fine was appealed and the complete enforcement record is not provided here.
Why is losing access to Uber rides more than a technical status change?
Losing access to Uber rides is more than a technical status change because it removes the driver’s ability to make rides and generate platform income. Article 22 focuses on the practical effect of the individualized outcome, not the field name used to store or communicate it.
Does a later human review automatically avoid Article 22?
No. A later human review does not automatically avoid Article 22 because it may provide a remedy after the original automated deactivation. The relevant checkpoint is before the serious effect, with enough information, discretion, competence, and authority to change the outcome.
What must Uber prove to rely on an Article 22 exception?
Uber would need to establish a qualifying route—contractual necessity, authorizing Union or Member State law with safeguards, or explicit consent—and meet the safeguards and other GDPR duties that apply. The available summaries do not identify which exception Uber relied on.