Back to blogTechnology

GDPR and HGV Drivers' Data: Photos, Location and Checks

Driver apps collect names, photos, locations and check records. What UK GDPR and ICO guidance expect from hauliers, with a retention schedule and privacy notice wording.

7 min readPublished 20 November 2026Updated 6 November 2026Alex Matei

Roll out a driver app and the first question in the yard is rarely about the checks. It is "are you tracking me?", usually followed by "where do the photos go?". Drivers are right to ask. A walkaround app collects their name, signature, the time they started work, a location and pictures taken on a phone, and that is personal data under UK GDPR.

This guide covers GDPR and HGV drivers' data in a haulage app: what you collect, which lawful basis is likely to fit, what the ICO says about vehicle and location monitoring, how long to keep records, and how to explain it to drivers in plain words. It is practical guidance, not legal advice, and for anything unusual you should speak to a data protection adviser.

What personal data does a haulage driver app collect?

Start with an honest inventory. For a typical digital walkaround and job workflow it looks like this:

  • Driver identity: name, login, employee or agency status
  • Licence, CPC and tacho card details and expiry dates held by the office
  • Check records: vehicle, trailer, time, answers, sign-off, nil-defect declarations
  • Photos of defects, loads and delivery points
  • A location stamp recorded at the moment a check or POD is submitted
  • Messages between driver and office
  • Timesheet entries, where you use them

Some of this can stray into more sensitive territory. A licence record may show medical restrictions, and that is health data. The ICO's guidance on data protection and monitoring workers explains that special category data such as health needs a condition for processing on top of a lawful basis, so keep medical detail to what the licensing rules actually require.

Which lawful basis covers walkaround checks, photos and POD?

The ICO says you must identify and document at least one lawful basis, and that consent is usually inappropriate in employment because of the imbalance of power between employer and worker. That matters: if your rollout email says "by using the app you consent", you have picked the weakest basis available.

The bases that usually fit a haulage operation:

  • Legal obligation. The ICO says this can apply where processing is needed to meet a specific statutory duty, and gives drivers' hours rules as an example. You need to identify the provision. Defect reporting and maintenance records tied to your operator licence undertakings are the obvious candidates.
  • Legitimate interests. For things like POD photos, messages and job records. The ICO expects a three-part test (purpose, necessity, balancing) and a documented legitimate interests assessment.

Write down which basis you rely on for each type of data before you go live, not after a driver complains.

Location data: a GPS stamp is not live tracking

There is a real difference between recording where a check was done and tracking where a driver is all day. HauliK, for example, records a GPS stamp at the moment a check is submitted. It does not track the vehicle or driver between checks.

Even so, a location tied to a named driver is personal data. The ICO's page on different methods of monitoring workers says you must inform workers and passengers of any vehicle monitoring. It also says you will rarely be able to justify monitoring during private use, and its examples describe tracking that the driver can switch off when off duty. If you also run telematics or dashcams, those carry their own considerations, and the ICO notes that dashcams recording audio present higher risk.

The practical rule for a stamp-at-check-time model: use the location for what you told drivers it is for, such as showing the check was done at the yard or at the trailer's drop location, and not as a back door to monitor breaks. Using data collected for one purpose for another without a fresh assessment is what the ICO calls function creep.

Photos taken on walkaround checks and deliveries

Photos are where drivers and office staff get careless without meaning to. A picture of a cracked lens is vehicle data. The same picture with a colleague's face in the background, or a member of the public at a delivery address, is personal data about someone who never agreed to anything.

Give drivers simple rules:

  1. Photograph the defect, the load or the delivery point, close up.
  2. Keep people out of shot where you can.
  3. Do not photograph customer paperwork that is not needed for the job.
  4. Take photos through the app where you can, so copies are not left in a personal camera roll.

How long should you keep driver check records?

The ICO's storage limitation guidance says UK GDPR does not set time limits for different types of data. You decide, justify it and write it in a retention schedule, then review and delete or anonymise what you no longer need.

For roadworthiness records you have a regulatory floor. The DVSA Guide to maintaining roadworthiness says drivers' defect reports must be kept for at least 15 months, electronic records are acceptable, and it recommends keeping nil defect reports for at least 3 months. Our article on how long vehicle inspection records must be kept covers the wider record set.

An example retention schedule for a fictional operator, Hartside Transport. Your periods may differ, so set your own:

RecordPurposeExample retention
Defect reports and rectificationRoadworthiness evidenceAt least 15 months, longer if an incident or claim is open
Nil-defect check recordsShow checks are doneAt least 3 months (recommended), many keep 15 months with defects
POD photos and signaturesBilling and disputesUntil the invoice is paid and the dispute window has closed
Driver messagesJob instructions and evidenceDecide a period and apply it consistently
Former driver profileRecords still heldReview when they leave; keep only what the records above need

Telling drivers: a plain-English privacy notice

The ICO says workers must be told about monitoring in a clear, accessible way and told again when it changes. A paragraph in the handbook that nobody reads is not much use. Put it in the rollout briefing as well.

Template wording you can adapt:

We use the HauliK driver app to record vehicle and trailer checks, defects, deliveries and messages. When you submit a check or a delivery, the app records the time and your phone's location at that moment. It does not track you between submissions. We use this to show checks and deliveries were done, to manage repairs and to deal with customer queries. We keep defect records for at least 15 months and other records for the periods in our retention schedule. You can ask for a copy of your data at any time by contacting the transport office.

If you already brief drivers on the app itself, add this to that session. Our driver app rollout guide covers the rest of the briefing.

Frequently asked questions

Do I need drivers' consent to use a walkaround check app?

Usually not, and the ICO says consent is generally inappropriate in employment. Most operators rely on legal obligation for roadworthiness records and legitimate interests for job records, documented before go-live.

Can I use check locations to discipline drivers?

Only if drivers were told that is a purpose and you have assessed it. Using check data to monitor breaks or behaviour when you said it was for evidence of checks is the kind of function creep the ICO warns about.

How quickly must I answer a driver's subject access request?

The ICO's subject access guidance says within one month, extendable by up to two further months for complex requests. In most cases you cannot charge a fee.

Is the ICO's monitoring guidance changing?

The ICO says its employment monitoring guidance is under review because of changes made by the Data (Use and Access) Act. Check the ICO site for updates before revising your policy.

Where HauliK fits

HauliK's driver app records checks, defects, photos and POD with a GPS stamp at the time of submission, not live tracking. That makes the explanation to drivers simpler and the records easier to justify.

You stay the data controller: you set the lawful basis, the privacy notice and the retention schedule. If you want to see exactly what a driver submits before writing your notice, start a 14-day free trial with no card and run a few walkaround checks yourself.

Note: This article is general information for UK transport operators, not legal or compliance advice. Requirements may change. Always check the latest DVSA guidance and confirm with your transport manager or compliance adviser.

Connect the working day

Run haulage operations and records in one system

HauliK connects checks, defects, jobs, proof of delivery and fleet records for UK transport operators.