Dashcams are legal across the United Kingdom, for private motorists and fleets alike. Personal, domestic use generally sits outside UK GDPR, but business use does not: once a dashcam serves a work purpose, ICO obligations apply. The immediate steps are registering with the ICO and paying the data protection fee where required, fitting in-vehicle signage with a published privacy notice, and switching audio off by default while setting a clear retention period.
TL;DR:
- Businesses must register with the ICO and pay the data protection fee if dashcam use involves recording customer deliveries or employee monitoring.
- All footage must have a clear purpose, with set retention periods and secure handling, including automatic deletion once expiration occurs.
- Audio recording inside vehicles should be turned off by default, and inward-facing cameras require a data protection impact assessment before use.
- Visible signage inside and outside the vehicle, along with a detailed privacy notice, is essential to meet transparency obligations.
- Proper dashcam positioning and anonymisation of faces and number plates reduce privacy risks and help ensure compliance during inspections or incidents.
Table of Contents
- Quick compliance checklist: what to do today
- Legal obligations under UK GDPR and DPA 2018
- Signage, privacy notices and transparency
- Retention, storage and secure handling of footage
- Audio and inward-facing cameras: proportionality and DPIAs
- Police requests, SARs and using footage as evidence
- Camera positioning, driver visibility and MOT considerations
- Practical policy and governance for fleets
- Guidance on third-party privacy rights when filming others in public spaces
- Legal implications of sharing or publishing dashcam footage online
- Differences between private individuals and commercial organisations using dashcams
- Best practices for anonymising or blurring faces and number plates
- Our perspective on privacy and evidence-ready installations
- Compliant tracker and dashcam installation from Thatcham Trackers
- FAQ
- Sources
Quick compliance checklist: what to do today
Before anything else, work out whether your dashcam use counts as business use. A sole trader doing school runs is different from a fleet recording customer deliveries, and that distinction decides whether the ICO data protection fee applies.
Once that’s settled, a handful of practical steps cover most of the immediate risk:
- Confirm whether your use is personal or business, and register with the ICO if required.
- Fit a visible in-vehicle notice and publish a privacy notice naming the controller and contact details.
- Turn audio recording off by default and write down why you’re recording and for how long.
- Set a retention period and delete footage automatically once it expires.
- Make sure footage can be exported in a standard, viewable format with timestamps intact for any police request.
Each of these takes an afternoon to put right and closes off the most common complaints the ICO receives about dashcam use.
Legal obligations under UK GDPR and DPA 2018
Dashcam footage becomes personal data the moment it captures an identifiable person: a face through a windscreen, a visible number plate, or a recognisable individual on a pavement. Purely private, personal use of a dashcam for journeys like commuting or family trips generally falls outside UK GDPR altogether. That exemption ends as soon as any commercial purpose enters the picture, whether that’s monitoring employees, recording customer deliveries, or running a private hire vehicle, according to ICO guidance for small organisations.
For businesses, the usual lawful bases are legitimate interests (preventing fraud, protecting drivers and vehicles) or legal obligation, where recording supports a specific regulatory duty. Whichever basis applies, write the decision down: what you’re recording, why, and how long you’ll keep it.
The ICO expects transparency, purpose limitation and proportionate security as standard. Where recording is particularly intrusive, such as inward-facing cameras or anything capturing audio, a Data Protection Impact Assessment becomes the expected starting point rather than an optional extra.
Signage, privacy notices and transparency
Transparency is the simplest obligation to meet and the one most often skipped. A clear notice inside the vehicle, visible to passengers and anyone who asks, should state that recording is taking place and give a route to further information.
- Place a sticker near the dashcam itself, worded along the lines of “This vehicle uses a dashcam for security purposes. See [website] for details.”
- Tell passengers directly when they get in, particularly in private hire or courier vehicles.
- Publish a privacy notice online naming the data controller, the purpose of recording, retention periods, and how to make a subject access request.
- State clearly whether audio capture is active, since this carries the highest privacy expectation, per ICO guidance on surveillance in vehicles.
Durable signage matters more than most businesses assume, since a sticker that peels off after a few months leaves no evidence that notice was ever given. Specialist suppliers such as PromoSigns UK produce vehicle graphics designed to survive daily use.
Pro Tip: Keep a dated photo of your in-vehicle notice on file; it’s the easiest way to prove transparency was in place if a complaint ever arrives.
Retention, storage and secure handling of footage
A retention period only holds up if it’s tied to a stated purpose. Security footage kept “just in case” with no deletion schedule is exactly what the ICO flags as poor practice, since regulators expect retention linked to clear business need and periodic deletion rather than indefinite storage.
Set a retention window that matches your purpose, whether that’s a rolling seven days for general fleet safety or a longer window tied to a specific incident, then automate deletion so footage doesn’t linger on devices or cloud accounts.
- Encrypt stored footage and restrict access to named individuals with a business reason to view it.
- Log every access, export and deletion so you have an audit trail if questioned.
- Choose cloud storage where remote access and backup matter, and local storage where bandwidth or cost rules it out.
- Export footage with intact timestamps in a non-proprietary, viewable format whenever police request it, following Gov.
Cloud-based retention also simplifies insurer evidence requests, a point covered in our dashcam cloud storage guidance.
Audio and inward-facing cameras: proportionality and DPIAs
Audio recording is more intrusive than video alone and should be switched off by default. The ICO’s position is explicit on this: audio capture inside a vehicle needs stronger justification than simply recording the road ahead, because it picks up conversations that have nothing to do with driving safety, as set out in ICO guidance on surveillance in vehicles.
Inward-facing cameras, common in fleet and private hire vehicles for driver safety, typically call for a Data Protection Impact Assessment before deployment. That DPIA should weigh the safety benefit against the intrusion into a driver’s working day.
Practical controls worth building in from the start:
- Give drivers a way to flag concerns or request footage review.
- Deactivate inward-facing recording outside working hours where the vehicle is used privately.
- Restrict who can review footage to a named, limited list, with access logged.
More detail on applying these controls sits in our vehicle tracking GDPR guidance.
Police requests, SARs and using footage as evidence
Police may reasonably ask for dashcam footage after a collision or incident, and cooperating is generally the sensible course. What matters is preserving the footage properly: GOV.UK guidance on CCTV systems states that footage should be provided in a viewable, non-proprietary format with timestamps intact. Where removable media is involved, guidance on recovery and acquisition of video evidence recommends transferring it to permanent storage promptly so nothing is lost and the chain of custody stays intact.
A subject access request works differently. Anyone identifiable in your footage can ask for a copy of data relating to them, and you’ll usually need to respond within a month, applying exemptions such as redacting third parties who also appear in the clip. Keep a record of every disclosure, whether to police or in response to a SAR, including who requested it, what was provided, and when. Where a request is unusual or legally ambiguous, get advice before releasing anything.
Camera positioning, driver visibility and MOT considerations
Where you mount a dashcam matters for safety and for passing an MOT. Top-centre, just behind the rearview mirror, keeps the unit out of the driver’s main sightline and away from the swept area the wipers clear, which MOT guidance on visibility treats as a potential failure point if obstructed.
A few habits avoid trouble at test time and on the road:
- Mount centrally rather than off to one side, where it’s more likely to intrude on the driver’s view.
- Check the unit doesn’t sit within the swept area before an MOT appointment.
- Allow for easy removal or repositioning if an inspector asks.
- Use privacy-masking features, where your camera supports them, to blur footage of neighbouring properties when parked, reflecting the approach in GOV.UK guidance on domestic CCTV.
Practical policy and governance for fleets
A written policy turns these obligations from a one-off task into something a fleet can actually run day to day.
- Set out the purpose of recording, the lawful basis relied on, and the retention period in one document.
- Define who can access footage, how access is logged, and how incidents or complaints are handled.
- Run a DPIA for any inward-facing or audio-capable system, consulting affected drivers and keeping a written record of the assessment.
- Review the policy periodically and rehearse how you’d respond to a SAR or police request before one arrives.
Central registers of fitted cameras, access rights and retention logs are a recognised part of good governance, mirrored in approaches such as the Lewisham Council CCTV and surveillance policy.
Pro Tip: Run a short incident drill once a year, simulating a police footage request, to confirm your export process actually works under pressure.
Guidance on third-party privacy rights when filming others in public spaces
Filming on a public road inevitably captures other people: pedestrians, cyclists, drivers in neighbouring vehicles. That’s generally lawful where the purpose is road safety and the capture is incidental rather than targeted, but it still carries obligations once footage is business use rather than purely personal.
Anyone identifiable in your footage has the same rights as anyone else whose personal data you hold. They can ask what you’ve recorded about them and request a copy, subject to redacting other people who also appear in the clip. Minimising unnecessary capture matters too: if your camera angle regularly catches a neighbour’s driveway or a specific individual’s daily routine rather than the road itself, that’s harder to justify as proportionate.
Guidance on domestic CCTV recommends minimising capture of neighbours and private property where recording reaches beyond what’s needed, and giving notice where it does. The same principle applies to dashcams parked on a driveway or left running outside a delivery address: angle the camera towards the road rather than a neighbouring window, and avoid parking in a fixed spot for long periods if the camera keeps running.

For fleets, this translates into training: drivers should understand that a dashcam fitted for safety isn’t a licence to film specific individuals repeatedly or to use footage for anything beyond its stated purpose. Keeping that boundary clear protects the business as much as it protects the people caught on camera.
Legal implications of sharing or publishing dashcam footage online
Posting dashcam footage online, whether to report dangerous driving or simply because a clip is dramatic, raises separate questions from recording it in the first place. Once footage leaves your own systems and reaches a public platform, anyone identifiable in it, through a face, a number plate or distinctive clothing, has an interest in how that footage is used.
For personal, non-commercial dashcam use, sharing an occasional clip for road safety purposes sits in a greyer area than routine business disclosure, but it’s not risk-free. Publishing footage that clearly identifies someone, particularly in a way that could embarrass or harm them, can expose the person sharing it to a complaint even where the original recording was lawful. Blurring faces and number plates before sharing anything publicly is the simplest way to reduce that risk.
For businesses, the position is firmer. If dashcam footage is business data, publishing it without a lawful basis for that specific use, separate from the basis for recording it, is a step most organisations should avoid without a clear policy reason and legal sign-off. Marketing footage, “driver of the week” style clips or social media posts built from fleet dashcams all fall into this category and need their own privacy assessment before release, not just a reliance on the original recording justification.
Where footage supports an insurance claim or a police investigation, sharing it with the insurer or the police directly is a different matter from posting it publicly, and carries far less risk. Keep those two uses separate in your own mind and in any policy you write down.
Differences between private individuals and commercial organisations using dashcams
The rules that apply to a single commuter’s dashcam and a 40-vehicle delivery fleet differ sharply, even though the hardware might be identical. Personal use for commuting, family trips or recreational driving generally sits outside UK GDPR altogether, which is why most private motorists never need to register with the ICO or write a privacy notice.
That exemption disappears the moment a commercial purpose enters the picture. A courier recording customer doorsteps, a driving instructor recording pupils, or a haulage firm monitoring driver behaviour are all business uses, and ICO guidance for small organisations treats them accordingly: registration, a published privacy notice, and a documented lawful basis all become expected rather than optional.
The scale of risk differs too. A single private car captures a handful of journeys a week; a fleet of vans captures thousands of hours of footage across multiple drivers, multiple routes and, often, inward-facing cameras pointed at employees. That scale is exactly why data protection and monitoring workers guidance expects employers to be more deliberate about transparency, proportionality and access control than an individual ever needs to be.
Practically, this means a sole trader with one van and a private family car sit in different compliance categories, even when the vehicles look the same from the outside. If your dashcam use touches customers, employees or contractual obligations, treat it as business use from day one rather than waiting for a complaint to clarify the boundary.

Best practices for anonymising or blurring faces and number plates
Reducing what your dashcam footage reveals about other people is one of the most effective ways to lower privacy risk, particularly before sharing clips beyond their original purpose.
Some practical habits make a real difference:
- Use blurring or pixelation tools before sharing footage externally, covering faces and number plates that aren’t relevant to the incident being reported.
- Keep an unedited original on secure, access-controlled storage for any police or insurance process, and only distribute the anonymised version more widely.
- Where dashcam software offers automatic face or plate detection, enable it as a default setting rather than relying on manual editing every time.
- Avoid capturing static shots of the same property or individual repeatedly, since that’s harder to justify as incidental and increases the identifiability of anyone in frame.
For fleets, build anonymisation into the standard workflow rather than treating it as an afterthought: anyone handling footage for marketing, training or public communication should know that blurring identifiable details is the default step before anything leaves internal systems. This keeps the organisation’s output consistent and removes the guesswork for whoever is handling the clip that day.
Technical anonymisation doesn’t replace the other obligations covered here. Retention schedules, access controls and lawful basis still apply to the original footage even after a shared copy has been anonymised, since the underlying recording remains personal data until it’s deleted.
Our perspective on privacy and evidence-ready installations
We advise on insurer-accepted tracking and dashcam hardware, and compliant installation sits at the centre of that. A professionally fitted, Thatcham-certified device gives insurers the certificate they expect and gives drivers footage that’s positioned correctly and ready to extract if an incident happens. Our dashcam laws guide covers the legal background in more depth.
— Thatcham Trackers
Compliant tracker and dashcam installation from Thatcham Trackers
We supply Thatcham-approved trackers, including Thatcham S7, Thatcham S5 and Thatcham S5 Plus, fitted nationwide by accredited engineers, alongside dashcams with remote live view for cars, motorhomes and fleets.
![]()
Every fitted tracker carries an immediate digital certificate, providing assurance to insurers regarding cover. For added security, our Casper Ghost-Like Immobiliser range pairs well with a fitted dashcam setup. If positioning or evidence extraction is part of your privacy planning, get in touch before booking a fitting.
FAQ
Can dashcam footage be used against you in the UK?
Yes, if footage shows a driving offence or contributes to evidence in an incident, it can be submitted to police or used in court proceedings. Footage should be handed over in a viewable format with timestamps intact to be useful as evidence.
Can police ask to see your dashcam?
Yes, police can reasonably request dashcam footage after a collision or other incident, and cooperating by preserving and exporting the clip is standard practice. Guidance on video evidence recommends transferring footage to permanent storage promptly so it isn’t lost.
Are neighbours allowed to have cameras overlooking my property?
Domestic CCTV and dashcams are generally permitted, but guidance recommends minimising capture of a neighbour’s property and providing notice where recording extends beyond your own boundary. The relevant domestic CCTV guidance sets out what reasonable use looks like.
What are the legal restrictions on dashcam positioning in the UK?
A dashcam should sit outside the windscreen’s swept area and away from the driver’s main sightline, as an obstruction here can cause an MOT failure under visibility rules. Top-centre behind the rearview mirror is the position least likely to cause problems.
Do I need to register with the ICO for a dashcam?
Registration and the ICO data protection fee generally apply once a dashcam is used for business purposes, rather than purely personal driving. Many small businesses fall into a lower fee tier but still need to register.