Vehicle gate logs and photographs: retention and privacy for UK sites

Decide what happens after the vehicle leaves

A gate log is useful when a manager needs to trace a recorded arrival, resolve an entry query or review an incident. Keeping every registration and photograph indefinitely is a different decision. Before introducing a digital register, agree what information you need, who can use it and when it should be removed. Otherwise a simple capture workflow can become an unmanaged archive.

This guide gives UK security companies and organisations running their own premises a practical way to prepare those decisions. It draws on ICO and NCSC guidance checked on 7 October 2026. The operational examples are recommendations to adapt to your site; buying a logging app does not, on its own, settle your data protection responsibilities.

Treat registrations and photographs in their real context

The ICO explains that a vehicle registration mark is personal data in most circumstances, depending on the context. A gate record may connect a plate to a visit time, contractor, permit or identifiable driver. A photograph may also include people or other vehicles. Do not assume the information falls outside data protection law simply because the main subject is a car.

Map the records your process actually creates: registration, photograph, entry and exit times, site, gate, guard and any permit information. Include copies downloaded for reports and any temporary paper register. This inventory is the starting point for a manageable policy, because deleting an app record says nothing about a spreadsheet saved elsewhere.

Name the organisation making the decisions

Under the ICO's definitions, a controller decides why and how personal data is processed, while a processor handles it on the controller's behalf. A premises operator, security contractor and software supplier can have different roles. Determine them from the actual arrangement rather than assuming the organisation providing the guards always owns every decision.

For a contractor, agree with the client who sets retention, approves disclosure and handles requests from drivers. Where a controller uses a processor, the ICO says a written contract or other legal act is required. Check that it covers the processing, security, assistance with individual rights and what happens to records when the contract ends. A general promise of confidentiality is not the whole arrangement.

Write a specific purpose before choosing the fields

Describe the operational question the record should answer. For example: tracing vehicle movements through staffed access points and reviewing disputed admissions. Then ask which fields are necessary for that purpose. A photograph, a registration and a driver telephone number each need their own justification; their availability in a form is not a reason to collect them.

Identify and document an appropriate lawful basis. If relying on legitimate interests, the ICO's guidance requires assessing the purpose, whether the processing is necessary and the balance against individuals' interests, rights and freedoms. Record the assessment. Do not present entry past a sign as automatic consent or treat the word security as a complete legal explanation.

Explain the process before recording

Give drivers clear information about vehicle logging and photography at the point of collection. The ICO's transparency guidance calls for accessible privacy information covering matters such as purposes, retention and sharing. For a gate operation, a prominent notice supported by an accessible fuller privacy notice is a practical arrangement to assess.

Make the notice match the actual workflow. If a guard takes a phone photograph, describe that plainly rather than implying there is only fixed CCTV elsewhere on site. Provide a useful contact for questions. The guard's brief should identify that contact and explain how to help someone who cannot access the online notice.

Review the notice when the process changes. Adding an external vehicle-data service, expanding the sites covered or using records for a new purpose should trigger a review of the data flow and privacy information. The website notice used for demo enquiries is separate from the notice your organisation needs for its own gate operation.

Assess plate recognition before deployment

The ICO's ANPR guidance recommends a data protection impact assessment before deployment and stresses necessity, proportionality and accuracy. A DPIA is legally required where processing is likely to result in high risk. Assess your proposed phone-based number plate reading in its actual setting; do not skip the assessment simply because a guard holds the camera.

Define the capture area and keep the photograph relevant to the vehicle being recorded. Rehearse a poor plate reading and the manual correction step. Priority Service's published workflow includes registration review before saving. That check helps produce a useful record, while the site's assessment addresses the wider effects of collecting and using the information.

Set a retention schedule you can justify and operate

The ICO says data protection law does not prescribe a universal minimum or maximum retention period for surveillance records. Your purpose determines the necessary period. A number such as 30, 90 or 365 days is therefore a proposal to justify, not an automatic compliance rule. Cheap storage is not a justification for keeping everything.

Separate routine visit history, vehicle photographs, current permits and incident-related material in your policy. They may serve different purposes and need different review points. For each category, state the period or trigger, the reason, the person responsible and how removal happens. Check any relevant contractual or legal requirement rather than copying another site's schedule.

Test the policy against the actual service. Ask how records and images are deleted, what happens to backups and how the supplier handles account closure. The current Priority Service feature descriptions advertise capture, permits, approvals and reporting; they do not establish an automatic retention scheduler. Agree the available implementation before relying on automated deletion.

Keep incident exceptions narrow and reviewable

A reported incident may justify keeping relevant information beyond the routine period, but it should prompt a specific decision. Identify the records, the reason for preservation, the authorised owner and a review date. Avoid suspending deletion for an entire organisation because one vehicle is involved in one dispute.

Consider this illustrative test: damage is reported near an entrance after a vehicle has left. The responsible manager identifies the relevant visit and photograph and records why they are being retained for review. Other routine records continue through the normal schedule. When the matter changes or closes, the manager reassesses whether the retained material is still needed.

The ICO's storage limitation guidance requires periodic review and removal or anonymisation when personal data is no longer needed. An exception register is a practical way to make that review visible. It can sit within your controlled management process; this is not a claim that the app provides a dedicated legal-hold function.

Control the phone and the exported report

Priority Service advertises guard, supervisor and administrator responsibilities, with CSV reporting for authorised administrators. Use the demonstration to check the access appropriate to your staffing arrangement. Give report access according to the task, review it when staff move or leave and decide who may send records to a client.

The NCSC recommends protecting devices with a suitable PIN or password and keeping devices and applications updated. Use supported phones for gate work and decide how a missing device is reported. If staff use personal phones, address that explicitly in your organisation's device arrangements.

A downloaded CSV is another copy to manage. Give exports an approved storage location, named owner and disposal rule. Check recipients before sending, and avoid retaining repeated full exports for convenience. Also ask whether vehicle images reach a phone gallery or personal cloud backup in your setup. Confirm the behaviour rather than assuming the app controls every copy.

Prepare for requests without handing over the whole register

The ICO's surveillance governance guidance says staff should recognise requests concerning access, erasure or restriction and route them efficiently. Teach the guard what to do when a driver asks for their record. Logging the request and referring it to the responsible contact is more reliable than an improvised promise at the gate.

An authorised reviewer should establish the request, locate relevant information and consider other people's data in any photograph or report. Redaction may require a separate tool or specialist process. Test retrieval and image handling with fictional records before launch; CSV export alone does not demonstrate a complete rights-response process.

Use a controlled disclosure procedure for other requests too. Record who receives information, why it is being shared and the secure method used. A request from a contractor, insurer or colleague is not a reason to circulate the site's complete vehicle history.

Run a policy rehearsal alongside the app demo

Before going live, ask your team to find a sample visit, correct a misread registration before saving, retrieve the associated photograph and produce a limited report. Then rehearse a privacy enquiry, an incident exception and the removal of records under your proposed schedule. Assign an owner to each unresolved step.

Review the published app features using Explore the app features below, and watch the simulated IN and OUT workflow on the demo page. Use Request a demo to discuss your sites, access roles and reporting needs. Bring your proposed retention schedule and ask how it can be implemented with the service.

Several ICO pages cited here are marked as under review following the Data (Use and Access) Act. The legitimate interests page was updated on 23 March 2026, and the NCSC device guidance was reviewed on 21 July 2026. Recheck the linked guidance when adopting or changing your procedure.

Vehicle logging for your operation

Explore the workflow, plans and demo options for your team.

• Security companies
• Construction sites
• Warehouses & logistics

Explore gatehouse management software