Table 2.

Requirements for the processing of personal data derived from the GDPR.

Requirement	Realization	Section
Personal data may only be processed if prior consent is given.	The data collection software natively integrated with the vehicle does not collect and transmit any data by default. An individual vehicle only performs data collection if a consent object exists within our system associated with the vehicle.	Section 3.2
The collection of personal data may not exceed the scope of the associated consent.	The data subject consents to grant the data consumer access to an immutable set of sensors (project). Subsequent data acquisition by the data consumer can not exceed this scope.	Section 3.2
If consent was revoked, all associated data must be deleted from our system.	Personal data stored on our system is linked to the associated consent. If consent is revoked, we automatically delete the associated data.	Section 4.8
If consent was revoked, all associated data must be deleted from the infrastructure of the data consumer.	We notify the data consumer about the revocation via a message-based interface. The data provided to him always references the associated consent. Thus, he can carry out a targeted deletion on his infrastructure.	Section 3.5
If consent was revoked, associated data acquisition must stop; no further data may be collected.	Each vehicle communicates continuously with our cloud platform to stop individual data acquisitions if associated consent is revoked. The cloud platform will discard data the vehicle transferred before the revocation was propagated upon receipt.	Section 4.3 and Section 4.8
No more data may be collected than necessary (data minimization).	Each vehicle only transmits sensors required to fulfill the data demand of the data consumers for which associated consent exists. Data consumers specify demand according to their needs and can adjust the scope of data acquisition even after consent is granted.	Section 3.2