Canada: privacy and security obligations
The practice is based in British Columbia, and the Canadian work is the longest-standing on the site. Which Canadian law applies depends on who you are and where the data is, so the first step is always the same: find which instruments reach you.
Where to start
Which Canadian privacy law applies explains the four instruments and their triggers, and Canadian privacy readiness is the engagement that follows from the answer.
| If you are | Start here |
|---|---|
| A private-sector organization in BC or doing business across provinces | Canadian privacy readiness; meaningful consent |
| Dealing with Quebec customers | Quebec Law 25 outside Quebec |
| A BC public body, or a supplier to one | FIPPA PIAs and ISAs; BC public sector vendors; information-sharing agreements |
| Asked for Canadian data residency | Canadian data residency for SaaS |
| A federally regulated financial institution, or its supplier | OSFI B-13 for suppliers; credit unions and insurers |
| Handling health information | clinics handling health data; HIPAA for Canadian SaaS |
| A defence supplier | CPCSC for defence suppliers |
Across the border
Canadian organizations selling into the United States meet a second set of rules, set out on the United States page. The transfer questions that sit between the two are on cross-border transfers and data localization.
How the work is bounded
The scope is agreed in writing before work starts, and the engagement is quoted in writing with it.
SecHB does not issue certifications, attestations or audit opinions: those come from accredited certification bodies, CPA firms and QSAs. The work here is what an organization does to be ready for them.
Nothing here is legal advice. Where a question turns on the law, the work is done alongside the client’s counsel, not instead of them.
Tell us which instruments you think apply
Say where your people, customers and systems are. The reply says what a readiness scope would cover.