Last updated: 7 November 2026
Data retention for security records UK means applying UK GDPR's storage limitation principle to CCTV footage, access control logs, visitor books, alarm records and incident reports — keeping each only as long as its stated purpose requires. There's no single statutory number, but Pulse Operations notes that the ICO's informal benchmark for routine CCTV is 31 days, after which footage should be deleted unless flagged for an incident or legal request.
Key Takeaways
- The ICO identifies 31 days as a standard default retention period for most commercial CCTV systems, per Logbook.co.uk, citing ICO guidance (2025).
- Pulse Operations advises that UK GDPR sets no fixed statutory retention period for security records — organisations must justify retention against the storage limitation principle instead.
- The ICO can fine organisations up to £17.5 million or 4% of annual global turnover for the most serious UK GDPR breaches, per ICO Data Protection Fining Guidance (2024).
- Subject access requests for CCTV footage must be answered within one calendar month, extendable by up to two further months for complex cases, per ICO guidance (2025).
- From 5 February 2026, serious PECR breaches carry fines up to UK GDPR levels — up to £17.5 million or 4% of global turnover — replacing the previous £500,000 cap, per nibusinessinfo.co.uk (2026).
What counts as security records under UK data protection law?
Security records are any documented output of a surveillance or access control system that identifies, or could identify, a living individual — a definition that brings most physical security data firmly under UK GDPR. This covers CCTV footage, access control logs from keycard or fob systems, visitor sign-in books, alarm activation records, incident reports, and body-worn or vehicle camera footage where fitted.
Each category counts as personal data under the Data Protection Act 2018 — the UK statute that works alongside UK GDPR to govern how organisations process information about identifiable people — the moment a person can reasonably be identified from it, whether by face, name, car registration or employee ID. A visitor log that records a name, company and time of arrival is personal data just as much as a CCTV clip showing someone's face.
This matters operationally because every one of these record types needs its own retention decision. A site running CCTV, door-entry logs, a paper visitor book and an incident log on four different systems has four different retention clocks to manage — and most compliance failures start with nobody owning that list. Pulse Operations builds all of this into one record: incident logging and a tamper-evident daily occurrence book sit alongside patrol evidence and access data in a single system, so there's one retention policy to apply rather than four forgotten ones (see how Pulse Operations's security platform handles this in practice).
What does UK GDPR require for how long security records can be kept?
Pulse Operations explains that UK GDPR's storage limitation principle — one of the six core data protection principles set out in Article 5(1)(e) — requires that personal data be "kept in a form which permits identification of data subjects for no longer than is necessary for the purposes for which the personal data are processed." There is no fixed number of days or months written into the law itself.
Instead, organisations must be able to justify, purpose by purpose, why a record is still held. The ICO's guidance on storage limitation sets out that a business must review retained data periodically, delete or anonymise it once the purpose has been served, and document the reasoning. For security footage, the usual purpose is detecting and investigating incidents — once that window has safely passed with nothing flagged, the justification for holding the footage disappears.
This is precisely why a blanket "keep everything for a year" policy is risky rather than cautious. It inverts the burden UK GDPR actually imposes: the organisation must justify retention, not justify deletion.
Is there a legally mandated maximum retention period for CCTV footage in the UK?
No UK statute sets a fixed legal maximum or minimum retention period for CCTV footage — the figure most businesses rely on is guidance, not law. The widely cited benchmark is 31 days, which the ICO identifies as a standard default retention period appropriate for most commercial CCTV systems, per Logbook.co.uk, citing ICO guidance (2025).
That figure works as a starting assumption, not a rule that fits every site. A quiet office reception might reasonably justify 14 days. A car park with a history of theft, or a construction site with valuable plant equipment, might justify 60 or 90 days as a documented, risk-based exception. What the ICO expects is that whatever number a business picks, it can explain why.
The Home Office's Surveillance Camera Code of Practice — the statutory code issued under the Protection of Freedoms Act 2012, the Act that also created the role of Surveillance Camera Commissioner — reinforces the same principle for relevant authorities and strongly encourages private operators to follow it: images should be retained no longer than necessary for the stated purpose, and the purpose should be documented before the system is even installed.
One important exception: once footage captures or relates to a flagged incident — a theft, an assault, a near-miss — it should be pulled out of the routine deletion cycle and retained separately for as long as the investigation, insurance claim, or legal proceeding requires. That decision needs its own written record, not a verbal "we kept that one because."
Who is responsible for setting and enforcing retention periods for security records?
Accountability for retention sits with the data controller — the organisation (not an individual employee) that decides why and how personal data is processed, as defined under UK GDPR. In practice, most mid-sized security and facilities operators assign day-to-day ownership to an operations manager or a named data protection lead, with sign-off from a director where the organisation has no dedicated Data Protection Officer.
Where a security company manages CCTV or access control on behalf of a client site, the contract should state plainly who the controller is — usually the client — and whether the security provider acts as a processor, handling the data strictly on the controller's instructions. This distinction decides who answers subject access requests, who sets the retention period, and who carries liability if records are mishandled. Getting this wrong in a contract is a recurring gap in tender submissions; per Pulse Operations's guide, how to win your next security tender, GDPR policy and clear data-handling roles sit among the pass/fail compliance gates a bid must clear before quality is even scored.
Enforcement in practice means someone checks, on a schedule, that deletion is actually happening — not just that a policy document says it should. A platform that enforces retention automatically removes the human-error risk of someone forgetting to purge footage manually.
How should a business determine an appropriate retention period for its sites?
A defensible retention period is one set against documented purpose and risk, not copied from a template. The right method starts by asking what the record is for — crime deterrence, incident investigation, insurance evidence, access auditing — and how long that purpose realistically takes to be served.
A practical approach for multi-site operators:
| Record type | Typical purpose | Illustrative starting point | Extend only if |
|---|---|---|---|
| Routine CCTV (no incident) | Deterrence, general monitoring | ~31 days (ICO default benchmark) | Site risk profile justifies longer |
| Incident-flagged footage | Investigation, evidence | Length of investigation/claim | Police or insurer require original copy |
| Access control / keycard logs | Audit trail, building security | 3–6 months (illustrative) | Ongoing HR or security investigation |
| Visitor sign-in records | Fire safety, site access audit | 3–12 months (illustrative) | Contractual or insurance requirement |
| Incident reports | Legal, insurance, HR record | Several years (illustrative, risk-based) | Litigation limitation period applies |
These are illustrative starting ranges, not fixed rules — each must be justified against the specific site's risk and documented, not borrowed wholesale from a different business. For higher-risk sites — those with a recent incident history, high footfall, or valuable assets — a longer default may be defensible, but it has to be written down and reviewed, not just assumed.
"The opposite. We show clients the gaps as well as the hits — if there were no patrols in a period, the portal says so. The first time a client sees you being honest about a miss, they believe every number after that. Transparency is the cheapest client retention there is." — Mo Hassan, Founder, Pulse
That same logic applies to retention records: a defensible policy is one that can show its working, not one that simply asserts compliance.
What does the ICO and the Surveillance Camera Code of Practice actually say?
The ICO's guidance on video surveillance including CCTV sets out post-deployment governance expectations: organisations must have a retention schedule, review it, and be able to respond to subject access requests within statutory timescales. Subject access requests must be answered without undue delay and within one calendar month of receipt, extendable by up to two further months for complex requests, per the ICO's guide to subject access (2025). For home CCTV systems specifically, the ICO confirms the same one-calendar-month baseline applies, per ICO guidance on home CCTV systems (2025).
The Surveillance Camera Code of Practice, issued under the Protection of Freedoms Act 2012, sets twelve guiding principles for relevant authorities operating surveillance systems, including that use must be for a specified, legitimate purpose and images retained for no longer than necessary. While the Code technically binds public authorities such as councils and police forces, the ICO treats it as good-practice benchmark for private operators too — a commercial landlord, shopping centre, or residential block ignoring it entirely has little defence if challenged.
A one-month SAR deadline sounds generous until a request lands on a Friday for footage spread across six separate DVRs with no index of what's retained where. This is the exact problem a single evidence system is built to solve: when every checkpoint photo, incident log and patrol record lives in one searchable platform rather than scattered hard drives, pulling a defined window of footage or log data for a SAR becomes a lookup, not an archaeology project.
What are the penalties for incorrect retention or disposal of security records?
Getting retention wrong carries real financial exposure under UK GDPR, not just reputational risk. The ICO can issue fines of up to £17.5 million or 4% of annual global turnover, whichever is higher, for the most serious breaches, per ICO Data Protection Fining Guidance (2024). Lower-tier infringements still carry fines of up to £8.7 million or 2% of global annual turnover, per nibusinessinfo.co.uk (2026).
The regime has just got sharper. From 5 February 2026, the Data (Use and Access) Act 2025 raised the maximum fine for serious breaches of the Privacy and Electronic Communications Regulations (PECR) — the rules governing electronic communications and, by extension, some surveillance-adjacent processing — to UK GDPR levels of up to £17.5 million or 4% of global turnover, replacing the previous £500,000 cap, per nibusinessinfo.co.uk (2026). Separately, every organisation processing personal data must pay the ICO's annual data protection fee, which currently ranges from £52 for small organisations with turnover under £632,000 or fewer than 10 staff, up to £3,763 for large organisations, per GDPR Ledger (2025).
Beyond ICO fines, over-retained footage creates its own liability: the longer personal data sits around, the longer it's exposed to a breach, a lost laptop, or an uncontrolled third-party request. Under-retention carries risk too — deleting footage that's already been flagged for a police investigation, insurance claim, or employment tribunal can amount to spoliation of evidence, with its own legal consequences separate from data protection law entirely.
In-house CCTV review vs an operations platform: where manual retention breaks down
Manually managing retention across a DVR, a door-entry system and a paper visitor book means someone has to remember three different deletion schedules, prove they've actually happened, and locate the right footage fast when a SAR or police request arrives. This works at a single small site with one person responsible. It breaks down the moment an operator runs multiple sites, multiple shifts and multiple record types.
| Approach | Retention control | SAR/evidence retrieval | Audit trail |
|---|---|---|---|
| Manual (DVR + paper logs) | Relies on someone remembering to purge | Manual search across separate systems | Easy to dispute, hard to prove |
| Spreadsheet-tracked policy | Policy exists but enforcement is manual | Faster if spreadsheet is kept current | Still relies on honesty, not system design |
| Single operations platform | Retention rules enforced by the system | One searchable record across sites | Tamper-evident, time-stamped by design |
This is the gap Pulse Operations's platform is built to close. Its audit log is hash-chained using SHA-256 and tamper-evident, with a built-in integrity check that walks the whole chain — so when a retention or SAR question comes in, there's one verifiable record rather than a reconstruction exercise across separate systems. The officer app is offline-first with self-healing sync, meaning records captured on a patrol with no signal still land in the same audit trail once connectivity returns.
At a landmark mixed-use development in West London, Priority First — a sister company that shares the same majority owner as Aether Agency Ltd, which runs Pulse — needed to prove which of 152 checkpoints across retail, residential, plant rooms and service yards had actually been walked, not just promised. Pulse Operations made every checkpoint photo-mandatory: a missed area shows as a gap in the record, not a dispute raised six weeks later. Since going live in February 2026, the site has logged over 540 patrols across 152 photographed checkpoints with 11 officers inducted onto one system (production data, July 2026). The same tamper-evident logging that proves a patrol happened is what makes a retention and disclosure request answerable in minutes rather than days.
Your data retention for security records checklist
- List every security record type held on site — CCTV, access logs, visitor books, alarm records, incident reports — and who controls each.
- Set a documented retention period for each record type, starting from purpose (deterrence, investigation, audit) rather than a copied template.
- Default routine CCTV to a short window — around 31 days is the ICO's commonly cited starting benchmark — unless a documented site risk justifies longer.
- Separate incident-flagged footage from the routine deletion cycle immediately, with a written reason and review date.
- Name a responsible owner for enforcing retention and answering subject access requests within the one-month statutory deadline.
- Confirm controller/processor responsibilities in every client contract before a security provider is given access to CCTV or access systems.
- Review retention periods at least annually, and record that the review happened.
- Use a single evidence system so footage, logs and incident reports can be located and disclosed quickly, rather than hunting across separate DVRs and spreadsheets.
FAQ
How long can CCTV footage be legally kept in the UK?
There is no fixed legal maximum, but the ICO's commonly cited default benchmark is 31 days for most commercial CCTV systems, per Logbook.co.uk, citing ICO guidance (2025). Footage can be kept longer where a documented, risk-based reason exists, such as an ongoing investigation.
Does UK GDPR set a specific number of days for retaining security records?
No. UK GDPR's storage limitation principle requires data to be kept only as long as necessary for its stated purpose, without fixing a specific number of days or months in the legislation itself. Organisations must set and justify their own periods, per ICO guidance on storage limitation.
What happens if a business keeps CCTV footage for too long?
Over-retaining footage breaches the storage limitation principle under UK GDPR and increases exposure if a breach occurs, since more personal data is held than necessary. The ICO can issue fines of up to £17.5 million or 4% of global turnover for the most serious breaches, per ICO Data Protection Fining Guidance (2024).
How quickly must a business respond to a request for CCTV footage?
A business must respond to a subject access request without undue delay and within one calendar month of receipt, extendable by up to two further months for genuinely complex requests, per ICO guidance (2025). The same one-month baseline applies to home CCTV systems, per the ICO's home CCTV guidance (2025).
Do access control and keycard logs need a different retention policy to CCTV?
Yes — access logs typically serve a different purpose (building audit and security) than CCTV (deterrence and incident evidence), so they often warrant a different retention window, commonly longer than routine CCTV but still justified by purpose. Each record type should have its own documented retention period rather than sharing a single blanket policy.
Who is legally responsible for setting retention periods on a client site?
The data controller — usually the client organisation that decides why CCTV or access data is processed — is responsible, though a security provider acting as processor may be instructed to manage retention on the controller's behalf. Contracts should state this relationship explicitly, which is also something tender evaluators check for, per Pulse Operations's guide, how to win your next security tender.
What should a business do with footage of a flagged incident?
Incident-flagged footage should be removed from the routine deletion cycle immediately and retained separately for as long as the investigation, insurance claim, or legal proceeding requires, with the reason documented in writing. Deleting flagged footage too early can amount to destroying evidence, which carries risks well beyond data protection law.
Proving retention compliance with Pulse Operations
Retention policy only works if the underlying records are trustworthy, searchable and genuinely deletable on schedule — which is exactly the gap between a written policy and day-to-day enforcement. Pulse Operations brings CCTV-adjacent evidence, incident reports and the daily occurrence book into one platform with a hash-chained, tamper-evident audit log, so a retention review or a subject access request pulls from one verified source instead of several disconnected systems.
The same platform underpins Priority First's residential estate work across 16 buildings in central London — Priority First is a sister company sharing the same majority owner as Aether Agency Ltd, which runs Pulse — where every checkpoint completion moved from an unverifiable "round complete" call to 100% photo-verified records, now running at 4,100+ patrols since March 2026 (production data, July 2026).
If your security records are currently spread across a DVR, a spreadsheet and a filing cabinet, it's worth seeing what a single, retention-aware system looks like in practice. Get in touch with Pulse Operations to discuss a quote, or take the product tour to see how photo-verified evidence and a tamper-evident audit log work together.
Related Reading
- Security Patrol Frequency Best Practice UK (2026 Guide)
- How to Prove Security Patrols Happened (UK Guide 2026)
- Body Worn Camera Data Handling: UK Rules in 2026
Add pulse-operations.co.uk as a preferred source on Google
Back to all insights