anonym.legal
Înapoi la BlogGDPR & Conformitate

Dutch AP: The €290M Uber Fine and Why Cross-Border Data Transfers Are Amsterdam's Enforcement Priority

The Dutch AP issued the EU's largest individual data transfer fine — €290M against Uber in 2024. Here's what cross-border transfer compliance requires for Netherlands-based organizations.

March 7, 20267 min citire
Dutch APNetherlands GDPRUber GDPR finecross-border data transferEU data transfer

The Dutch AP and the Uber Precedent

The Dutch Autoriteit Persoonsgegevens (AP) established the EU's most significant data transfer enforcement precedent in August 2024: a €290M fine against Uber Technologies for unauthorized transfer of European drivers' personal data to servers in the United States.

The Uber enforcement action involved:

  • European driver data (taxi licenses, criminal background checks, medical records, travel histories) stored on US-based servers
  • Data transfer after the EU-US Privacy Shield was invalidated by Schrems II (July 2020)
  • Continuation of transfers without implementing Standard Contractual Clauses or other GDPR Article 46 safeguards for approximately two years post-Schrems II

The €290M fine is the EU's highest individual fine for data transfer violations and third-highest overall GDPR fine. It establishes that cross-border transfer violations — not just data breaches — carry catastrophic financial consequences.

The Dutch AP's Enforcement Priority Structure

The Dutch AP received 21,400+ GDPR complaints in 2023, deploying enforcement resources according to a published priority matrix. The three priority categories:

Priority 1 — Employee surveillance (43% of enforcement cases): Netherlands-headquartered companies have received repeated AP enforcement for employee monitoring: covert surveillance, disproportionate email monitoring, and geolocation tracking without adequate notice. Dutch labor law (Arbeidstijdenwet) provides additional protection beyond GDPR.

Priority 2 — Cross-border data transfers (31% of enforcement cases): Following Uber and the Dutch AP's co-investigation with Irish DPC on Cloudflare (2023), the AP has increased focus on data transfer compliance. Amsterdam's tech hub concentration — particularly cloud services, fintech, and scale-ups — creates high exposure for organizations transferring data to non-EU countries.

Priority 3 — Marketing and behavioral profiling (26% of enforcement cases): Cookie consent, behavioral advertising, and direct marketing compliance. The Dutch AP's guidance on "legitimate interest" for marketing is stricter than some EU equivalents — the AP requires documented balancing tests with specific evidence that the legitimate interest overrides data subject rights.

Cross-Border Transfer Requirements Post-Uber

The Uber enforcement establishes practical requirements for organizations transferring personal data from the Netherlands:

Transfer Impact Assessments (TIAs): Post-Schrems II, the EDPB requires TIAs for all transfers to third countries, assessing whether the legal protections in the destination country are "essentially equivalent" to EU protections. The Dutch AP's post-Uber guidance makes explicit that TIAs must assess:

  • Destination country's government access laws
  • Intelligence service capabilities in the destination country
  • Track record of government requests to the data importer
  • Available legal remedies for data subjects

Standard Contractual Clauses (SCCs) — not sufficient alone: The AP's Uber enforcement note clarifies that SCCs alone do not satisfy Article 46 where TIA reveals that destination country law enables government access to transferred data. Additional supplementary measures are required where SCCs are insufficient.

Supplementary technical measures accepted by the Dutch AP:

  • Encryption where the data importer does not hold decryption keys
  • Pseudonymization before transfer (identifier replacement) where re-identification is not possible by the data importer
  • Data minimization before transfer (removing data categories not needed by the importer)

The offline Desktop App architecture — processing all data locally, never transmitting to servers — eliminates the cross-border transfer question entirely for that processing activity.

Employee Data and Dutch Labor Law

The Dutch AP's 43% employee surveillance enforcement share reflects the interaction between GDPR and Dutch labor law (Wet bescherming persoonsgegevens arbeidsverhoudingen — the labor relations data protection act).

Key Dutch requirements for employee data:

  • Works council consultation: Dutch organizations with works councils (Ondernemingsraad) must consult the works council before implementing any employee monitoring system. This includes AI performance monitoring, communication monitoring, and attendance systems.
  • Proportionality assessment: Employee monitoring must be strictly proportionate to the stated purpose. Covert monitoring is generally prohibited; overt monitoring must be the least intrusive method available.
  • Processing limitation: Employee data collected for one HR purpose cannot be repurposed for another HR purpose without fresh legal basis.

For organizations headquartered in the Netherlands or employing Dutch staff, these requirements create specific technical documentation needs: the works council consultation record, the proportionality assessment document, and the processing limitation controls.

Netherlands-Specific PII Detection

For PII tools deployed in the Netherlands, Dutch-specific entity detection is required:

  • Burger Service Nummer (BSN): Dutch national identity number (9 digits) — used for tax, healthcare, social services
  • IBAN Netherlands (NL prefix): Dutch IBAN format with specific validation
  • Dutch postal codes (postcode): Format: 4 digits + space + 2 letters
  • Dutch DigiD: Government digital identity system identifier
  • Dutch healthcare numbers: BGZ/EP identifier formats for electronic patient records

Standard global PII tools may detect generic IBAN formats but may not validate Dutch BSN checksum or detect Dutch postcode format. Organizations processing Dutch national identity data should verify BSN detection coverage.

Compliance Approach for Dutch Organizations

For Netherlands-headquartered organizations:

1. Cross-border transfer audit:

  • Map all data flows from Netherlands to third countries
  • Identify all SCCs in place and their coverage
  • Conduct or update TIAs for significant transfer flows
  • Document supplementary technical measures for transfers where TIA reveals risk

2. Employee monitoring review:

  • Inventory all employee monitoring systems (including AI tools)
  • Verify works council consultation records
  • Confirm proportionality assessments are documented

3. Dutch-specific PII coverage:

  • Verify BSN detection in deployed PII tools
  • Verify Dutch postal code and IBAN detection
  • Test Dutch language NER accuracy for Dutch-language documents

4. Amsterdam tech hub exposure:

  • For startups and scale-ups: document data architecture decisions that minimize cross-border transfer (EU-region cloud services, local processing options)
  • For cloud service providers with EU-US architecture: document transfer mechanisms and TIA methodology

Sources:

Pregătit să vă protejați datele?

Începeți să anonimizati PII cu 285+ tipuri de entități în 48 de limbi.