
Alberta PIPA and mandatory breach notification
Alberta was the first Canadian jurisdiction to make private-sector breach notification mandatory, in 2010. If your organization has customers or employees in Alberta, you need to know how its commissioner-notification model works and how it differs from PIPEDA's.
Reviewed by the ITRS security team · Last updated
Scope of Alberta PIPA
Alberta's Personal Information Protection Act (PIPA) governs how private-sector organizations collect, use and disclose personal information in Alberta, including information about their own employees. Like BC's law, it sits alongside PIPEDA: federally regulated businesses and personal information that crosses provincial or national borders in commercial activity can bring PIPEDA into play, so many organizations with Alberta operations have obligations under both.
Health custodians are covered by a different statute, the Health Information Act, and Alberta public bodies by the Protection of Privacy Act. Each has its own breach rule. This article focuses on PIPA for private organizations.
Reasonable security arrangements
PIPA requires organizations to make reasonable security arrangements to protect personal information in their custody or control against risks such as unauthorized access, collection, use, disclosure, copying, modification, disposal or destruction. As with other Canadian laws, 'reasonable' scales with the sensitivity of the information. In practice: strong authentication, encryption on portable devices, patching, endpoint protection, access control, logging, backups, training and vendor oversight. These are also the controls that determine how bad a breach turns out to be.
Mandatory notification to the Commissioner
Section 34.1 of PIPA says an organization having personal information under its control must, without unreasonable delay, provide notice to the Commissioner of any incident involving the loss of or unauthorized access to or disclosure of personal information where a reasonable person would consider that there exists a real risk of significant harm to an individual as a result.
The Office of the Information and Privacy Commissioner of Alberta (OIPC Alberta) provides a PIPA breach notification form for this purpose, and publishes guidance to help organizations decide whether a breach meets the threshold, including a 2022 report summarizing ten years of breach-reporting decisions. The OIPC notes that publication of individual decisions on real risk of significant harm stopped in October 2024, but the earlier published decisions remain a useful reference.
The assessment draws on the same technical evidence as anywhere else: what information was involved, whether it was encrypted, whether logs show access or exfiltration, who obtained it and whether it was recovered.
Direct notification to individuals
Alberta's model differs from PIPEDA's in who decides on individual notice. Under section 37.1, once a reportable breach has been notified, the Commissioner may require the organization to notify individuals to whom there is a real risk of significant harm, in the form prescribed by regulation and within a time the Commissioner sets. The Commissioner can add terms and conditions, and must have an expedited process for cases where the risk is obvious and immediate.
Nothing stops an organization from notifying individuals on its own initiative, and most do: OIPC Alberta reports that since 2012-2013 at least 80% of organizations had already notified affected individuals by the time they reported to the Commissioner.
Section 19.1 of the PIPA Regulation sets out the required content: notice must be given directly to the individual and include a description of the circumstances, the date or period of the incident, a description of the personal information involved, the steps taken to reduce the risk of harm, and contact information for someone who can answer questions. Indirect notice is possible only if the Commissioner decides direct notice would be unreasonable. The OIPC recommends that organizations notifying voluntarily use the prescribed content, because it has required organizations to re-notify where earlier notices fell short.
Comparison with PIPEDA
Where a breach affects people in Alberta and elsewhere in Canada, organizations often have to report to both the OIPC Alberta and the OPC, and sometimes to other provincial regulators as well.
| Topic | Alberta PIPA | PIPEDA |
|---|---|---|
Threshold | Real risk of significant harm, judged by a reasonable person | Reasonable to believe there is a real risk of significant harm |
Report to regulator | Commissioner, without unreasonable delay (s.34.1) | Privacy Commissioner of Canada, as soon as feasible (s.10.1) |
Notice to individuals | Commissioner may require it (s.37.1); voluntary notice permitted | Organization must notify directly, as soon as feasible |
Notice content | PIPA Regulation s.19.1 | Breach of Security Safeguards Regulations s.3 |
Record of all breaches | No equivalent federal-style register duty identified in this review | Required for every breach, kept 24 months |
Checklist
- Confirm with counsel whether PIPA, PIPEDA or both apply to each of your activities in Alberta.
- Name who decides on breach reporting, and who files the OIPC Alberta form.
- Keep an internal breach log for every incident, with your reasoning on real risk of significant harm, even where PIPA does not mandate one.
- Draft a notice template that meets section 19.1 of the PIPA Regulation, so voluntary notices don't have to be redone.
- Make sure logs (email, cloud, endpoint) are retained long enough to show what was or wasn't accessed.
- Encrypt laptops and mobile devices, so a lost device is less likely to become a reportable breach.
- Review vendor contracts for prompt breach notice to you, since the obligation to report rests with the organization in control of the information.
Related reading.
- PracticePrivacy, Data Governance & AIPIPEDA and Quebec Law 25 readiness, data mapping, breach notification and AI governance.
- ServicePrivacy breach assessment and notification supportAfter a cyber incident, someone has to turn log files and mailbox exports into a defensible answer to three questions: whose information was involved, how much risk it…
- ArticleBC PIPA for private organizationsMost private-sector organizations operating in British Columbia answer to BC's Personal Information Protection Act rather than PIPEDA for their in-province activity.
- ArticleWho to tell after a cyber incident in CanadaAfter a cyber incident, the list of people who may need to hear from you is longer than most organizations expect: privacy regulators, police, the Cyber Centre, your…
Not sure what your obligations require of your systems?
Speak with our privacy practice. We are staffed 24/7. Active incident? Call (289) 582-9930, 24/7.
