
Real risk of significant harm: how the assessment works
Whether a Canadian privacy breach must be reported usually turns on one judgment: does it create a real risk of significant harm? The legal test is short. Getting it right depends on technical evidence most organizations don't gather until it's too late.
Reviewed by the ITRS security team · Last updated
What is a real risk of significant harm under PIPEDA?
Real risk of significant harm (RROSH) is PIPEDA's test for whether a privacy breach must be reported. Section 10.1 weighs the sensitivity of the personal information and the probability it has been, is being or will be misused. Significant harm includes humiliation, damage to reputation or relationships, financial loss, identity theft, damage to credit records and lost business opportunities.
The two factors: sensitivity and probability
Under section 10.1 of the Personal Information Protection and Electronic Documents Act (PIPEDA), an organization must report a breach of security safeguards to the Privacy Commissioner of Canada and notify affected individuals if it is reasonable in the circumstances to believe the breach creates a real risk of significant harm (RROSH). The Act names the relevant factors: the sensitivity of the personal information involved, and the probability that it has been, is being or will be misused.
Think of it as a two-way grid. Highly sensitive information with a meaningful chance of misuse points strongly toward reporting. Low-sensitivity information that almost certainly went nowhere points away. The difficult cases sit in between, and that is where the quality of the evidence matters most. The Office of the Privacy Commissioner (OPC) also offers an online tool that walks through sensitivity and probability questions.
What 'significant harm' includes
PIPEDA defines significant harm broadly. It includes:
- bodily harm;
- humiliation;
- damage to reputation or relationships;
- loss of employment, business or professional opportunities;
- financial loss and identity theft;
- negative effects on the credit record; and
- damage to or loss of property.
What 'significant harm' means in practice
The breadth matters. A breach does not need to involve credit card numbers to be significant. Information about health, mental health, sexual life, criminal matters, finances, or a person's location can cause humiliation or relationship damage. Context matters as well: a list of names and email addresses is ordinarily low sensitivity, but the same list labelled 'clients of a family law practice' or 'patients of an addiction clinic' is not.
Technical evidence that changes the answer
Probability of misuse is where technical facts carry the most weight. These are the questions we work through with counsel:
| Question | Evidence that answers it | Typical effect |
|---|---|---|
Was the data encrypted, and was the key safe? | Device encryption status from management tools; key escrow records | Strong encryption with an uncompromised key can lower probability considerably |
Was it actually accessed, or only exposed? | Microsoft 365 audit log (MailItemsAccessed, FileAccessed), server and application logs | Logs showing no access can lower probability; missing logs force worst-case assumptions |
Was it copied out? | Firewall and proxy logs, endpoint telemetry, cloud download events, ransomware leak-site monitoring | Evidence of exfiltration raises probability sharply |
Who had it? | Threat-actor indicators, recipient identity in misdirected email | A criminal group versus a trusted professional who confirmed deletion are very different risks |
How long was it exposed? | Timeline from first malicious sign-in to containment | Longer windows increase the chance of misuse |
Was it recovered? | Device recovery, written confirmation of deletion, takedown | Recovery can lower probability, though not erase it |
Examples by scenario
Lost laptop, encrypted
BitLocker enforced and reported by device management, recovery key held centrally and not stored with the device. Probability of misuse is usually assessed as low. Without encryption evidence, the same loss is a very different assessment.
Compromised mailbox
An attacker held access for two weeks to set up invoice fraud. Audit logs show they searched for and read messages. The mailbox contains client identification and banking details. Both sensitivity and probability are high; reporting is likely.
Misdirected email
A payroll summary went to the wrong internal manager, who confirmed deletion. Sensitivity is moderate to high, but probability of misuse is low. Often not reportable, but it must still be recorded.
Ransomware with leak threat
Files were encrypted and the attacker claims to have stolen data. Treat the claim seriously: look for exfiltration evidence and monitor leak sites. Where data from sensitive folders was taken, probability is high.
Documenting the decision
Whatever you decide, write it down. PIPEDA requires a record of every breach, kept for 24 months, containing enough information for the Commissioner to verify compliance, including how you assessed RROSH. A good assessment memo states the facts relied on, separates confirmed facts from assumptions, rates sensitivity and probability with reasons, records who made the decision and when, and notes what new facts would change the answer. If the investigation later finds something new, update the assessment and, where needed, report or notify at that point.
Where provinces differ
Other Canadian regimes use related but different tests. Alberta's Personal Information Protection Act requires notice to the Commissioner without unreasonable delay where a reasonable person would consider there is a real risk of significant harm. Quebec's private-sector law uses a 'risk of serious injury' test and directs organizations to consider the sensitivity of the information, the anticipated consequences of its use and the likelihood it will be used for injurious purposes, in consultation with the person in charge of the protection of personal information. Ontario's PHIPA works differently again: health information custodians must notify affected individuals of theft, loss or unauthorized use or disclosure, and must notify the Information and Privacy Commissioner of Ontario in specific listed situations, such as stolen information, snooping by staff, or a significant breach.
If a breach involves people in several provinces, more than one test can apply at the same time.
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…
- ArticlePIPEDA breach reporting and record-keepingPIPEDA has three linked breach duties: report serious breaches to the Privacy Commissioner, notify the people affected, and keep a record of every breach, even the small…
- ArticleQuebec Law 25: confidentiality incidents and the incident registerQuebec's private-sector privacy law has its own incident regime: its own definition, its own 'risk of serious injury' test, specific notice contents for the Commission…
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.
