Germany autonomous vehicle data policy

Momenta's Munich Robotaxi Pilot Shows Germany Needs Data Disclosure Rules, Not Data Localisation

Uber and Momenta's supervised Munich pilot says nothing on where driving data goes. GDPR transfer rules already answer that; disclosure, not a ban, is the fix.

Munich Robotaxi Pilot at a Glance People of Internet Research · Germany 1+ Safety operators per ride A safety supervisor is on board ev… Nationwide KBA Level 4 test scope Granted July 2026; previously city… Free Pilot ride price Rides are free and non-commercial … peopleofinternet.com
Munich Robotaxi Pilot at a Glance People of Internet Research · Germany 1+ Safety operators per ride Nationwide KBA Level 4 test scope Free Pilot ride price peopleofinternet.com

Key Takeaways

On 18 November 2026, Uber and Momenta opened a supervised, free robotaxi pilot in northern Munich. Electrive reports that it covers large parts of the north of the city, including the neighbourhoods around the Olympic Park. Pre-registered riders who request UberX, Electric or Comfort may be offered an autonomous ride, with fixed pick-up and drop-off points. A safety supervisor is on board every trip. It is the first time riders in Germany can book such a vehicle through the Uber app.

The launch coverage is detailed on routes and rider access. It is silent on one point: where the data from these rides is processed and stored. Momenta is a Chinese company, and its driving AI learns from real-world driving data. That gap is the policy story.

What the permit does and does not cover

The pilot runs under test permits that Germany's Federal Motor Transport Authority (KBA) issued to Momenta. In July 2026, electrive reported that the KBA granted Momenta nationwide approval for Level 4 test drives in urban traffic. Momenta described itself as the first Chinese company to receive such approval. Before this, each city needed its own approval.

The same report stresses that this is a test permit, not an operating licence, and that further approvals are needed before commercial passenger service. The permit regime is about vehicle safety and road testing. Nothing in the coverage suggests it answers questions about personal data.

The strongest case for tighter rules

The case for tough data controls is serious. A robotaxi fleet continuously records streets, pedestrians, licence plates and the movements of paying passengers. Riders and passers-by in Munich did not choose to feed a foreign company's training pipeline. The European Data Protection Board has long flagged vehicles as a high-risk setting. Its Guidelines 01/2020 on connected vehicles and mobility-related applications, in the version dated 9 March 2021, treat mobility data as a privacy by design problem. They also recommend, where possible, processing data locally in the vehicle rather than sending it elsewhere. If the data leaves the EU, critics argue, the public cannot verify who can access it or for what purpose.

That argument is right on one point: citizens and regulators should be able to find out what happens to the data. It does not follow that the answer is a ban on foreign firms or a blanket localisation mandate.

GDPR already supplies the framework

The General Data Protection Regulation, Regulation (EU) 2016/679, already regulates this. Article 44 provides that any transfer of personal data undergoing processing, or intended for processing after transfer, may take place only under the conditions of Chapter V. Article 46 lists the appropriate safeguards that can make a transfer lawful. Data that stays in the EU needs no such mechanism. Data that leaves needs a legal basis and safeguards.

The regulation therefore does not require data to stay in Europe. It requires that, if it goes elsewhere, a lawful mechanism exists and can be shown. For a pilot with a handful of vehicles, safety operators and pre-registered riders, that is a manageable compliance exercise. The open question is not whether the law applies. It is whether the companies have done the work and will say so.

Why localisation mandates are the wrong tool

Autonomous driving improves through exposure to varied real-world data. Fencing off training data by nationality of the developer would slow safety improvements and push the best systems to test elsewhere. Germany has courted this testing with a nationwide permit route. Adding an unpredictable data-residency layer on top would signal that the rules change after the investment is made.

Localisation also confuses two separate risks. Where data sits is not the same as who can access it or what it is used for. A server in Frankfurt controlled from abroad can pose the same exposure as a server abroad. Purpose limits, access controls, retention periods and audit rights address that risk directly. Residency does not.

A proportionate path

The pilot is small, supervised and free, which makes it the right moment to set expectations before commercial scale. Three steps would help without chilling the technology:

The German data protection authorities, including the Federal Commissioner for Data Protection (BfDI), are the natural place to ask these questions. A short, public answer from Uber and Momenta would cost them little and would remove the one open issue in an otherwise carefully staged launch.

Germany has taken a pro-testing stance. It should pair it with transparency, because public trust in driverless cars depends on knowing where the data goes. Regulation should demand disclosure and enforce the transfer rules already in force, not close the market to firms based on where they were founded.

Sources & Citations

  1. CnEVPost: Momenta and Uber launch robotaxi pilot in Germany
  2. CnEVPost: Momenta cleared to test robotaxis across Germany
  3. GDPR, Regulation (EU) 2016/679 (EUR-Lex)
  4. EDPB Guidelines 01/2020 on connected vehicles
  5. CnEVPost: Momenta and Uber launch robotaxi pilot in Germany