The biggest privacy risk with common area cameras is not simply that a camera is present. It is that a building collects more footage than it needs, keeps it for too long, or lets too many people view and share it. A camera intended to help investigate a lift incident can quietly become a record of residents’ routines, visitors’ movements and staff activity.
That distinction matters in a residential or mixed-use building. Cameras may cover lobbies, lifts, corridors, mailrooms, loading areas and garages—places people use repeatedly and often cannot avoid. Footage can reveal access patterns captured over time, show license plates recorded at entrances and include unrelated bystanders in footage who have nothing to do with an incident.
A useful reality check is: What security question does this camera answer? If the answer is vague—“it might be useful one day”—the camera’s purpose, position, access rules and retention period deserve a closer look.
The real risk is a chain of decisions
A camera does not create privacy risk in isolation. Risk grows through a chain: an unclear purpose leads to broad coverage; broad coverage produces more sensitive footage; weak access controls make casual viewing or disclosure easier; and long retention gives the footage more time to be misused or exposed.
Common area video can show when a resident leaves, who visits, which facilities someone uses and whether a person is regularly alone. A single short clip may seem harmless. Repeated footage can tell a much more revealing story. This is why data minimisation is central: collect only what is genuinely needed for a defined security purpose, rather than treating every visible detail as useful.
There is also a human risk. Staff, contractors, board members or residents may be tempted to look at live or recorded footage out of curiosity. Even when no clip is shared, unnecessary viewing intrudes on people’s privacy and can undermine trust in building management.
Start with purpose and data minimisation
Before approving a camera, write down the specific problem it is meant to address. Is there a recurring package theft at a particular entrance? A vehicle collision at a blind garage turn? An access-control issue at a secured door? A defined purpose helps determine whether a camera is appropriate—and how narrowly it can be configured.
Data minimisation means more than buying a camera with a lower resolution. It involves deciding what to collect, where to collect it, who needs access, how long footage is kept and whether a less intrusive measure could work. Better lighting, a repaired lock, a door closer or an access-control change may address the problem without recording a wide area.
Questions to ask before installation
- What specific security issue is this camera intended to address? Is video necessary, or would a less intrusive measure be effective? What is the smallest area the camera can cover to meet the purpose? Will it capture homes, windows, private balconies or areas where people expect greater privacy? Who will be authorised to view footage, and for what reasons? Where do exported clips end up, and who can open them? When will footage be routinely deleted?
For buildings in the UK, the organisation responsible for the system should consider its data-protection obligations, including the UK GDPR and Data Protection Act 2018. The exact requirements depend on who controls the system and how it is used. The ICO’s guidance on video surveillance is a useful starting point, but it is not a substitute for advice on a building’s specific circumstances.
Ownership and governance: decide who is accountable
“The building has cameras” is not an accountability plan. The HOA, freeholder, management company or another organisation may be responsible for deciding why the system operates and how footage is handled. That responsibility should be clear, documented and reflected in contracts with any security or camera-service provider.
Good governance separates authority to make policy decisions from permission to view footage. A board may approve the purpose, location and retention policy without giving every board member direct access to live or recorded video. Access should be limited to named, trained people who need it for an authorised task.
Set rules for access and disclosure
- Use individual accounts rather than shared logins, with strong authentication where available. Keep an access log that records who viewed, exported or disclosed footage and when. Require a stated reason for a search, such as a reported incident and a relevant time window. Set a documented process for responding to requests from residents, police, insurers or legal representatives. Review vendor access and confirm how the vendor secures, stores and deletes footage. Train staff that viewing footage for curiosity, convenience or gossip is not acceptable.
Disclosure should be controlled rather than improvised. A request for a clip does not automatically mean that an entire recording should be sent. Check the purpose, authority and relevant time range, and consider whether people who are not involved can be masked or excluded. Keep a record of what was disclosed, to whom, why and by whom it was approved.
Do not email raw clips around or place them in a broadly shared folder. Before exporting anything, identify the destination, the people who can open it, how long it will remain available and how it will be securely deleted. A clip copied to a personal device or an unmanaged folder can outlive the original recording and its deletion schedule.
Camera placement and field of view control
Even a well-governed system can collect too much if cameras point in the wrong direction. Field of view should be reviewed on site, not just from a plan or a product demonstration. Walk through the space at the camera’s height and check what appears at the edges of the image, in reflections and through open doors.
Use the narrowest angle that still covers the relevant security point. A garage camera might need to capture a vehicle entrance, but not every parking bay. A lobby camera may need to show the entry door, but not a wide view into a resident lounge or across the mailroom. Avoid aiming cameras at windows or legal hold security footage private areas, and use privacy masking where suitable. A mask should be tested to ensure that it actually blocks the view rather than merely appearing to do so on a setup screen.
Think carefully before recording audio. Sound may capture conversations that are not relevant to the security purpose and can raise additional privacy concerns. Do not assume that audio should be enabled simply because the device supports it.
Check what else appears in the frame
Faces and number plates are not the only details that may need attention when footage is reviewed or shared. A practical redaction checklist should also consider:
- unit or flat numbers, door nameplates and access codes visible on screens; documents, delivery labels, parcels and computer monitors; reflections in glass, mirrors, polished surfaces and vehicle windows; children, visitors, workers and other unrelated bystanders; distinctive clothing, mobility aids or other details that could identify someone; audio, timestamps or camera labels that reveal more than the recipient needs.
Redaction is not a substitute for careful collection. If a camera routinely captures a sensitive area, it is usually better to fix the placement or field of view than to rely on editing every clip after an incident.
Retention periods and routine deletion
Keeping footage indefinitely “just in case” is one of the most common and avoidable problems. A long retention period increases the amount of footage exposed to unauthorised access, cyber incidents or accidental disclosure. It also allows detailed patterns of movement to accumulate.
Set a retention period that is proportionate to the purpose and local circumstances. There is no single number that suits every building. Consider how quickly incidents are normally reported, whether footage is reviewed routinely and whether a shorter period would still allow a legitimate investigation. Document the reasoning, tell residents how the system works and review the schedule when the purpose or risk changes.
Routine deletion should be automatic where possible, with a clear process for footage that must be preserved because of a specific incident or lawful request. A preservation hold should apply only to relevant footage, be access-controlled and include a review or end date. Once the reason to retain a clip has ended, delete it securely from the recording system and any authorised export locations, subject to applicable legal obligations.
Practice Lower-risk approach Warning sign Purpose Written, specific security purpose for each camera Installed “just in case” with no defined need Coverage Narrow field of view, tested on site Wide views into private or unrelated areas Access Named users, logged activity and a disclosure process Shared logins or casual viewing Retention Documented schedule and routine deletion Footage kept indefinitely by default Exports Secure destination, restricted recipients and deletion date Raw clips emailed or dumped in a shared folderMake the policy visible and review it
Residents and visitors should be able to understand that surveillance is in operation, who is responsible for it and where to find more information. Clear signs are useful, but a sign alone does not explain the purpose, retention period, access controls or how someone can make a privacy enquiry. Provide an accessible privacy notice with those details.
Review the system periodically and after significant incidents, changes to the building layout or changes in who manages the cameras. Check that camera angles have not shifted, access permissions are still appropriate, logs are being reviewed and deletion is working. If a camera no longer answers a real security question, consider removing it or switching it off.
What is the biggest privacy risk?
The biggest risk is uncontrolled, unnecessary surveillance: a building captures more than it needs, turns footage into a record of residents’ routines and fails https://dlf-ne.org/cctv-clip-shows-a-badge-and-a-screen-what-needs-to-be-redacted/ to govern access, sharing and deletion. Strong privacy practice starts before installation, with a clear purpose and restrained field of view. It continues through named access, careful handling of exports, proportionate retention and routine deletion.
There are no prices listed in this article because it is a practical guide to privacy and governance, not a product comparison or quotation. Camera and storage costs vary by building, system and service provider; a price alone does not tell you whether a proposed setup is proportionate or well managed.
One final check: What security question does each camera answer—and can the building answer where every exported clip goes, who can open it and when it will be deleted?
Share this article
- Facebook share X (Twitter) share