Quick answer: Do not apply the same PIPEDA explanation to every Canadian workplace or public body. Have the customer identify the applicable privacy regime, document why surveillance is needed and turn that decision into clear coverage, access, notice and retention requirements.
On this page
Does PIPEDA apply to this customer?
PIPEDA governs private-sector commercial personal-information handling within its scope and employee information of federally regulated businesses. Alberta, British Columbia and Quebec have substantially similar private-sector legislation; cross-border commercial information flows and federally regulated organizations require particular attention. Public bodies and sector-specific information may follow different laws.
Use the OPC’s scope guidance to identify the right question, then have the customer’s privacy lead determine which regime and other obligations apply. The installer should not decide an employer’s jurisdiction from its street address alone.
| Decision | Customer record | Installer verification |
|---|---|---|
| Purpose and need | Specific problem and why the selected coverage is needed. | Views and operating schedule match the approved plan. |
| Responsible organization | Policy owner, applicable privacy regime and request contact. | The handover names the right contact and responsibilities. |
| Collection boundary | Areas to cover/exclude and separately approved sound or identification functions. | Actual views, masks and enabled functions are checked. |
| Access and sharing | Authorized users and approved local/remote routes. | Permissions and agreed access paths are demonstrated. |
| Retention and disposal | Approved period, preservation exceptions and disposal process. | Recording settings and later mature-retention check are scheduled. |
| Notice and review | Approved notice, policy information and review triggers. | Notice locations, contact path and final configuration record agree. |
How do you make the surveillance purpose practical?
Replace “for security” with a problem the camera plan can address: an entrance that needs incident review, a stockroom access point or a loading-area dispute. Compare the proposed views and operating schedule with that purpose. A camera facing every desk may collect much more than a door-focused requirement needs.
Discuss alternatives and unnecessary collection with the customer. Mark areas to exclude and confirm whether supported privacy masking remains effective in the relevant views and recordings. A masking checkbox is not enough if a different stream or later PTZ position exposes the excluded area.
What needs a separate decision?
Audio, identification analytics, remote sharing and a change in use deserve their own review. Do not assume ordinary video approval covers conversations or biometric identification. Use the audio checklist and the facial-recognition guide when those functions are requested.
Ask where recordings and account information will be accessible, including a service provider or remote client. Record the actual data flow and supported configuration; a product name containing “cloud” does not answer the hosting, recording or disclosure question.
How should access and requests be handled?
Agree who may view, export and administer the system. Demonstrate the supported roles and keep temporary installer access separately authorized. The customer needs a procedure for an access request or disclosure, including how other people’s information will be handled; do not promise an editing/redaction capability without testing the actual tool.
Keep credentials out of the general handover document. The handover checklist provides a place to record access responsibilities and outstanding work without exposing secrets.
How do you link retention and notices to the real configuration?
Document the approved recording period and its basis. Configure the supported system accordingly, distinguish calculated capacity from observed oldest footage and arrange the later verification. Include the authorized process for preserving an incident rather than simply increasing every camera’s default loop.
Use the retention-policy guide for the technical calculation. Have the customer approve notice wording and the contact process, then use the signage checklist to verify actual placement.
What should trigger a review after handover?
Include a new camera view, workplace change, different operator, new collection purpose, enabled microphone, identification function, remote service or changed retention. Keep a dated configuration and decision record so the next service visit can identify what changed.
FAQ
Is every Canadian employee camera system governed only by PIPEDA?
No. The employer, activity, sector and jurisdiction matter. Resolve the applicable regime before using a standard explanation.
Does posting a sign settle every privacy requirement?
No. The plan still needs an approved purpose, appropriate collection, access and retention decisions and a workable customer policy.
Can a camera be called privacy compliant from a feature list?
A feature list describes available controls, not the whole deployment. Verify the project’s required behavior on the exact supported system.
What should you send Anabon before equipment selection?
Provide the customer-approved coverage, excluded areas, required access paths and retention basis. Separate available equipment controls from the customer’s legal and policy decisions. For model-specific questions, contact Anabon technical support. Use Anabon Downloads for available product resources. Compare IP camera options after the requirements and evidence needed for acceptance are clear.
References
References checked October 21, 2026. Confirm the current requirements for the actual project before a commitment.
