Resident Asked for Raw Security Footage: Do I Have to Give It?

2026-10-15T16:19:25Z

Iris-kim07: Created page with "<html><p> A resident asks to see the CCTV footage of an incident in the lobby, lift or car park. The request sounds straightforward: they want the recording, so should the building send them the raw clip?</p> <p> Usually, not automatically. In the UK, a recording may contain personal data about the resident and other people, including visitors, staff and neighbours. A request may need to be handled as a data protection request, but that does not mean a resident is entitl..."

<html><p> A resident asks to see the CCTV footage of an incident in the lobby, lift or car park. The request sounds straightforward: they want the recording, so should the building send them the raw clip?</p> <p> Usually, not automatically. In the UK, a recording may contain personal data about the resident and other people, including visitors, staff and neighbours. A request may need to be handled as a data protection request, but that does not mean a resident is entitled to an unedited copy of everything the camera captured. The building must consider what information it holds, who appears in it, why it is being requested and how other people’s privacy can be protected.</p> <p> This guide explains how to handle a <strong> resident footage request</strong> proportionately, when a supervised viewing option may help, and what good CCTV governance looks like. It is general information, not legal advice; the right response depends on the facts, your role and the applicable rules.</p> <h2> First, clarify what the resident is asking for</h2> <p> “Can I have the footage?” can mean several different things. The resident may want to confirm whether an incident happened, identify a person, support an insurance claim, report an offence or simply watch a particular moment. Ask what happened and, if they can, for the date, time, location and a description of the event.</p> <p> That is not an invitation to interrogate the resident or make them justify a valid data protection request. It is a practical way to locate the relevant recording, avoid searching more footage than necessary and understand whether there is an immediate safety or police issue. If the request is unclear, explain what details would help you find the material.</p> <p> Ask yourself: <strong> What security question does this camera answer?</strong> The same discipline applies when responding to a request. Identify the specific incident and relevant camera, rather than opening broad footage “just in case”.</p> <h2> Does a resident have a right to raw footage?</h2> <p> A person can ask for access to personal data about them. CCTV images can be personal data if a person is identifiable, directly or indirectly. But a request for access is not automatically a right to receive the original, unedited video file.</p> <p> The controller—the organisation that decides why and how the CCTV is used—must respond in line with data protection law. Depending on the circumstances, it may provide a copy of the relevant personal data, arrange another form of access, or withhold or redact material where necessary to protect the rights and freedoms of other people. The response should be based on an assessment of the particular footage, not a blanket rule that all requests are refused or all clips are handed over.</p> <p> In a block, the controller may be the residents’ management company, a landlord, a housing association or another organisation. A managing agent or security provider may operate the system on the controller’s behalf, but operating the cameras does not by itself make that provider the decision-maker for disclosure.</p> <h3> Why raw clips can be a problem</h3> <p> Raw footage may reveal far more than the incident. It could show other residents entering their homes, children, visitors, staff routines, access codes or activity unrelated to the request. Giving one resident a downloadable file can also make copying and onward sharing easy. These risks matter even if the resident has a legitimate reason for asking.</p> <p> Consider whether a narrower response would meet the request: for example, a short clip covering the relevant time, still images, redaction, or a supervised viewing option. Do not assume that blurring faces alone resolves every privacy issue. A person may still be identifiable by clothing, mobility aids, a distinctive routine, their location or the context of the scene.</p> <h2> Assess the request and protect the privacy of bystanders</h2> <p> Use a consistent process. Confirm the requester’s identity where appropriate, identify the time and camera, preserve relevant footage while the request is assessed, and check whether the recording contains information about the requester and others. Keep access restricted to staff who need to review the footage for this purpose.</p><p> <img src="https://images.pexels.com/photos/2958068/pexels-photo-2958068.jpeg?auto=compress&cs=tinysrgb&h=650&w=940" style="max-width:500px;height:auto;" ></img></p> <p> Before disclosure, consider whether third-party information can be removed or obscured without making the requester’s own data unintelligible. Redaction may involve blurring, masking, cropping or selecting a narrower sequence. A still image may be more proportionate than a video in some cases, but it is not automatically sufficient in every situation.</p> <p> Use this small redaction checklist—not just faces and number plates:</p> <ul> <li> Faces, vehicle registration plates and distinctive clothing or personal items.</li> <li> People reflected in glass, mirrors or polished surfaces.</li> <li> Entry systems, PIN pads, access cards, door codes and security procedures.</li> <li> Flat or unit numbers, name labels, post, documents or screens visible in the scene.</li> <li> Children, vulnerable people, staff-only areas and details that reveal a person’s routine.</li> <li> Audio, if the system records it, including conversations unrelated to the incident.</li> </ul> <p> Check the final export before sending or showing it. Confirm that the redaction is permanent and cannot be removed by playing the file in another application, adjusting settings or extracting individual frames. Keep a note of what was redacted and why.</p> <h2> When a supervised viewing option may help</h2> <p> A <strong> supervised viewing option</strong> can be useful where the resident needs to understand what happened but an unredacted copy would expose other people’s information. It may allow the resident to view a limited, relevant sequence in a controlled setting, with a trained staff member present.</p> <p> It is not a universal substitute for an appropriate access response. Consider whether <a href="https://realtytimes.com/new-headlines/cctv-in-elevators-and-common-areas-property-manager-responsibilities">realtytimes.com</a> the viewing genuinely gives the requester meaningful access to their personal data, whether the footage can be safely redacted, and what format is suitable in the circumstances. Do not let staff browse unrelated recordings or use the session as an informal investigation.</p> <p> If you offer supervised viewing, set clear rules: book an appointment, show only the relevant segment, prevent recording or photography where lawful and appropriate, and make a brief log of who attended, what was shown and when. Explain the arrangement to the resident in advance. Where an incident is serious, a police or insurer request may require a separate process; do not disclose on the assumption that any caller claiming to be an official is authorised.</p> <h2> Ownership and governance: who decides?</h2> <p> CCTV decisions should have an accountable owner. In a managed building, the board or management company may set the purpose and policy, while the managing agent and security contractor carry out defined tasks. Confirm the arrangement rather than relying on assumptions. Contracts and operating instructions should explain who can view footage, who handles requests, who authorises disclosure and who keeps the disclosure log.</p> <p> Governance should start before a request arrives. The organisation should be able to explain why each camera is there, what it captures, who can access recordings and how long they are kept. If the answer to “Why do we have this camera?” is merely “it might be useful one day”, revisit the need and proportionality of the installation.</p><p> <img src="https://images.pexels.com/photos/36852946/pexels-photo-36852946.jpeg?auto=compress&cs=tinysrgb&h=650&w=940" style="max-width:500px;height:auto;" ></img></p> Decision Good governance question Purpose What specific security or safety purpose does the camera serve? Access Which named roles can view live or recorded footage, and for what reason? Disclosure Who assesses requests and approves an export or viewing session? Storage Where do exported clips end up, who can open them, and when are they deleted? <h2> Camera placement and field of view control</h2> <p> Good disclosure practice cannot compensate for poor camera placement. Position cameras to cover the necessary area, not to watch residents’ everyday lives. A lens aimed at an entrance may unintentionally capture private doors, windows, neighbouring property or a wider section of a pavement than the building needs.</p> <p> Review the field of view when a camera is installed, moved or reconfigured. Use privacy masking where suitable, limit zoom and avoid capturing sound unless there is a clearly justified and lawful reason. Document the camera’s purpose and the areas it is intended to cover. If a camera’s view has drifted, or a new obstruction has prompted staff to widen it, check whether the change remains necessary and proportionate.</p> <h2> Retention periods and routine deletion</h2> <p> There is no single retention period that suits every building. Set a period based on the purpose of the system, how quickly incidents are normally reported, storage capacity and any applicable legal or operational requirements. Keep footage only as long as necessary for that purpose.</p> <p> Routine, automatic deletion is an important safeguard—not an administrative nuisance. A clip should not be kept indefinitely because it may become useful later. If an incident has been reported, preserve only the relevant footage while the matter is handled, restrict access, record why it is being retained and review the decision. Once the need ends, delete it in line with the retention schedule.</p> <p> Include exported clips in the same discipline. Ask: <strong> Where do exported clips end up, and who can open them?</strong> Avoid raw clips being emailed around or placed in shared folders without restricted permissions and a deletion date. Use an approved, secure transfer method, limit access to named recipients, and record the export and its eventual deletion.</p> <h2> What about fees or prices?</h2> <p> There is no standard price for supplying CCTV footage, and a resident should not be quoted an invented “processing fee”. A subject access request is generally free of charge. In limited circumstances, an organisation may charge a reasonable fee or refuse to act on a request that is manifestly unfounded or excessive, but that requires a case-specific assessment under the rules—not a default price list.</p> <p> Be clear about this in the response. If the building offers optional services outside a data access request, such as a separately requested professional copy for another purpose, do not blur that with the resident’s legal access rights. Explain any genuine charge, its basis and what the resident is choosing to receive before proceeding. If no fee applies, say so. A missing price list is not a reason to delay a request or invent a charge.</p> <h2> A practical response workflow</h2> <ol> <li> <strong> Acknowledge the request.</strong> Record when it arrived and explain that you will assess the relevant footage and third-party privacy.</li> <li> <strong> Pin down the search.</strong> Ask for the date, approximate time, location and incident details needed to find the clip.</li> <li> <strong> Preserve relevant footage.</strong> Prevent routine deletion of the specific material while the request is assessed, but do not retain unrelated footage unnecessarily.</li> <li> <strong> Confirm authority and roles.</strong> Identify the controller and the staff member authorised to review and decide the request.</li> <li> <strong> Assess and minimise.</strong> Review only the relevant footage; consider redaction, a narrower clip, stills or supervised viewing.</li> <li> <strong> Respond securely and on time.</strong> Explain the decision, any limits, and how the resident can raise a concern. Follow the applicable statutory deadline.</li> <li> <strong> Log and delete.</strong> Record what was reviewed, disclosed or withheld, who approved it, where any export is stored and when it will be deleted.</li> </ol> <h2> Common mistakes to avoid</h2> <ul> <li> Handing over an entire raw recording when a short, redacted segment would address the request.</li> <li> Refusing every request because other people appear, without considering redaction or another proportionate form of access.</li> <li> Letting staff watch footage out of curiosity or allowing informal viewing without a recorded purpose.</li> <li> Emailing clips to multiple people or dropping them into an open shared folder.</li> <li> Keeping footage indefinitely after an incident, with no review date or deletion plan.</li> <li> Assuming that blurring faces and plates is enough to protect the privacy of bystanders.</li> </ul> <h2> Final check before you respond</h2> <p> A thoughtful answer to a resident footage request is neither an automatic “yes” nor an automatic “no”. It is a documented, proportionate decision that gives the requester appropriate access while taking the privacy of bystanders seriously. Good camera placement, clear ownership, restricted access and routine deletion make that decision easier—and reduce the risk of a raw clip travelling further than anyone intended.</p><p> <iframe src="https://www.youtube.com/embed/4X29PMQSDKk" width="560" height="315" style="border: none;" allowfullscreen="" ></iframe></p> <p> Before sending anything, check: Is this the minimum footage needed? Have other people and sensitive details been considered? Is the export secure? Who can open it, and when will it be deleted? If you cannot answer those questions, pause and review the process before disclosing the recording.</p> <h2> Share this article</h2> <ul> <li> Share on Facebook</li> <li> Share on X (Twitter)</li> </ul></html>

Qqpipi.com - User contributions [en]

Resident Asked for Raw Security Footage: Do I Have to Give It?