Privacy Constraints on EU Route Data: DSGVO and Local Rules

Last-mile delivery fleets operating across the European Union generate a constant stream of route data: GPS coordinates, timestamps, driver identifiers, stop sequences, and delivery confirmations. Under the DSGVO (the General Data Protection Regulation, known in Germany as DSGVO and elsewhere as GDPR), most of this data qualifies as personal data because it can be linked to an identifiable driver. Fleet operators expanding into low-emission zones and multi-country corridors need to understand not just what they can collect, but what they must eventually delete.

What Counts as Personal Route Data

Route data becomes personal data the moment it can be tied to an individual, directly or indirectly. A vehicle's GPS trace alone might seem anonymous, but combined with a driver roster, shift schedule, or vehicle assignment log, it identifies a specific person's movements throughout the day. This matters for milieuzone compliance systems too: logging which driver entered a low-emission zone, at what time, and in which vehicle creates a personal data trail even if the primary purpose is emissions or access-restriction enforcement rather than employee monitoring.

Fleets should distinguish between operational data needed for routing and compliance (zone entry timestamps, vehicle emission class, route deviations) and data that reveals more than necessary, such as continuous minute-by-minute location history retained indefinitely. The DSGVO's data minimization principle requires collecting only what is proportionate to the stated purpose, whether that purpose is proof of low-emission zone compliance, delivery verification, or dispute resolution.

Retention Limits and Legal Basis

There is no single EU-wide retention period fixed in the regulation itself; instead, the DSGVO requires that personal data be kept "no longer than necessary" for the purpose it was collected for. In practice, this means fleets must define retention periods tied to concrete business or legal needs:

- Delivery proof-of-service data is often kept for the duration of a commercial dispute window, frequently a few years, aligned with national contract law.

- Route and zone-entry logs used purely for real-time compliance checks generally have a shorter useful life once the trip is verified.

- Payroll- or working-time-linked location data may need to follow labor law retention rules, which can differ by member state.

Because retention obligations intersect with national labor, tax, and civil procedure law, a single EU-wide policy rarely fits every country a fleet operates in. Legal basis matters as much as duration: processing route data for legitimate interest, contractual necessity, or legal obligation each carries different documentation requirements and different expectations for how