Video surveillance can support legitimate business objectives, but recorded images may also be personal information. Privacy planning should begin before camera placement and system configuration—not after a complaint or footage request.
Typical scopes and budget levels
The appropriate approach depends on the jurisdiction, workplace context, camera purpose and sensitivity of the area. The consistent theme across regulator guidance is to define a legitimate need, minimize unnecessary collection and protect the recordings.
| Scope | What it usually includes | Budget context |
|---|---|---|
| Purpose and necessity | Document the business problem, alternatives considered and why recording is proportionate. | Written assessment before procurement |
| Transparent operation | Use appropriate notices, policies and contact information. | Plan signage and communications |
| Controlled records | Limit retention, users, exports and disclosure. | Build governance into configuration |
What changes the price?
Purpose limitation
A camera installed for one reason should not quietly become a general employee-performance tool.
Field of view
Capture only the area needed for the stated purpose and avoid adjacent private spaces.
Retention
Keep recordings only as long as reasonably necessary, subject to applicable obligations.
Access and disclosure
Use named accounts, least privilege, logs and a defined process for requests.
System security
Protect cameras, recorders, cloud accounts, exports and administrator credentials.
Line items to include in the budget
- Assessment: Privacy impact or necessity assessment appropriate to the organization and jurisdiction.
- Notices and policy: Visible signage, internal policy and a contact route.
- Technical controls: Permissions, retention, encryption, secure remote access and audit logs.
- Operational process: Footage requests, incident holds, exports, disclosure and secure deletion.
- Training: Authorized users should understand lawful purpose and handling rules.
A practical planning process
- Define the purpose. Write a specific objective and identify who is accountable.
- Check applicable rules. Review federal, provincial/state, employment, tenancy and sector requirements.
- Minimize collection. Adjust broad zones and settings to avoid unnecessary capture or audio.
- Configure governance. Set retention, roles, logs, secure export and incident procedures.
- Review periodically. Confirm the purpose remains valid and users, views and retention are still appropriate.
Questions to ask before approving a quote
- What law or policy governs the organization and workplace?
- Is audio recording disabled unless specifically lawful and necessary?
- How can an individual make an access or privacy inquiry?
- Who can export footage, and is that action logged?
- When and how are recordings securely deleted?
Common budgeting mistakes
- Adding privacy after installation: Camera purpose and field of view must influence the design.
- Using shared logins: Shared accounts weaken accountability and make access review difficult.
- Keeping footage indefinitely: Unlimited retention increases risk and may conflict with privacy principles.
- Assuming signage alone is consent: A notice does not replace necessity, proportionality or other legal requirements.
Bottom line
Treat privacy requirements as system requirements. A well-governed camera system has a defined purpose, limited views, controlled access, a justified retention period and a documented response process.
Official references and further reading
- Office of the Privacy Commissioner of Canada — overt video surveillance
- UK Information Commissioner's Office — CCTV and video surveillance
- Australian OAIC — security cameras
- U.S. Federal Trade Commission — privacy and security
External rules and guidance may change. Confirm the current requirements that apply to your site, industry and jurisdiction.