Technically, a camera system in a residential complex isn’t very different from one in an office building; the difference is on the management side, and that’s where the problems come from. The recordings contain the daily lives of residents, guests, children and staff. A security company operates the system and the complex management supervises it; residents are both the people being recorded and, at times, the party requesting recordings. Below, how to cover common areas, how to prevent views into private areas, how to separate access and how to handle recording requests are explained from a technical perspective.
Requirements in residential complexes
A residential camera system is usually expected to do three things: identify who and which vehicle entered at entry points, help investigate damage and theft incidents in car parks and common areas, and let the security guard watch live and respond. Alongside these, three boundaries are put in writing before installation:
- Decision authority: Installing cameras in common areas is a matter for the owners’ assembly. The content of the decision and the required majority are determined under the Turkish Condominium Law and the complex’s management plan, with legal advice if needed. The technical design is based on this decision.
- Data responsibility: Recordings are personal data. Who holds the data controller role (in most cases the complex management; the security company is usually a data processor), the duty to inform and the retention period are determined under personal data protection legislation. For current guidance and decisions, the official website of the Turkish Personal Data Protection Authority is the reference.
- Purpose limit: The system is for common area security. Uses such as residents watching each other or management tracking service charge payments are outside its purpose.
Common area coverage table
Each area’s purpose and required image level differ. The table is a starting plan for a typical complex; the number and position of cameras are finalized in the site survey, not at the desk.
| Field | Purpose | Image level | Watch out for |
|---|---|---|---|
| Pedestrian entrance gate, turnstile | Identifying who enters | Diagnostics | Backlight; position the camera inside the gate, facing the person entering |
| Vehicle entry and exit | Plate and vehicle type | A separate camera for plates, a separate camera for the overview | Headlight glare; integration with the barrier and access system |
| Block entrance and lobby | People entering and leaving the block | Recognition–identification | Glass door reflections; mailboxes and the intercom panel |
| Elevator car | Vandalism and security incidents | Observation–recognition | Cabling with the elevator company; audio recording off |
| Indoor and outdoor car parks | Damage, theft, vehicle tracking | Observation; recognition at entrances and ramps | Behind columns; low light; vehicle headlights |
| Playground, walkways | General security | Observation | Don’t collect more close-up detail than needed |
| Waste area, technical room, generator | Unauthorized access, fire risk | Observation | In technical rooms, together with a door alarm |
| Perimeter wall | Unauthorized entry | Detection–observation | Views of neighboring plots and public roads should be limited |
A common mistake at pedestrian entrances is a camera looking from outside the gate inward, against daylight. The image shows a silhouette, not a face. Plate and barrier setup at vehicle entrances is a separate design topic; details are in the car park and vehicle entry camera system article.
A note on elevator cars
The elevator car is technically the hardest point because of the traveling cable running to the car. Spare cores in the traveling cable aren’t always suitable for Ethernet; in that case, converters carrying IP over coax or a twisted pair, or wireless bridge kits designed for elevator shafts, are used. Whatever the method, every change in the car is made with the approval and participation of the company responsible for the elevator’s maintenance. Unapproved intervention also puts the maintenance contract at risk.
Preventing views into private areas
The most common mistake with residential cameras is a wide-angle camera that sees apartment windows, balconies or the inside of doors along with the common area. This is the main source of resident complaints and legal risk. An angle labeled “we’ll adjust it later” during installation is often never adjusted. The rules:
- Cameras are positioned at an angle from which apartment windows, balconies, ground floor terraces and the inside of apartment doors aren’t visible. In floor corridors, cameras that continuously watch a particular apartment’s door are avoided.
- Where the angle can’t be changed, a static privacy mask is applied; it’s checked that the mask is applied not only to the live view but also to the recording. For methods, see the privacy masking in cameras article.
- No cameras are placed in changing rooms, toilets, showers or pool changing areas. If a camera is needed at the pool and sports area, a placement focused only on entry control, without a detailed view of the usage area, is chosen.
- If cameras have microphones, audio recording is switched off. Audio carries far more personal information than video.
- After installation, each camera’s view is documented against a possible resident objection: camera name, date, field-of-view screenshot and the mask applied. When an objection arrives, you have evidence in hand.
Separating security and management access
In many complexes, the recorder has a single admin password, and that password circulates among security guards, the manager, technical service and even some residents. In such a system, it’s impossible to know who watched and exported which recording. A shared password is responsibility with no owner. The right model is personal accounts and role-based permissions:
| Role | Live viewing | Recording playback | Export | Configuration |
|---|---|---|---|---|
| Security guard | Yes | Short look-back (defined period) | No | No |
| Security supervisor | Yes | Yes | With an approved request | No |
| Complex manager | Limited | For reviewing requests | Approves | No |
| Technical service | For installation and faults | No | No | Yes |
| Residents | No direct access | No | No | No |
Residents often ask to access cameras through a mobile app. But a setup in which all residents see all cameras and recordings turns the complex into a place where everyone watches everyone. Opening common area footage to residents as a live stream or as recordings is an access decision separate from the original purpose of installation. General access shouldn’t be opened without assessing authority, purpose, necessity and privacy impact.
The technical complement to access management is the audit trail. The recorder or VMS should log every login, playback and export by username, and the logs should be reviewed regularly. A log nobody looks at is as useless as a log nobody keeps. For permission model design, see our camera recording access rights and audit trail page.
Recording requests and export
The most common request in a complex is predictable: “My car was scratched in the car park; I want the footage.” This request is handled not arbitrarily but through a written procedure:
- Written request: The date, approximate time range, location and a short description of the incident are taken.
- Securing the recording: If the retention period is about to expire, the relevant time range is locked so it isn’t deleted until a decision is made, or copied to a secure location. If this step is skipped, loop recording overwrites it; the argument ends, and so does the evidence.
- Assessment: The purpose of the request and whether other people appear in the recording are assessed. In many cases, handing the recording over to the police or judicial authorities upon an official request is a more appropriate route than giving it to the resident; watching it together with the resident is also an option.
- Export: Only the relevant time range and cameras are exported. If the recorder has a signed export feature, it’s used; otherwise the file’s hash value is taken.
- Record: The request, decision, person exporting, recipient and handover date are entered in a log.
# Integrity hash of the exported file (Linux)
sha256sum carpark-b2_2026-11-03_2140-2210.mp4 > carpark-b2_2026-11-03.sha256
# Windows PowerShell equivalent
Get-FileHash .\carpark-b2_2026-11-03_2140-2210.mp4 -Algorithm SHA256
The hash value is written on the handover record; if the file is changed afterwards, the value won’t match. How to preserve the chain of custody in legal proceedings is explained in the camera recording incident investigation and chain of custody article, and setting the retention period in the camera recordings and KVKK retention period article.
Power, outdoor conditions and infrastructure
- Central recording: The recorder sits in a locked technical room only authorized people can enter. Only a viewing client is placed in the security booth; putting the recorder in the booth exposes the device itself to physical risk. A thief takes the recorder first.
- Links between blocks: In complexes with scattered blocks, fiber is preferred for links between blocks; where digging isn’t possible, point-to-point wireless bridges can be used. Copper’s 100 m limit and earth potential differences between blocks make long copper runs problematic; switch ports burned out after a surge are often at the end of these runs.
- Power continuity: The recorder, PoE switches and cameras at entry points are connected to UPSs. A power cut is one of the moments when entry points most need watching.
- Outdoor resistance: Cameras at reachable heights are chosen impact-resistant (IK10) and outdoor-rated; cables run in conduit and junction boxes are locked.
- Cybersecurity: Remote access to the recorder isn’t opened to the internet by direct port forwarding; default passwords are changed and firmware is kept up to date. A recorder exposed to the internet is a target waiting to be scanned.
Implementation checklist
- The owners’ assembly decision and the system’s purpose are in writing.
- Privacy notice signs are posted at entry points and in camera areas; the privacy notice text is accessible.
- Purpose, image level and field of view were documented for each camera; there’s no view of private areas, or it has been masked.
- Audio recording is off; if there are PTZs, privacy masks and movement limits are defined.
- Personal accounts and role-based permissions are defined; no shared password is used.
- The audit trail is on and the person responsible for reviewing it is named.
- The retention period has been set and automatic deletion on the recorder is configured accordingly.
- The recording request procedure, request form and handover log are ready.
- The recorder is in a locked room; the recorder, switches and critical cameras are on UPSs.
- Remote access is provided by a secure method; default passwords have been changed.
In a residential project, installation is half the job; the other half is the rules for access and requests. For details, see our residential and common area cameras page.
Frequently asked questions
Is a decision needed to install cameras in a complex’s common areas?
Decisions about common areas are made by the owners’ assembly. The decision and majority required for camera installation should be determined under the Turkish Condominium Law and the complex’s management plan, with legal advice if needed.
Should residents be able to access cameras from their phones?
It isn’t recommended for all residents to access all cameras and recordings; that would mean residents could watch each other. Opening common area footage to residents as a live stream or as recordings is an access decision separate from the original purpose of installation. General access shouldn’t be opened without assessing authority, purpose, necessity and privacy impact.
What should be done if a resident whose car was damaged asks for footage?
A written request is taken, the relevant time range is protected against deletion and the request is assessed. In most cases, footage is handed over to the police or judicial authorities upon an official request; every handover is entered in a log.
How do you fix a camera that sees into an apartment window?
First, the camera angle is changed. If the angle can’t be changed, a static privacy mask is applied, and it’s checked that the mask is applied not only to the live view but also to the recording.