Breach Notification: Applying the Real Risk of Significant Harm Test
Under PIPEDA, a breach must be reported to the Privacy Commissioner and notified to individuals when it creates a real risk of significant harm. The test turns on the sensitivity of the information and the probability of misuse. Every breach must be recorded for 24 months, and Alberta and Quebec apply their own thresholds.

Key takeaways
- PIPEDA s. 10.1 requires reports and notices where a breach creates a real risk of significant harm.
- Significant harm includes humiliation, reputational damage, financial loss and identity theft.
- Sensitivity and probability of misuse are the core statutory factors.
- Reports and notices are due as soon as feasible after the breach is determined.
- Every breach must be recorded and kept for 24 months.
- Quebec applies a risk of serious injury test and requires an incident register.
The real risk of significant harm test in brief
The real risk of significant harm test decides whether a privacy breach must be reported to the Office of the Privacy Commissioner of Canada (OPC) and notified to affected individuals under the Personal Information Protection and Electronic Documents Act (PIPEDA). Section 10.1(1) requires an organization to report to the Commissioner any breach of security safeguards involving personal information under its control "if it is reasonable in the circumstances to believe that the breach creates a real risk of significant harm to an individual". The same threshold triggers notification of individuals (s. 10.1(3)). Alberta uses a similar test, and Quebec uses a "risk of serious injury" test for confidentiality incidents.
Getting the analysis right matters. Under-reporting exposes the organization to regulatory findings, offences and class action allegations of concealment; over-reporting creates unnecessary alarm, cost and reputational damage. Because every breach must be recorded regardless of the outcome of the analysis, the reasoning behind each decision should be documented.

This insight explains the statutory elements, how to assess sensitivity and probability, notification content and timing, notices to other organizations, record-keeping, provincial differences and regulator follow-up. It is general information, not legal advice.
What is a breach of security safeguards?
PIPEDA defines a breach of security safeguards as the loss of, unauthorized access to or unauthorized disclosure of personal information resulting from a breach of an organization's security safeguards or from a failure to establish those safeguards. This includes cyberattacks, lost devices, misdirected emails, employee snooping, improper disposal of records and incidents at service providers that process information on the organization's behalf. The organization that has "control" of the information remains responsible even when the incident occurs at a vendor.
What counts as significant harm
Section 10.1(7) defines significant harm broadly to include bodily harm, humiliation, damage to reputation or relationships, loss of employment, business or professional opportunities, financial loss, identity theft, negative effects on the credit record, and damage to or loss of property. The list is inclusive, so other serious harms may qualify. In practice, the question is rarely whether the type of harm is significant, but whether there is a real risk that it will occur.
Assessing a real risk of significant harm: sensitivity and probability
Section 10.1(8) identifies the relevant factors: the sensitivity of the personal information involved, the probability that it has been, is being or will be misused, and any other prescribed factor.
Sensitivity
Some information is almost always sensitive: health information, financial account and payment card details, government identification numbers, passwords and authentication data, information about children, and intimate images. Other information becomes sensitive in context: a list of names may be harmless, but a list identifying people as clients of an addiction clinic is not. Combining data elements can also increase sensitivity.
Probability of misuse
Probability depends on the circumstances: whether the breach was malicious, such as a ransomware attack with exfiltration, or accidental, such as an email sent to the wrong internal recipient who promptly deleted it; whether the information was encrypted with keys not compromised; how long it was exposed; whether there is evidence of misuse; who had access; and whether the information was recovered. The OPC's guidance lists questions that organizations should ask.
| Scenario | Sensitivity | Probability of misuse | Likely outcome |
|---|---|---|---|
| Ransomware with data exfiltration of customer financial records | High | High | Report and notify |
| Encrypted laptop stolen; keys secure | Varies | Low | Likely not reportable; record the breach |
| Email with health information sent to wrong external recipient who confirms deletion | High | Low to moderate | Case-specific; document reasoning |
| Employee views customer files without authorization out of curiosity | Moderate to high | Moderate | Often reportable depending on information and motive |
Write down the harm analysis for every breach, including those you decide not to report: the information involved, the sensitivity, the facts bearing on probability, the conclusion and who made it. The OPC can request breach records, and a reasoned file is the best defence of a decision not to notify.
Reporting to the OPC
A report to the Commissioner must contain prescribed information and be made "as soon as feasible" after the organization determines that the breach occurred (s. 10.1(2)). The Breach of Security Safeguards Regulations specify the content, which includes a description of the circumstances and cause, the date or period, the personal information involved, the number of individuals affected, steps taken to reduce risk, notification steps and a contact person. Organizations can submit additional information later as investigations proceed; waiting for a complete picture is not a reason to delay the initial report.
Notifying individuals
Unless prohibited by law, organizations must notify affected individuals of a reportable breach as soon as feasible. The notice must contain enough information to allow individuals to understand the significance of the breach and to take steps to reduce risk, such as changing passwords or monitoring accounts. The regulations prescribe content, including a description of the breach, the information involved, steps taken, steps individuals can take, and contact information. Notification is normally direct, by email, letter or phone, with indirect notification, such as a public notice, permitted in limited circumstances, for example where direct notification would cause further harm or be prohibitively costly.
Notifying other organizations
Under s. 10.2, an organization that notifies individuals must also notify any other organization or government institution that may be able to reduce the risk of harm or mitigate it, such as banks, credit bureaus or law enforcement, subject to conditions. This is often overlooked, but it can materially reduce harm, for example by allowing banks to monitor affected accounts.
Breach records
Every breach of security safeguards must be recorded, whether or not it meets the reporting threshold (s. 10.3). The regulations require records to be kept for 24 months after the day the organization determines that the breach occurred, and the Commissioner can request them. Records should contain enough information to allow the OPC to verify compliance with reporting and notification obligations.
Alberta, Quebec and British Columbia
Provincial regimes differ. Alberta's Personal Information Protection Act requires organizations to notify the Alberta Commissioner without unreasonable delay of incidents where a reasonable person would consider that there exists a real risk of significant harm, and the Commissioner may require notification of individuals.
Quebec's private-sector law, as amended by Law 25, requires organizations to notify the Commission d'accès à l'information and affected persons of confidentiality incidents presenting a "risk of serious injury", considering sensitivity, anticipated consequences and probability of misuse, and to keep a register of all confidentiality incidents. British Columbia's private-sector law has historically not contained a general mandatory breach notification requirement, but notification may still be advisable. Organizations operating nationally must assess each regime separately; see our insight on confidentiality incidents in Quebec.
Sector rules and other notifications
Breaches may trigger other obligations: notices to health privacy commissioners under provincial health information laws, reports to OSFI or securities regulators for regulated entities, notifications under contracts with customers and partners, and disclosures by reporting issuers where an incident is material. Cross-border incidents can trigger foreign regimes with fixed deadlines. Our privacy and data protection page addresses related obligations, including health privacy and ransomware decisions.
Regulator follow-up and enforcement
After a report, the OPC may ask questions about the breach and the organization's safeguards, and may open an investigation. Findings can be published. Knowingly failing to report or notify, or failing to keep records, is an offence under PIPEDA, punishable by fines. Separately, affected individuals may bring claims, and class actions often follow significant breaches, alleging negligence, breach of contract or privacy torts; see our insight on data breach class actions.
Common errors in applying the test
- Waiting for certainty. The test asks whether it is reasonable to believe there is a real risk, not whether harm has occurred. Waiting for proof of misuse delays notices beyond "as soon as feasible".
- Relying on threat actor assurances. Promises by ransomware groups to delete data do not reliably reduce the probability of misuse.
- Ignoring context. Seemingly innocuous data, such as names and addresses, can be sensitive when it reveals a relationship with a clinic, a lender or a support service.
- Treating encryption as conclusive. Encryption lowers risk only if keys were not compromised and the method was robust.
- Overlooking vendors. Breaches at service providers still require the controlling organization to assess and report.
Timing in practice
"As soon as feasible" is not defined by a fixed number of hours, but regulators expect organizations to move quickly once they determine that a breach occurred. In practice, an initial report can be filed with the information available and supplemented as forensic work continues. Delays to complete a full investigation, to manage public relations or to wait for insurer input are difficult to justify. Organizations subject to foreign laws with fixed deadlines, or to sector regulators with shorter timelines, should align their internal process with the strictest applicable deadline.
Who decides, and how
Decisions about whether a breach creates a real risk of significant harm should not be left to the IT team alone. A small incident response committee, typically including privacy, legal, security and communications leads, should make and document the decision, with escalation to senior management for significant incidents. Pre-approved templates for OPC reports and individual notices, and a decision matrix with examples, speed up the process and improve consistency. After each incident, the committee should review whether the decision and timing were appropriate and update the playbook. Consistency across incidents also helps if the OPC later reviews the organization's breach records, because regulators look for a principled approach rather than case-by-case improvisation.
Building the real risk of significant harm analysis into incident response
- Contain the breach and preserve evidence, including logs and affected systems.
- Identify the personal information and individuals affected as quickly as possible.
- Assess the risk of harm under the statutory test, documenting sensitivity and probability.
- Report to the OPC and other regulators as soon as feasible where required.
- Notify individuals and organizations that can mitigate harm.
- Record the breach and the analysis, and keep records for at least 24 months.
- Review safeguards and implement lessons learned, including changes to vendor controls, training and technical measures.
- Prepare for follow-up questions from regulators, customers, insurers and the media, with consistent messaging.
How TRW & Co helps
We advise organizations on breach response and the real risk of significant harm test under PIPEDA, Alberta PIPA and Quebec law. Our work includes rapid risk assessments, preparation of reports to the OPC and provincial regulators, notification letters, coordination with forensic investigators under privilege, vendor incident management and responses to regulator follow-up and class actions. See our cybersecurity and incident response page or contact us.
Frequently asked questions
When must a privacy breach be reported in Canada?
Under PIPEDA, when it is reasonable in the circumstances to believe the breach creates a real risk of significant harm to an individual. The report goes to the Privacy Commissioner as soon as feasible, and affected individuals must also be notified. Alberta and Quebec have their own requirements.
How do I assess the real risk of significant harm?
Consider the sensitivity of the personal information and the probability that it has been, is being or will be misused, based on facts such as malicious intent, encryption, exposure time, evidence of misuse and recovery of the information. Document the analysis.
Do I need to record breaches that are not reportable?
Yes. PIPEDA requires organizations to keep a record of every breach of security safeguards, and the regulations require records to be kept for 24 months after the organization determines the breach occurred. The Commissioner can request them.
Who else must be notified?
Organizations and government institutions that may be able to reduce or mitigate the risk of harm, such as banks or credit bureaus, under s. 10.2 of PIPEDA, as well as other regulators and contractual counterparties depending on the sector.
Is Quebec's test the same?
No. Quebec requires notification of the Commission d'accès à l'information and affected persons for confidentiality incidents presenting a risk of serious injury, and requires a register of all confidentiality incidents.
Sources
General information only, not legal advice. References to statutes, courts and authorities describe published law and practice at the date shown.


