Since July 7, 2026, every newly registered vehicle in the EU has been required to include an Advanced Driver Distraction Warning system, or ADDW — in practical terms, a camera aimed at the driver's face, running continuously, watching for signs of distraction. If you run a dashcam channel, edit driving footage, or handle in-cabin video in any capacity, this is worth understanding even if you never touch a car sold in Europe, because it's a preview of where camera-in-the-cabin regulation is heading more broadly.
What ADDW actually does
The system tracks eye gaze, head position, and eyelid closure to detect when a driver isn't looking at the road, and it triggers a warning based on speed-dependent thresholds — roughly six seconds of gaze-off-road at lower speeds, tightening to around three and a half seconds above 50 km/h. New vehicle models entering production picked this up starting in July 2024; as of this July, it applies to all new vehicle registrations, not just new model launches.
What the law does not do
The regulation specifies that the system isn't supposed to rely on facial recognition — it's meant to classify attention state, not identify who's driving. That said, the practical enforcement gap is real: the mandate governs the required function, not everything the hardware and software stack in a given car could theoretically do with the same camera feed. Manufacturers control what else that data touches, and that's not something drivers can verify from the driver's seat.
Two different privacy surfaces, and only one is yours to manage
It's worth separating two things that are easy to conflate. The first is the ADDW camera itself — built into the car, controlled by the manufacturer, not something you're exporting clips from for YouTube. The second is your own dashcam, whether that's a factory unit, an aftermarket one, or footage submitted to you by viewers of a dashcam compilation channel. That second category is the one creators and channel operators actually handle day to day, and it's not directly regulated by ADDW at all.
What ADDW does is raise the ambient stakes around all in-car cameras at once. As driver-facing cameras become standard equipment rather than a niche aftermarket product, footage from inside and around vehicles is becoming a much more scrutinized category generally — more coverage, more regulatory attention, more viewers who've started asking "wait, is that legal?" in the comments. Content that would have passed without much thought two years ago is more likely to get flagged, reported, or challenged today.
What that means if you export or publish dashcam and in-cabin footage
None of this changes what's technically identifiable in a piece of footage — it changes how much scrutiny that footage gets. If you're compiling submitted dashcam clips, posting your own driving footage, or sharing an incident clip for an insurance dispute, the same categories of information have always mattered. They just carry more risk of complaint or takeover now:
- Faces of other drivers, visible through windows or during close encounters
- Faces of pedestrians and cyclists caught in frame
- License plates of any vehicle visible in the shot, not just the one involved in an incident
- House numbers, street signs, and other location identifiers in residential footage
- Minors' faces, which carry the highest scrutiny and the least tolerance for a "we forgot" excuse
Why manual blurring stops scaling fast
For a single clip, blurring a plate or a face by hand in a video editor is annoying but doable. For a dashcam compilation channel running multiple submitted clips a week, or a real-estate or delivery-driver channel with a backlog of footage, manual masking becomes the bottleneck that makes editors quietly skip it — which is exactly the failure mode that turns into a takedown, a complaint, or worse.
That's the specific gap VideoBlur is built for: automatic per-scene detection and tracking for faces and license plates, run entirely on your Mac, so a ten-clip compilation gets the same treatment as a single clip without turning into an afternoon of manual masking. Detection runs once per scene and tracks between cuts, so it holds up on dashcam footage specifically — lots of cuts, lots of motion, plates and faces entering and leaving frame constantly.
If you're sitting on a backlog of dashcam or driving footage that needs faces and plates cleared before it goes out, VideoBlur handles both in one pass, entirely on-device.
See how it works→Where this is likely heading
ADDW is an EU vehicle-safety regulation, not a privacy law in the GDPR sense, but it's landing in a regulatory environment that's already moving toward more camera oversight generally, alongside things like the EU AI Act's provisions on biometric and emotion-inference systems. It would be an overstatement to say ADDW itself changes what you're legally required to blur in a YouTube video — it doesn't, directly. What it does is put driver- and cabin-facing cameras firmly in the public conversation, and that conversation tends to end with more scrutiny for anyone publishing footage of people who didn't agree to be filmed, not less.
If dashcam or in-cabin footage is part of what you publish, this is a reasonable moment to build face-and-plate blurring into your normal export workflow rather than treating it as an occasional, case-by-case decision.