EU Driver-Facing Camera Law (2026): ADDW Privacy Guide for Drivers and Builders
From July 7, 2026, every new EU car must have a driver-monitoring camera (ADDW). Closed-loop on paper — real risk when footage leaves the car. bgblur.com guide for anonymization and Video Intelligence API distraction detection.
From July 7, 2026, every newly registered car, van, truck, and bus in the European Union must ship with an Advanced Driver Distraction Warning (ADDW) system — typically an infrared camera aimed at the driver's face that tracks gaze, head position, and attention. That deadline is phase two of the EU General Safety Regulation (GSR2) — the same package that added mandatory pedestrian AEB and tire monitoring; see explainx.ai's five mandatory EU car safety features guide for the full GSR2 context and Tesla FSD overlap.
The goal is road safety. The backlash — on Reddit, Cybernews, and across EU media — is about privacy: another camera pointed at your face, another sensor in a vehicle that already uploads telemetry, and unclear rules about what happens when that video leaves the car.
This guide explains what the law actually requires, where privacy breaks down in practice, and what engineers should build — including on-device distraction detection, anonymization before upload, and API patterns for fleets, insurers, and OEM debug pipelines.
Monitor driver gaze and head movement while driving
Activate automatically above 20 km/h (with provisions at lower speeds)
Warn when attention drifts — thresholds include roughly 6 seconds off-road gaze between 20–50 km/h, and 3.5 seconds above 50 km/h (per manufacturer implementation under type-approval rules)
Use visual distraction detection — lane-keeping alone is not enough; the driver must be observed directly
What the system must not do (on paper)
Per EU technical rules and GDPR framing:
No biometric identification of occupants (no facial recognition login, no identity matching)
Closed-loop operation — process only what is needed for the warning function
No unnecessary retention — don't store driver video beyond immediate function
No external transmission of cabin video to servers or third parties for ADDW itself
The European Commission's public messaging: "Smarter cars mean safer roads." Critics' messaging: "First it's your car, then your living room."
Both can be true. ADDW as a warning light is not the same as ADDW footage in a cloud bucket.
Why drivers are angry (and not wrong to ask questions)
The Reddit thread on EU driver cameras that hit 576+ upvotes isn't really about seatbelts. It's about precedent:
The hardware is permanent. Once every car has a driver-facing camera, software updates can change behavior — logging, upload, insurer scoring.
Manufacturers have a privacy track record. Reporting on automotive data misuse makes "trust us, it's local" a hard sell.
Inspection economics. Comments from the Netherlands note annual roadworthiness checks (APK) — will a working camera become part of compliance?
False positives hurt safety. Drivers report distraction systems that brake during overtakes or nag on long trips — safety tech that becomes distraction.
Deactivation is limited. Regulation allows manual deactivation of warnings or the system in some configurations — but obstructing the camera can trigger other vehicle behaviors.
The law says no authority mandate to record. The fear is capability without durable enforcement — the same gap GDPR was supposed to close, now inside the cabin.
The privacy gap nobody puts in the press release
Here's the distinction that matters for engineers:
ADDW does not require storing video. The privacy risk appears when someone decides to retain, upload, or share footage.
Real-time distraction detection only needs:
Frame-in → pose/gaze estimate → warning out
Optionally: event metadata (timestamp, distraction score, speed) — not a recognizable face
Problems start when video is used for:
Use case
Privacy risk
OEM debug after crashes
Identifiable driver faces in support tickets
Insurance telematics
Gaze scoring tied to identity or policy
Fleet management dashboards
Supervisors reviewing cabin clips
ADAS training data collection
Biometric video in ML pipelines
Warranty / legal discovery
Unblurred exports in evidence chains
GDPR still applies. Face and gaze data are personal data under the same framework covered in explainx.ai's EU AI Act vs US policy guide and Europe AI landscape 2026. Minimization, purpose limitation, and deletion aren't optional because the camera is labeled "safety."
Privacy-by-design means:
Process on-device — inference at the edge, in the ECU
Default to no recording — metadata-only event logs
Anonymize before any export — if video must leave the car, blur or anonymize faces first
Separate ADDW from infotainment cloud — different trust boundary, different retention policy
Reporting from Cybernews and automotive trade press: similar driver-monitoring requirements are expected in the US on 2027+ model year vehicles, aligned with NHTSA distraction-mitigation direction.
If you're building for one market, you're probably building for both. Design for EU closed-loop rules and you are well positioned for US state privacy laws (CPRA, etc.) and insurer scrutiny.
What builders should implement
1. On-device distraction detection (no cloud required)
You do not need to send raw video to a server to detect "driver looked at phone for 4 seconds."
2. Video Intelligence API — detect distraction, preserve privacy
For teams building fleet tools, aftermarket dash systems, insurer pilots, or OEM validation rigs — not every pipeline runs inside a homologated ECU on day one.
Regulation references accurate as of July 2026. Not legal advice — consult counsel for product-specific GDPR, type-approval, and US FMVSS/NHTSA compliance.
