← Guides·Which law applies to you →
Your SituationWe had a privacy incident →
PIPEDA Breach Reporting Requirements for Canadian Organizations
By Yong DuPublished Reviewed
When PIPEDA requires an OPC report and notice to individuals, and why every breach needs a record kept for 24 months.
On this page
What are the breach notification requirements under PIPEDA?
PIPEDA requires three things when a breach poses a real risk of significant harm: report to the Office of the Privacy Commissioner of Canada (OPC) as soon as feasible, notify all affected individuals directly, and maintain an internal breach record for 24 months. ClearBreach automates all three, generating your OPC breach report, individual notification letter, and internal incident record in a single 15-minute assessment.
The duties are in PIPEDA itself, ss.10.1 to 10.3, in force since November 1, 2018. The Breach of Security Safeguards Regulations set what the report, the notice and the record must contain. A breach of security safeguards is the loss of, unauthorized access to, or disclosure of personal information resulting from a breach of your security safeguards, or from a failure to have them (s.2).
When a breach creates a real risk of significant harm, you must:
- report it to the Office of the Privacy Commissioner of Canada (OPC);
- notify the affected individuals directly;
- notify any other organization or government institution that may be able to reduce the risk of harm, such as a bank or the police (s.10.2).
Separately, you must keep a record of every breach, whether or not it meets the test, for 24 months (s.10.3).
Generate your OPC breach report, individual notification letter, and internal incident record automatically. ClearBreach tells you whether your breach must be reported under PIPEDA, Alberta PIPA and BC PIPA, and gives you the documents that calls for, entirely in your browser.
Who is subject to PIPEDA breach reporting?
PIPEDA applies to every private-sector organization engaged in commercial activity in Canada, regardless of size. Alberta and BC have substantially similar provincial PIPA legislation, but any interprovincial or cross-border commercial activity triggers PIPEDA regardless of province. Federally regulated industries are always subject to PIPEDA.
PIPEDA applies to:
- Businesses of any size operating interprovincially or internationally
- Organizations in federally regulated sectors (banking, telecommunications, transportation, broadcasting) regardless of province
- Organizations in provinces without substantially similar provincial legislation
Provincial exceptions: Alberta (PIPA) and British Columbia (PIPA) have provincial legislation deemed substantially similar to PIPEDA. Organizations that only collect, use, and disclose personal information within Alberta or BC in the course of purely intraprovincial commercial activity are governed by the provincial legislation instead of PIPEDA. However, if any commercial activity crosses provincial or international borders, PIPEDA applies.
In practice, most Canadian small businesses are subject to PIPEDA for cross-border transactions, online business, and any activity that moves personal information outside the province. If you are uncertain which legislation applies to your organization, err on the side of compliance with both PIPEDA and your applicable provincial PIPA.
Under PIPEDA, a breach must be reported to the OPC, and the people affected told directly, when it creates a real risk of significant harm. Both go out as soon as feasible after you make that determination, and you need not wait for a forensic investigation. Every breach, reportable or not, goes in a record you keep for 24 months.
Which provinces are covered by PIPEDA only?
Saskatchewan, Manitoba, New Brunswick, Nova Scotia, Prince Edward Island, and Newfoundland and Labrador, like Ontario and the territories, have no general private-sector privacy law of their own. Organizations there are subject to PIPEDA, with the OPC as the single regulator. Quebec is different: its own private-sector Act applies there, and is not covered here. Some provinces also have health-information laws that apply to health custodians instead. Report to the OPC at priv.gc.ca. No concurrent provincial regulator filing is required.
Alberta and BC have their own PIPA laws, recognized as substantially similar to PIPEDA. These provinces do not. For organizations in Saskatchewan, Manitoba, New Brunswick, Nova Scotia, Prince Edward Island or Newfoundland and Labrador, that means:
- One regulator: the Office of the Privacy Commissioner of Canada (OPC) at priv.gc.ca
- One report: the OPC PIPEDA breach report, filed as soon as feasible when RROSH is present
- No provincial OIPC filing: unlike organizations in Alberta or BC, there is no concurrent provincial filing requirement
- Same obligations as Ontario organizations: the single-regulator advantage applies equally
A Saskatchewan consulting firm, a Manitoba retailer, a New Brunswick accounting practice and a Nova Scotia tech company have identical breach duties under PIPEDA. This guide covers all of them; there is no provincial layer on top.
What is the RROSH threshold that triggers PIPEDA reporting?
Not every breach must be reported. PIPEDA's threshold is a real risk of significant harm (RROSH). A breach must be reported only when there is a genuine, not speculative, possibility of significant harm, given what was exposed and how.
What counts as significant harm under PIPEDA?
PIPEDA itself defines significant harm, in s.10.1(7), to include:
- Bodily harm
- Humiliation
- Damage to reputation or relationships
- Loss of employment, business, or professional opportunities
- Financial loss
- Identity theft
- Negative effects on credit records
- Damage to or loss of property
The harm need not have happened yet; a real risk of it is enough. "Real" means more than speculative: a genuine possibility, given how sensitive the information is.
What factors decide whether the risk is real?
PIPEDA names two factors (s.10.1(8)): the sensitivity of the personal information, and the probability that it has been, is being or will be misused. The OPC's guidance weighs the questions below under them.
1. Sensitivity of the personal information Financial account numbers, social insurance numbers, health information, and passwords are highly sensitive. Name and address alone are lower sensitivity. The more sensitive the information, the higher the probability RROSH is present.
2. Probability that the personal information has been, is being, or will be misused Was access confirmed? Was it an intentional attack or an accidental disclosure? Ransomware attacks and deliberate exfiltration carry high probability of misuse. An internal accidental send to the wrong recipient with prompt recall carries lower probability.
3. Number of individuals affected A breach of sensitive data about thousands of people almost certainly meets the test. One person's limited information may not. Scale does not decide it alone: one person's health record or SIN can still meet the test.
4. Whether the information has been recovered Data recovered with strong evidence it was not accessed or copied lowers the chance of harm. Data not recovered, especially after ransomware or confirmed copying, weighs heavily towards the test being met.
For a fuller breakdown with worked examples, see What Is RROSH?
What must I report to the OPC and when?
Report to the OPC as soon as feasible after you determine the risk is real. The Act sets no number of days. File on what you know and send updates as your investigation continues. Do not hold the report back until a forensic investigation is complete.
What the OPC breach report must contain
The Regulations (s.2) require the report to include:
- a description of the circumstances of the breach and, if known, its cause;
- the date or period when it happened, or an approximation;
- a description of the personal information involved;
- an estimate of the number of individuals at real risk of significant harm;
- the steps taken to reduce that risk or mitigate the harm;
- the steps taken or intended to notify affected individuals;
- a contact person who can answer the OPC's questions.
You submit the report through the OPC's online breach portal at priv.gc.ca.
When must I notify affected individuals under PIPEDA?
When RROSH is present, notify every affected individual directly, as soon as feasible after you determine the breach occurred (s.10.1(3) and (6)).
Requirements for individual notification under PIPEDA
The notice must be given directly to each affected individual, and include (Regulations s.3):
- a description of the circumstances of the breach;
- the date or period when it happened, or an approximation;
- a description of the personal information involved;
- the steps your organization has taken to reduce the risk of harm;
- the steps the individual can take to reduce their own risk;
- a toll-free number or email address for further information;
- your internal complaint process and the individual's right to complain to the OPC.
When is indirect notice permitted?
Only in three cases (Regulations s.5): direct notice would likely cause further harm to the individual, it would cause undue hardship for the organization, or you have no contact information for the individual. Indirect notice means a public communication or similar measure likely to reach them.
What are the PIPEDA record-keeping requirements?
PIPEDA requires a record of every breach of security safeguards, whether or not it met the test, kept for 24 months after the day you determine the breach occurred (s.10.3; Regulations s.6). It must hold enough for the OPC to check that you assessed, reported and notified correctly, and the OPC may ask to see it. Knowingly failing to keep it is an offence.
Your internal breach record should document:
- Date and description of the breach
- Nature of the personal information involved
- Cause of the breach (if known)
- Number of individuals affected
- RROSH determination and the reasoning behind it
- Steps taken to contain the breach and prevent recurrence
- Whether the breach was reported to the OPC and individuals notified
What happens if I fail to report a breach under PIPEDA?
Knowingly failing to report, notify or keep records is an offence under PIPEDA s.28, with fines of up to $100,000. The OPC may also investigate and publish its findings.
Beyond the regulator, an organization that delays or fails to notify can be sued if people are harmed as a result.
Specific enforcement mechanisms include:
- Fines of up to $100,000 for organizations that knowingly fail to comply
- OPC investigation: the OPC may open a formal investigation into your organization's privacy practices broadly, not just the breach
- Published findings: the OPC regularly publishes investigation findings. A published finding naming your organization is significant reputational risk
- Federal Court: after an OPC investigation, the complainant or the OPC can apply to the Federal Court, which can order compliance and award damages
What do I do when PIPEDA and provincial PIPA both apply?
When both apply to the activity involved, one notice to individuals can meet both. File the mandatory OPC report under PIPEDA. Also report to the OIPC Alberta, which Alberta PIPA requires, or consider a voluntary report to the OIPC BC. ClearBreach shows which apply and gives you a separate report for each regulator.
| PIPEDA | Alberta PIPA | BC PIPA | |
|---|---|---|---|
| Governing body | OPC Canada (priv.gc.ca) | OIPC Alberta (oipc.ab.ca) | OIPC BC (oipc.bc.ca) |
| Regulator reporting | Mandatory when real risk of significant harm | Mandatory when real risk of significant harm | Voluntary; no breach provision in the Act |
| Notifying individuals | Mandatory when real risk of significant harm | When the commissioner requires it; may notify on your own | Not required by the Act; expected where there is a risk of harm |
| Timing | As soon as feasible | Without unreasonable delay | As soon as possible (Commissioner's guidance) |
| Breach records | Every breach, kept 24 months | Not required; good practice | Not required; good practice |
Scenario-specific PIPEDA guidance
The RROSH framework applies regardless of how the breach occurred. For detailed guidance on specific incident types:
- Ransomware Attack: What Canadian Organizations Must Do, confirmed access, malicious intent, dwell time, and reporting obligations across all three frameworks
- Phishing and Business Email Compromise: PIPEDA, Alberta PIPA, and BC PIPA, compromised email accounts, unresolvable access probability, audit log review, and reporting obligations when inbox data spans multiple provinces
- Lost or Stolen Device: What Canadian Organizations Must Do, encryption uncertainty and multi-jurisdiction reporting when the device holds data about individuals in multiple provinces
- Accidental Email Disclosure: What Canadian Organizations Must Do, when most wrong-recipient emails fall below RROSH, what pushes them over the threshold, and the internal documentation obligation that applies regardless of verdict
- Vendor or Third-Party Breach: What Canadian Organizations Must Do, why your PIPEDA accountability does not transfer when data is breached at an IT provider or SaaS platform, how to assess RROSH when you depend on vendor disclosure, and why the vendor's regulatory notification does not satisfy yours
- Unauthorized Employee Access: What Canadian Organizations Must Do, when a current or former employee accesses personal information beyond their authorization, why the HR investigation does not pause your reporting clock, and how to assess RROSH when you have no audit logs
- Cloud Storage Misconfiguration: What Canadian Organizations Must Do, when an S3 bucket or cloud container is accidentally left public, how to assess RROSH without access logs, and why remediating the misconfiguration does not end your reporting obligations
- Physical Records Breach: What Canadian Organizations Must Do, when paper records are lost, stolen, or improperly destroyed, why the same RROSH standard applies to physical and digital records, and how to assess scope when actual access cannot be determined
- Website or Database Compromise: What Canadian Organizations Must Do, SQL injection, web shells, database dumps, and card-skimming attacks; how to determine dwell period when logs are incomplete; and why forensics completion is not the notification trigger
For province-specific guidance:
- Alberta PIPA Breach Notification Requirements, mandatory OIPC Alberta reporting, the April 2024 simultaneous notification process, and dual PIPEDA and Alberta PIPA obligations
- BC PIPA Privacy Breach Reporting Requirements, voluntary OIPC BC reporting, when it applies alongside PIPEDA, and what the OIPC BC expects to see in a voluntary report
For sector-specific guidance on how PIPEDA applies to your industry:
- Accounting Firms, SINs, tax returns, and financial records; why accounting firms are a primary ransomware target; CPA professional overlay
- Dental and Medical Practices, patient health records, Alberta HIA interaction, EHR vendor accountability
- Law Firms, client file sensitivity, solicitor-client privilege in access requests, BEC wire fraud risk in real estate matters
- Mortgage Brokers, SIN plus financial records plus government ID; FINTRAC identity verification obligations; RECA and BCFSA overlay
- Real Estate Agents, FINTRAC identity verification, transaction file sensitivity, BEC deposit fraud risk
- Financial Advisors, KYC data, account records, CIRO and securities regulatory overlay
- HR and Recruitment Firms, background check consent, SIN collection timing, processor vs. accountable party for client employer data
- Insurance Brokers, health history on applications, claims file sensitivity, AIC and Insurance Council of BC overlay
- Pharmacies, prescription records imply diagnoses, Alberta HIA custodian obligations, unauthorized employee access risk
- Private Schools, minors require heightened protection, IEPs and health records, Vulnerable Sector Checks for staff
Using ClearBreach for your PIPEDA assessment
Run your PIPEDA breach assessment and generate all required documents automatically. ClearBreach guides your organization through a structured assessment covering every RROSH factor under PIPEDA, Alberta PIPA, and BC PIPA simultaneously. At the end of the assessment, you receive:
- An Assessment Verdict Card, your formal RROSH determination and the obligations it triggers
- An Internal Incident Record, the 24-month compliance record, complete
- An Individual Notification Letter, ready to send to affected individuals
- An OPC Breach Report draft, pre-populated with your assessment data, ready for review and submission
Your answers about the breach are processed in your browser and never sent to us.
Proactive compliance under PIPEDA
Breach notification is one of ten PIPEDA compliance obligations. Once a breach is resolved, a compliance assessment identifies the safeguard, governance, or consent gaps that contributed to the incident, and the documentation the OPC expects to find if a complaint follows. ClearBreach's compliance assessment shows where you stand on all ten PIPEDA principles, the gaps and the next step for each, with the documents to close them.
Privacy case of the month
Once a month, a five-minute read: a real case a Canadian privacy commissioner investigated, what went wrong, and what to check in your own organization so it doesn't happen to you. Written for organizations under federal, Alberta and BC privacy law. Not written for Quebec.
We send one email to confirm. Nothing else arrives until you confirm, and an unconfirmed address is deleted after 7 days. Sent by ClearBreach Technologies Inc. Mailing address and contact details · Privacy policy
Related guides
- How Canadian Regulators Decide Whether a Breach Must Be Reported. What real reporting decisions turned on
- What is a Real Risk of Significant Harm. The test the whole duty turns on
- Data Breach Response Checklist. The hours before the report is written
- PIPEDA Compliance Requirements. The duties that apply when nothing has happened
- Which Canadian Privacy Law Applies to Your Business. Whether PIPEDA is the only Act that reaches you
Frequently asked questions
What does RROSH mean under PIPEDA?
RROSH stands for Real Risk of Significant Harm. Under PIPEDA, a breach must be reported to the OPC and affected individuals only if it poses a real risk of significant harm to an individual. Significant harm includes bodily harm, humiliation, damage to reputation or relationships, financial loss, identity theft, negative effects on credit records, and property damage. The risk must be more than speculative, it must be a genuine possibility given the circumstances of the breach.
Do I have to report a data breach to the OPC?
Yes, if the breach poses a real risk of significant harm (RROSH) to affected individuals. Reporting is mandatory under PIPEDA s.10.1 and must be made as soon as feasible after you determine the breach has occurred. Knowingly failing to report can bring a fine of up to $100,000.
How long do I have to report a data breach under PIPEDA?
PIPEDA requires reporting 'as soon as feasible' after you determine the breach poses a real risk of significant harm. The Act sets no number of days, so do not hold the report back. You do not need to complete a full forensic investigation before reporting. File on available information and provide supplements as your investigation continues.
What happens if I don't report a data breach in Canada?
Failure to report a reportable PIPEDA breach is an offence. Knowingly failing to report to the OPC, notify affected individuals or keep breach records can bring a fine of up to $100,000 (s.28). The OPC may also investigate and publish its findings, and after an investigation the matter can go to the Federal Court. Reputational damage is significant if the breach is discovered later.
Does PIPEDA apply to small businesses in Canada?
Yes. PIPEDA applies to all private-sector organizations that collect, use, or disclose personal information in the course of commercial activity, regardless of size. There is no small-business exemption. Alberta and BC have their own substantially similar PIPA legislation, but organizations engaged in interprovincial or international commercial activity are subject to PIPEDA regardless of province.
Do I have to notify affected individuals after a data breach?
Yes. Under PIPEDA, if RROSH is present you must notify affected individuals directly, not just through a public notice unless direct notification is not reasonably possible. The notice must describe the breach and when it happened, the personal information involved, the steps you have taken, the steps the individual can take, a toll-free number or email address for information, and how to complain to you and to the OPC.
What documents do I need to produce after a privacy breach in Canada?
Under PIPEDA you need three things: (1) an internal breach record for every breach regardless of whether RROSH is present, retained for 24 months; (2) an OPC breach report filed as soon as feasible if RROSH is present; (3) individual notification letters sent directly to each affected individual if RROSH is present. ClearBreach generates all three automatically after your assessment.
This guide is educational and does not constitute legal advice. It is grounded in the text of PIPEDA, Alberta PIPA, and BC PIPA and published guidance from the OPC, OIPC Alberta, and OIPC BC. If your situation involves regulatory investigation, litigation risk, or circumstances not addressed here, engage a qualified privacy lawyer.
Find out what this incident requires of you
See whether you must report, to whom and by when, under each privacy law that applies to you.
How ClearBreach handles a breach →