Vehicle photos, data protection and retention: a guide for workshops

Photographing every car at check-in protects your workshop when a dispute comes up. But those photos are not neutral. They show a number plate, sometimes the customer's face or a passer-by, a parking permit on the dashboard, paperwork on the passenger seat. And they sit in a job alongside a name, a phone number and an email address. In other words, they usually count as personal data under GDPR-style data protection rules.

None of this is a reason to stop taking photos. It is a reason to take and keep them properly. Here are the essentials, in practical terms.

Why check-in photos are personal data

Personal data is information that identifies a person, directly or indirectly. A number plate linked to a customer record identifies the keeper or driver of the car, so it is generally treated as personal data, especially in a job that also holds the customer's name and contact details.

Then there is what a photo captures by accident: faces, documents visible inside the car, personal belongings. Again, the answer is method, not avoidance.

The principles to apply

1. A clear purpose

You photograph the car to record its condition at check-in and to be able to respond to a complaint. That is the purpose. Do not reuse the photos for something else without thinking it through: social media posts, marketing, sharing with third parties unconnected to the job.

2. A lawful basis

Data protection law requires a lawful basis for processing. For a workshop, recording vehicle condition usually relates either to performing the repair contract or to the workshop's legitimate interest in protecting itself against disputes. The choice has practical consequences, so confirm it with your adviser or data protection lead.

3. Data minimisation

Only capture what you need:

Frame the car, not the people.
Avoid detailed interior shots unless needed, and make sure no paperwork is legible.
Do not collect more customer information than the job requires.

4. Telling the customer

Customers should know their car is being photographed, why, how long the photos are kept, and how to exercise their rights. A line on the job card, a notice at the service desk and a link to your privacy notice cover most of it. Saying it during the walkaround ("I'll just take a few photos so we're both starting from the same place") is a useful addition.

5. Security

Photos need protecting against loss, theft and unauthorised access. Advisors' personal phones are a poor solution: no access control, risk of loss, mixed with private data, automatic backups to services you do not control.

6. A limited retention period

This is the principle most often overlooked, and the one workshops ask about most.

How to set a retention period

Data protection rules do not set a fixed period for check-in photos. They require that data is not kept longer than necessary for its purpose. So it is up to the workshop to set a period and be able to justify it.

A sensible approach splits it into two phases:

Routine retention: the period in which a complaint is realistic. In practice most bodywork complaints come at handover or within days of it. You can set a short period based on your own experience.
Dispute retention: if a complaint is open, keep the relevant photos until it is fully resolved, and make sure they are not deleted in the meantime.

There is no single period that suits every workshop. What matters is setting a period that fits your evidence needs, documenting it and being able to explain it. Use the guidance published by your data protection authority (the ICO in the UK) as a starting point, and take professional advice for unusual situations.

Once you have set the period:

Write it down in your privacy notice and your records of processing.
Actually apply it, ideally with automatic deletion.
Build in a dispute exception, so an open case is never purged automatically.

If you use software or an app

If a software provider stores the photos, they normally act as your processor. Data protection rules then require a contract setting out what they may do with the data. Check in particular:

Where the data is hosted, and whether it leaves your jurisdiction.
Who at the provider can access it.
Whether retention is configurable, and whether deletion is real.
Whether you can export your data at any time, including at the end of the contract.

These points are part of choosing a vehicle check-in app.

When a customer asks about their photos

Occasionally a customer will ask to see the photos you hold, or to have them deleted. Have a simple process ready: who handles the request, how you confirm the person's identity, and how quickly you respond. If photos are needed for an open complaint, explain why they are being kept for now and for how long.

Common mistakes

Keeping photos forever "just in case". That goes against the retention principle.
Leaving photos on personal phones. Security and control become impossible.
Posting customer cars online (before/after shots) without hiding the plate or getting consent.
Not telling customers their car is being photographed.
Deleting a job under dispute because of a badly configured automatic purge.

Check-in photo data protection checklist

Purpose defined and limited to recording vehicle condition
Lawful basis identified and confirmed
Photos framed on the car, no people or legible documents
Customers informed (job card, desk notice, privacy notice)
Photos kept off personal phones, access controlled
Retention period written down and applied
Exception for jobs under dispute
Processor contract with your provider, export available

Handled properly, photos remain your best protection: see timestamped check-in photos as evidence and how CheckAuto approaches documented check-in.

This article provides general information only and does not constitute legal advice. For a specific situation, speak to a qualified adviser, your data protection lead or your data protection authority.