Choosing how long to keep CCTV footage in a residential or mixed-use building is not a matter of picking a number that feels safe. A longer retention period can preserve evidence for a later incident review, but it also means holding more personal data for longer. A shorter period reduces that exposure, but may leave a genuine incident uncovered if nobody reports it in time.
The practical aim is to set a period that is necessary, proportionate and workable—and then make sure footage is routinely deleted when that period ends. Start with a reality check: What security question does this camera answer? If there is no clear answer, the camera’s purpose, position or continued use may need reviewing before you decide how long to retain its footage.
This guide is for property managers, building operators and boards considering common-area cameras in places such as lobbies, lifts, mailrooms and car parks. Rules vary by jurisdiction and by the organisation responsible for the system. Check applicable privacy, data-protection and surveillance requirements before adopting a policy.
Start with the operational need
A retention period should follow a defined operational need—not a general wish to keep anything that might someday be useful. Write down the purpose of each camera and what event the footage is intended to help investigate. For example, a camera may support the review of reported damage to a lift, an unauthorised entry into a controlled area or a vehicle collision in a garage.
Then consider the time it realistically takes for that type of incident to be discovered, reported and referred to the right person. A damaged parcel locker might be noticed quickly; a vehicle scrape in a shared garage may not be spotted until its owner returns. The period should reflect actual reporting and investigation workflows, rather than an arbitrary buffer.
Ask the onsite team what happens in practice. Who receives a report? How quickly can they request footage? Are incidents often reported after weekends or holidays? If reports regularly arrive after footage has been overwritten, investigate why before extending retention across every camera. The issue could be a slow reporting process, poor signage or a camera that does not capture the relevant area.
Check the rules before choosing a period
There is no single retention period that suits every building or jurisdiction. The relevant requirements may depend on who operates the cameras, Gallio PRO where the building is located, the purpose of recording, and whether footage is shared with law enforcement, insurers or other parties.
Before approving a period, check state local retention rules and any applicable national or regional privacy and data-protection requirements. In a UK setting, the organisation responsible for the system should consider data-protection obligations, relevant regulator guidance and its own documented purposes. In other jurisdictions, state, provincial, municipal or sector-specific rules may also apply. Do not assume that a common industry practice is automatically lawful for your building.
Keep a record of the guidance checked and the reasons for the decision. If the building operates across jurisdictions, or the system captures sensitive areas, seek advice from a qualified privacy professional or legal adviser. This article is general operational guidance, not legal advice.
Set the period from evidence, not instinct
Once the purpose and applicable rules are clear, use a documented decision process. The period should be long enough to support the stated operational need, but no longer than necessary. Consider the following:
- Discovery and reporting time: How long after an event is it usually reported? Review time: How quickly can authorised staff locate and assess relevant footage? Incident type: Do different locations or risks require different periods? System capability: Can the system apply different settings by camera, or does it use one setting for all footage? Actual use: Are clips regularly needed near the end of the proposed period, or is footage rarely reviewed? Storage and access risks: Does keeping more footage increase the chance of inappropriate access, loss or disclosure?
Do not set a long period simply because storage is inexpensive or technically available. Data minimisation applies to how much footage is collected and how long it is kept. Conversely, do not choose a very short period just to appear privacy-conscious if the documented process cannot meet the building’s legitimate incident-review need. Record the rationale, review it periodically and change it when the evidence or circumstances change.
Control camera placement and field of view
Retention is only one part of surveillance governance. A camera that records too much will collect unnecessary footage every day, no matter how short the retention period is. Review each camera’s position, angle and field of view. Ask whether it can be aimed more narrowly, repositioned or masked to avoid capturing areas unrelated to its purpose.
For example, a lobby camera intended to help investigate forced entry may not need to capture the inside of a resident’s home through a glazed door. A garage camera may need to cover an entrance or vehicle route without unnecessarily recording neighbouring private areas. Use privacy masking or similar controls where available, and check the live view and recorded image after any adjustment.
Also review whether a camera is appropriate at all. Avoid installing cameras “just in case”. Document why each one is needed, who approved it and what area it should cover. Provide clear notices where required, and make sure the stated purpose matches what the camera actually records.
Decide who owns the decision
Camera decisions should not be made casually by whoever has access to the system. The board, owners’ association, landlord or other responsible body should establish who has authority to approve purposes, placement, retention and disclosure. The property manager may administer the policy, but the governance arrangement should be clear and recorded.
Assign named roles for routine operations. These may include an authorised person who can review footage after a reported incident, an administrator who manages user access, and a decision-maker who approves exports or exceptional retention extensions. Limit access to people who need it for their role. Curiosity is not a valid reason to view camera footage.
Set a written procedure for requests from residents, visitors, contractors, insurers and law enforcement. It should explain how requests are assessed, who approves them, how the decision is logged and what happens if footage must be preserved beyond the normal deletion date. An incident-related hold should be limited to relevant footage and reviewed when the need ends; it should not become a reason to keep everything indefinitely.
Make routine deletion real
A retention policy does not work unless deletion happens reliably. Configure the system to overwrite or delete footage automatically at the end of the approved period, where the technology allows. Confirm that the setting is correct for each camera and that it has not been changed during maintenance, an upgrade or a system reset.
Document how deletion works, who checks it and how exceptions are handled. Periodically verify that footage older than the approved period is no longer available in the system, backups or exported copies. If deletion is manual, assign responsibility and keep a completion log. A shared folder full of clips with no deletion date is not a retention process.
Before exporting a clip, ask two questions: Where will the export end up, and who can open it? Use a controlled, access-limited location—not a broadly shared drive or an informal email chain. Set a deletion date for the export, restrict permissions and record who received it and why. Use a secure transfer method when disclosure is authorised.
Keep a practical disclosure and redaction log
When footage is reviewed or shared, keep a log that records the date, requester, purpose, camera or area involved, authorisation, recipient and any action taken. Record whether footage was exported, the storage location and the planned deletion date. If no footage was disclosed, note that too.
Before releasing a clip, check whether people or information unrelated to the request need protection. Redaction is more than blurring faces and number plates. Use a small review checklist:
- Faces and vehicle registration details of people not relevant to the incident. Door-entry codes, keypads, access cards or other security credentials visible in the frame. Private interiors, documents, screens or personal information captured incidentally. Audio, if the system records it, and whether it is necessary and permitted to disclose. Other cameras or areas that reveal security arrangements beyond the request’s scope.
Keep the original secure where it must be preserved, and make a redacted disclosure copy when appropriate. Follow applicable rules for access requests and third-party information; do not promise a particular outcome before checking the relevant requirements.
Consider insurer needs without over-retaining
Insurance considerations footage can influence how quickly a building needs to identify and preserve a relevant clip after an incident. Ask the insurer or broker whether there are specific notification or evidence-handling expectations for particular claims, such as damage, theft or vehicle incidents. Confirm those expectations in writing where possible.
Insurance requirements do not automatically justify keeping all camera footage for an extended period. Distinguish between routine retention and a specific incident hold. Once a claim or investigation is identified, preserve only the relevant footage and related records for as long as there is a documented need, subject to applicable rules and advice. Review the hold periodically and remove it when it is no longer required.
Review the policy and measure whether it works
Retention settings should be reviewed when the building’s use changes, a camera is moved, an incident pattern shifts, technology is replaced or relevant rules change. A periodic review—at least as often as the organisation’s governance process requires—can also reveal whether clips are being requested too late, access is broader than necessary, or a camera no longer serves a clear purpose.
Decision area Question to document Purpose What specific security or operational question does the camera answer? Field of view Can the camera cover less space while still meeting that purpose? Retention How long does reporting and review realistically take? Governance Who approves access, exports and exceptions to routine deletion? Deletion How will the organisation verify footage and exports are deleted on time?A note on prices and sharing
No prices are listed in this article because it is about setting a proportionate retention policy, not comparing CCTV products or storage plans. Costs vary by system, supplier, storage method and building requirements; obtain current quotes if you are budgeting for changes.
Here's what kills me: if this guide is useful to your board or onsite team, share it using facebook or x (twitter):
- Share on Facebook Share on X (Twitter)
The bottom line
Choose a retention period by connecting a clear operational need to real reporting timelines, checking applicable rules and documenting the decision. Keep camera views as narrow as practical, assign ownership for access and disclosure, and make routine deletion verifiable. When an incident requires preservation, hold only the relevant footage, control where it goes and set a review and deletion date. The goal is not to keep everything for as long as possible; it is to retain what is genuinely needed, for no longer than necessary.