Client Alert

Focus: EDPB Adopts Guidelines on Connected Vehicles

20 Apr 2021

Vehicles are becoming more than just a means of transportation, and the focus of European data protection regulators is increasingly shifting towards the collection and use of personal information generated by smart vehicles. The latest models integrate sensors and connected on-board equipment to collect and record vast amounts of personal information, such as very specific driving routes, locations visited, driving habits, and potentially even the driver’s well-being. Biometrics (such as fingerprints) are also increasingly used for authentication and identification purposes. And when interfaced with mobile applications, a host of other information about the driver and passengers (such as their interest in music, video, sports, social media and other related activities) can be collected by such smart vehicles.

A number of EU data protection authorities (DPAs) have in recent years published varied opinions on the processing of personal information by vehicle sensors, telematics boxes and driving applications (such as the German Federal Data Protection Commissioner and France’s CNIL). The European Data Protection Board (EDPB) has now weighed in on the topic by adopting Guidelines 1/2020 on processing personal data in the context of connected vehicles and mobility related applications (the “Guidelines”). Relevant stakeholders are advised to review and adjust their processing practices accordingly.

Takeaways for Relevant Stakeholders

Stakeholders using data generated by Connected Vehicles will need to review their data collecting, processing and sharing processes and procedures, and ensure compliance with the recommendations set out in the Guidelines and as summarised below. This will particularly include the following:

1. Determining whether your organization acts as a company responsible for the processing of personal information (data controller) in the complex eco-system of various stakeholders;

2. Conducting DPIAs as early as possible in the design process, even when this might not be legally required (as a matter of best practice);

3. Ensuring appropriate legal basis under the ePrivacy rules and the GDPR;

4. Integrating privacy by design and default into the Connected Vehicles’ setup;

5. Providing appropriate notices to individuals, and considering best ways and technological solutions to bring them to the attention of the individuals using Connected Vehicles;

6. Ensuring local/in-vehicle processing of raw data as much as possible, and otherwise consider applying appropriate anonymization or pseudonymization techniques to raw data;

7. Implementing appropriate technical and organizational security measures; and

8. Considering additional measures when processing location, biometric, and other data that could potentially reveal criminal offenses or other infractions.

Scope of the Guidelines

The Guidelines focus on “Connected Vehicles,” which are smart vehicles that are equipped with electronic control units (ECUs). The ECUs can be linked together via an in-vehicle network as well as connectivity facilities that allow sharing of information with other devices both inside and outside the vehicle. They can include mobile applications that might (i) connect to a vehicle’s entertainment unit or (ii) work as standalone applications that assist drivers or passengers (such as GPS navigation on smart phones). The EDPB does limit the scope of the Guidelines to mobile applications that are related to the driving environment. So other applications that suggest, for example, places of interest (such as restaurants or museums) are out of scope.

While the Guidelines do not cover employee-monitoring issues, they provide useful insights for various Connected Vehicles stakeholders on how to set up a system that is compliant with the EU General Data Protection Regulation (GDPR) and the ePrivacy rules. The wide spectrum of stakeholders that the Guidelines are directed towards, includes traditional actors of the automotive industry as well as emerging players from the digital industry. This includes but is not limited to vehicle manufacturers, equipment manufacturers, automotive suppliers, car repairers, automobile dealerships, vehicle service providers, fleet managers, motor insurance companies, entertainment providers, telecommunication operators, and road infrastructure managers.

Compliance with the ePrivacy Rules and the GDPR is Required

The EDPB leaves no room for doubt whether Connected Vehicles generate personal information. It notes that most of the data collected and processed through Connected Vehicles can be linked to one or more identifiable individuals. This can include directly identifiable data (such as the driver’s identity), as well as indirectly identifiable data. The latter may include, for example, the details of journeys made, the vehicle usage data (such as data relating to driving style or the distance covered), or the vehicle’s technical data (such as data relating to the wear and tear on vehicle parts). Metadata (such as vehicle maintenance status) may also qualify as personal information.

A Connected Vehicle is furthermore considered to be “terminal equipment,” just like any computer, smartphone or smart TV. Compliance with Article 5(3) of the ePrivacy Directive is therefore required. Organizations wishing to store data in a vehicle, or access such data, will need to obtain prior user consent under the ePrivacy rules, unless an exception applies. Additionally, any processing of personal information must also have a legal basis under Article 6 GDPR in order to be lawful. The EDPB provides one example of when user consent is not needed, i.e., when “processing is necessary to provide GPS navigation services requested by the data subject when such services can be qualified as information society services”.

Considering the above, the EDPB sets out a number of specific recommendations for organizations wishing to process personal information generated by Connected Vehicles. Many of the following key recommendations basically reiterate general obligations under the GDPR:

A. Data Controllership

While the EDPB does not consider in much detail which players in the Connected Vehicles eco-system are (jointly) responsible for the processing of personal information (data controllers), it does specifically call out as such:

  • Service providers that send the driver traffic-information, eco-driving messages or alerts regarding the functioning of the vehicle;
  • Insurance companies offering “Pay As You Drive” contracts; and
  • Vehicle manufacturers gathering data on the vehicles’ wear and tear to improve their quality.
B. Data Protection Impact Assessments (DPIA)

Connected Vehicles will often result in high risk processing; this will particularly be the case when data are processed outside the vehicle because of the potential sensitivity and scale of the data involved. Where this is the case, a DPIA will be required. The EDPB recommends that all responsible stakeholders conduct a DPIA as a best practice as early as possible in the design process, even where this would not be legally required.

C. Privacy by Design and Default

Connected Vehicle technologies need to be designed to minimize the collection of personal information, provide privacy-protective default settings, and ensure that individuals are well informed and have the option to easily modify their privacy settings.

Organizations should consider specific tools to allow effective exercise of individuals’ rights and control over their personal information. In particular:

  • A profile management system should be implemented inside the vehicle to store privacy preferences and assist individuals with changing their privacy settings at any time;
  • The system should centralize all of the individual’s privacy settings and preferences to facilitate individuals’ rights requests; 
  • Individuals should be enabled to stop the collection of certain types of personal information, temporarily or permanently, at any moment, unless there is a specific legal ground justifying continuous collection of specific data. These features should be implemented inside the vehicle, although it could also be provided to individuals through other means, such as dedicated applications.
  • In order to allow individuals to quickly and easily remove personal information stored on the car’s dashboard (e.g., GPS navigation history, web browsing), manufacturers should provide simple deletion functionalities, such as a delete button; and
  • The sale of a vehicle should trigger deletion of any personal information that is no longer necessary and the individual should be able to exercise his or her right to portability.
D. Transparency

Individuals need to be provided with a comprehensive GDPR-compliant notice that can be provided in layers. The first level should contain the most important information. The EDPB does not expand on what this information is, except to say that it should include information about data recipients (such as vehicle manufacturers or insurance providers).

Organizations can consider using (i)  concise and easily understandable clauses in the vehicle’s purchase or service contracts, (ii) other written forms, distinct documents (such as the vehicle’s manual) or an on-board computer; and/or (iii) standardized icons that can potentially reduce the need for vast amounts of written information. The icons should be used to let the individuals know when certain types of information (such as location) are being collected. The EDPB suggests a light coming on in the vehicle, or moving arrows on relevant screens.

E. In-Vehicle Processing

Organizations should consider processing raw data inside the vehicle - thus not transferring it to vehicle manufacturers or insurers. This includes individuals having direct access to the data generated by their vehicles and any associated applications, and being enabled to permanently delete any personal information before their vehicles are put up for sale.

Organizations should also consider “hybrid processing.” The EDPB suggests, for example, that insurance companies should not have access to raw driving data. The data should instead be processed in the vehicle (or by a third party service provider) to generate a “score,” which is then shared with insurance companies.

If it is necessary to transfer data outside the vehicle, organizations should instead consider anonymizing or pseudonymizing the data first. When anonymising, the responsible party (data controller) should take into account all processing involved which could potentially lead to re-identification of data, such as the transmission of locally anonymised data.

F. Security

Given that risks to security can endanger the lives of the driver of a vehicle and any number of other individuals, organizations need to consider a number of security measures:

  • Various forms of encryption (including encrypting communication channels, putting in place an encryption key management system and adequately protecting and updating such keys);
  • Ensuring data integrity (for example, by hashing);
  • Making access to personal information contingent on reliable user authentication methods (for example, passwords or electronic certificates);
  • Keeping vehicles’ vital functions separate from non-vital functions (such as “infotainment” systems);
  • Implementing technical measures that will allow vehicle manufacturers to rapidly patch security vulnerabilities during the entire lifespan of the vehicle;
  • Setting up an alarm system in case of an attack on the vehicle systems; and
  • Storing of a log history of any access to the vehicle’s information system, so that attacks or other potential anomalies can be detected.

Data Requiring Special Attention

The EDPB points out that the following three categories of personal information warrant special attention because of their potential sensitivity:

  • Location: Organizations are advised to (i) not activate location processing by default, (ii) point out to individuals that location has been activated by using icons (such as arrows that moves across the screen), (iii) provide options to deactivate location at any time, and (iv) define limited storage period for location data.  
  • Biometrics: Organizations should (i) provide for non-biometric alternatives (such as physical keys or codes to unlock a car); (ii) store the biometric templates/models in the vehicle, in an encrypted form (using a cryptographic algorithm and key management that comply with the state of the art); (iii) process raw data (used to make up the biometric template and user authentication) in real time without ever being stored (not even locally): (iv) limit the number of authentication attempts; and (v) adjust the biometric solution use (such as the rate of false positives/false negatives) according to the security level of the relevant access control.
  • Data revealing criminal offenses or other infractions: The EDPB notes that some categories of personal information from connected vehicles could reveal that a criminal offence or other infraction has been (or is being) committed (e.g., data indicating that the vehicle crossed a white line or the instantaneous speed of a vehicle combined with precise location data). When processing data revealing criminal offenses or other infractions, organizations should consider resorting to local processing whereby individuals have full control over the processing in question, and use robust security measures to ensure that there is sufficient protection against illegitimate access, modification and deletion of the data in question. Such processing should also be fully compliant with Article 10 GDPR.


Unsolicited e-mails and information sent to Morrison & Foerster will not be considered confidential, may be disclosed to others pursuant to our Privacy Policy, may not receive a response, and do not create an attorney-client relationship with Morrison & Foerster. If you are not already a client of Morrison & Foerster, do not include any confidential information in this message. Also, please note that our attorneys do not seek to practice law in any jurisdiction in which they are not properly authorized to do so.