Urgent.News

What's breaking now, across thousands of outlets.

Tech

Uber Fined $966M: The High Cost of Automation Without Oversight

Uber faces a $966 million Dutch privacy fine over automated driver suspensions, raising questions about GDPR compliance and meaningful human oversight. The post Uber Fined $966M: The High Cost of Automation Without Oversight appeared first on TechRepublic .

Uber has been hit with a massive $966 million fine from Dutch privacy regulators over its use of automated decision systems to suspend drivers' accounts. The Dutch regulator found that Uber violated the EU General Data Protection Regulation by relying too heavily on automated processing without providing sufficient safeguards or information to affected drivers.

The fine covers incidents between 2018 and 2022, when Uber used algorithms to suspend drivers suspected of fraud, such as taking unnecessary detours or accepting trips without completing them. One affected driver, Brahim Ben Ali, gathered evidence from around 170 other drivers and filed a complaint through a Swiss digital-rights nonprofit.

Uber disputes the findings and plans to appeal the decision, arguing that drivers have the opportunity to contest any automated decisions and that most suspensions were temporary. The regulator maintains that the penalty is justified as a fraction of Uber's projected 2025 annual revenue. This case highlights the growing concerns around delegating too much authority to automated systems that make decisions impacting people's livelihoods, finances, and access to services, emphasizing the need for meaningful human oversight and transparency in AI-driven processes.

Written by urgent.news from TechRepublic's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at techrepublic.com →

More in Tech

I Spent Months Looking for a Job. Then I Said No to One.

I’ve been working in the industry for almost a decade, mostly under the title of iOS Developer . For most of that time, I was continuously employed.

  • Reporter spent months unemployed after nearly a decade in iOS development.
  • Declined higher-paying mobile developer offer due to preference for daytime work.
  • Values control over time and freedom to pursue interests over job security.

Release notes are not release documentation: a reader-task coverage method

A release note can be completely accurate and still leave an integrator unable to use the release. “Webhook retries now use exponential backoff and stop after 24 hours” tells readers what changed.

  • Release notes alone insufficient for integrators' needs
  • Expand change coverage to prerequisites, defaults, limits, etc.
  • Map reader's task to ensure proper understanding and handling

REST vs GraphQL in Practice

The Real Trade-offs After building APIs with both REST and GraphQL, I've learned that the choice isn't about which is "better" but about what your consumers need.

More from Tuesday 25 August →