managed cyber hub

PIPEDA Breach Reporting Requirements: What Canadian Businesses Must Do

PIPEDA breach reporting requirements

PIPEDA Breach Reporting Requirements: What Canadian Businesses Must Do

Under PIPEDA breach reporting requirements, a Canadian business must report a breach of security safeguards to the Office of the Privacy Commissioner of Canada (OPC) and notify affected individuals as soon as feasible when it is reasonable to believe the breach creates a real risk of significant harm. You must also keep a record of every breach for 24 months.

This is the essence of the rule. The difficulty comes in implementing it in the middle of the night when there are dozens of notifications on your phone, when your IT department is handling an incident and when no one knows if any customer information has been affected.

This document is geared towards business owners and IT managers of small and medium sized companies based in Toronto, Canada and across Canada. It discusses what is a reportable breach, how to make a decision on reporting, what should be in a report and what the retention obligation is.

This document is for informational purposes only and does not constitute legal advice. Consult a privacy lawyer regarding a particular

Does PIPEDA apply to your business?

PIPEDA stands for the Personal Information Protection and Electronic Documents Act. In most cases, this is applicable to organizations that collect, use or disclose personal information in the course of commercial activities.

This affects Toronto and Ontario businesses in that Ontario does not have any privacy law covering the private sector. Majority of business in Ontario are covered under PIPEDA. However, businesses within the healthcare industry will be covered under the separate health privacy law of PHIPA.

Other provinces have their own regulations:

Quebec: Under Law 25, there are “confidentiality incident” reporting requirements to the privacy authority of Quebec called the Commission d’accès à l’information.

Alberta & British Columbia: Both have their own Personal Information Protection Act (PIPA), which applies to provincially regulated private-sector organizations. Alberta has its own breach notification regulation for its PIPA.province, one incident can trigger more than one set of obligations. Work out which laws apply before an incident happens, not during one.

What counts as a “breach of security safeguards”?

PIPEDA defines a breach of security safeguards as the loss of, or unauthorized access to or disclosure of, personal information. It results from a breach of your safeguards or from a failure to put safeguards in place.

That is broader than a “hack.” Common examples include:

  • A phishing attack that gives an attacker access to a mailbox full of customer records
  • Ransomware that encrypts or copies files containing personal information
  • An employee emailing a spreadsheet of client data to the wrong person
  • A lost or stolen laptop or phone that is not encrypted
  • A misconfigured cloud storage folder or shared link that exposes files
  • A former employee whose access was never removed
  • A vendor or service provider you rely on suffering its own breach

Several of these involve no attacker at all. A misdirected email can trigger the same assessment as a ransomware incident.

PIPEDA breach reporting requirements at a glance

Here is what the law asks of you once you become aware of a breach.

ObligationWhat it meansApplies to
Assess the riskDecide whether the breach creates a real risk of significant harm (RROSH)Every breach
Report to the OPCSubmit a report as soon as feasible after you determine a breach occurredRROSH breaches
Notify individualsTell affected people directly, as soon as feasibleRROSH breaches
Notify other organizationsTell any organization or government institution that may be able to reduce the harmWhen applicable
Keep recordsKeep a record of the breach for 24 months after you determine it occurredEvery breach, even if not reported

The last row catches many businesses out. You do not have to report every breach to the OPC, but you do have to record every one.

RROSH under PIPEDA: how to decide whether to report

RROSH stands for “real risk of significant harm.” It is the threshold that triggers the duty to report and notify.

What is “significant harm”?

Personal information under PIPEDA may include physical injury, humiliation, damage to reputation/relationships, loss of employment/business opportunities, financial loss, identity theft, negative impact on the credit rating, and property damage/loss.

What qualifies a risk as being a “real” risk?

PIPEDA advises you to take into consideration at least two things:

The sensitivity of the personal information. Information relating to finances, government identification numbers, health, and login information is normally more sensitive than an email for business purposes.

The likelihood of improper use. You can inquire about the parties that have had access to the information, whether they were authorized, if the information was encrypted, if it was copied, sold or published.

Also document the number of people affected, how long the exposure lasted, whether the data was recovered, and whether the recipient is trusted. The OPC also publishes a RROSH assessment tool that can help structure your thinking.

A simple way to think about it

Scenario (illustrative)Likely assessmentWhy
Unencrypted laptop with customer financial files is stolen from a carLikely reportableSensitive data, no encryption, unknown recipient
Ransomware group claims to have copied HR files and threatens to publish themLikely reportableSensitive data, clear malicious intent
Staff member emails a client list to the wrong internal colleague, who deletes itPossibly not reportable, but record itLow probability of misuse, trusted recipient
Encrypted backup drive is lost, and the key was not with itNeeds careful assessmentStrong encryption may lower the probability of misuse; document your reasoning

These examples illustrate the thinking, not legal rulings. Every incident turns on its facts. When you are unsure, treat it as reportable and get advice.

How to report a data breach in Canada to the OPC

Businesses covered by PIPEDA report to the Office of the Privacy Commissioner of Canada using the OPC’s secure online breach reporting form. You can also submit the information in another format, including the OPC’s PDF form, as long as it contains everything required.

A report to the OPC must include:

  • A description of the circumstances of the breach and, if known, its cause
  • The date, or period, during which the breach occurred
  • A description of the personal information involved
  • The number of individuals affected, or an estimate
  • The steps you have taken to reduce the risk of harm
  • The steps you have taken or intend to take to notify affected individuals
  • The name and contact details of someone who can answer questions about the breach

“As soon as feasible” does not mean “when the investigation is finished.” If you already have enough to conclude that RROSH is met, report. You can add new information to the report later.

Notifying affected individuals

The notice to individuals should provide sufficient information to enable them to understand the importance of the breach and take necessary measures to safeguard themselves. The notice should also make them aware of your internal complaints procedure and their right to lodge a complaint with the OPC. Normally, the notice should always be made directly through an email, letter or telephone call. Indirect notice is possible only under certain limited conditions; please consult counsel to verify whether this is acceptable.

An effective notice would be one which uses clear language and provides specific information.

Notifying other organizations

If another organization or government institution could help reduce the risk of harm, you must notify them too. Examples include your bank, a payment processor, or law enforcement. Check your cyber insurance policy early, as many policies require prompt notice and may require you to use approved incident response providers.

Breach record keeping under PIPEDA

You must keep a record of every breach of security safeguards involving personal information under your control. This applies whether or not you reported it. Keep each record for 24 months after the day you determine the breach occurred. The OPC can ask to see your records.

Your record should let a reader understand what happened and why you decided what you decided. Include:

  • The date or period of the breach and the date you became aware of it
  • A description of the circumstances and cause
  • The type of personal information involved and the number of people affected
  • Your RROSH assessment and the reasoning behind it
  • Whether you reported to the OPC and notified individuals, with dates
  • The containment and remediation steps taken

Practical tip: Keep a simple breach register (a spreadsheet or ticket queue is fine) and a standard template. Businesses with no register often discover that “minor” incidents from the past year were never written down.

What are the penalties?

Intentionally not reporting a breach, notifying individuals, or maintaining breach documentation is considered a violation according to PIPEDA. Penalties can range from a maximum of $10,000 if the matter is a summary offense or $100,000 if the offense is indictable. However, the Office of the Privacy Commissioner does not impose any fines or prosecute violations. Instead, it will investigate complaints, audit, issue reports, and any binding orders will have to be applied for from the Federal Court.

Reputational damage is a larger penalty. The findings of the OPC may be published and customer attention drawn to it.

Is PIPEDA changing?

In June 2026, the federal government brought forward Bill C-36 to replace the private-sector component of PIPEDA with a new piece of legislation and grant the new regulator order-making and penalty powers. As at the time of writing, it had yet to pass, so PIPEDA was still the legislation. Please verify for yourself before taking any of this to heart.

A practical response checklist

When you suspect a breach, work through this list. The order matters.

  • [ ] Contain. Isolate affected devices, disable compromised accounts, revoke tokens, and stop any ongoing data loss.
  • [ ] Preserve evidence. Do not wipe systems before logs and images are captured.
  • [ ] Start the record. Note the time you became aware and who is involved.
  • [ ] Identify the data. Which systems, which personal information, how many individuals, which provinces?
  • [ ] Assess RROSH. Document sensitivity, probability of misuse and your reasoning.
  • [ ] Call your advisers. Privacy counsel, your cyber insurer and your IT or SOC provider.
  • [ ] Report to the OPC and any applicable provincial regulator if the threshold is met.
  • [ ] Notify individuals and other relevant organizations.
  • [ ] Remediate. Fix the root cause, such as MFA gaps, unpatched systems or over-broad access.
  • [ ] Review. Update your incident response plan and training.

Common mistakes with PIPEDA breach reporting requirements

These are the mistakes that come up most often:

  1. Waiting for certainty. Teams wait for a full forensic report before deciding. The law expects a report as soon as feasible once RROSH is met, not after every question is answered.
  2. Assuming “no ransom paid” means “no breach.” If data was accessed or copied, a breach may have occurred whether or not anyone was paid.
  3. Forgetting about vendors. The duty to report generally sits with the organization that controls the personal information, even if a supplier was the one breached. Your contracts should say who reports and require suppliers to tell you promptly.
  4. Not recording “small” incidents. The 24-month record duty applies to all breaches.
  5. No logging. If you cannot tell what was accessed, you may not be able to rule out harm, which often forces a worst-case assessment.
  6. Weak backups. Without clean, tested, offline or immutable backups, ransomware recovery is slower and costlier.
  7. Improvising the notice. Drafting customer letters mid-crisis leads to vague or inconsistent messages. Prepare templates in advance.
  8. Ignoring provincial rules. A Toronto business with customers in Quebec or Alberta may face additional obligations.

A real-world style scenario (anonymous and illustrative)

Take a mid-sized professional services firm in the GTA. One of the firm’s employees falls for a phishing attack and as a result, the attacker manages to get access to a shared mailbox with copies of IDs and financial statements of clients stored there over several years.

The IT team manages to reset the passwords and block the attacker in just a few hours, but because mailbox auditing was never enabled, it is impossible to trace which emails were accessed. Due to that, along with the highly sensitive nature of the information and the obvious malicious intent behind the breach, the assessment goes in favor of meeting RROSH.

The important thing is not whether each phishing attack is reportable or not. The important thing is how you log, use MFA and monitor.

How to reduce breach risk before you have to report one

Reporting is a response. The better outcome is not having a reportable incident. PIPEDA expects safeguards proportionate to the sensitivity of the information. Practical controls to consider:

  • Multi-factor authentication on email, remote access and admin accounts
  • Endpoint protection and patching on a monitored schedule
  • 24/7 monitoring through a cybersecurity and SOC monitoring service so suspicious activity is spotted and escalated quickly
  • Encryption for laptops, mobile devices and sensitive data
  • Least-privilege access and prompt removal of departed staff
  • Tested backups separated from your production network, such as managed backup and recovery
  • A written incident response plan with named roles and a tested contact list
  • Staff awareness training focused on phishing and misdirected email

The Canadian Centre for Cyber Security publishes practical guidance for small and medium organizations that can help you prioritize these controls.

How Sandser Technology Services can help

  • Setting up logging and monitoring so you can answer “what was accessed?” quickly
  • Hardening email, identity and endpoint security
  • Building and testing backup and recovery processes
  • Helping draft an incident response plan and breach register that fit your size and sector

We are not a law firm, and we do not provide legal advice or guarantee compliance outcomes. We work alongside your legal counsel so the technical evidence and the legal decisions line up.

Conclusion: know the rules before you need them

The breach notification provisions under PIPEDA are based on four specific steps that must be taken. These are assessing the risk of significant harm, reporting to OPC if the condition is fulfilled, notifying affected individuals, and documenting all breaches for 24 months. Companies that deal with incidents in a proper way have always decided on these issues prior to the incident.

If you are not confident that your system allows you to do all this, find this out now, not during an incident.

Frequently Asked Questions

What is PIPEDA compliance in Canada?

Compliance with PIPEDA entails handling personal information in accordance with the law. This means that one must only collect necessary information, obtain proper consent, implement reasonable security measures, and respond to access requests in line with PIPEDA. There are also provincial laws governing the collection and use of private sector information in Alberta, British Columbia and Quebec.

What is RROSH under PIPEDA?

What RROSH stands for “real risk of significant harm.” This is the point at which reporting is done to OPC and notice is given to individuals. One will determine it based on the sensitivity of the data, risk of misuse, among other considerations. Record your rationale, whether or not you report.

How do I report a data breach in Canada?

If PIPEDA applies, submit a report through the OPC’s secure online breach reporting form and notify affected individuals as soon as feasible. Quebec, Alberta and British Columbia have their own regulators and rules, so check which laws apply to your operations before you file.

Do I have to report every privacy breach in Canada?

No. Under PIPEDA, you must report to the OPC and notify individuals only when a breach creates a real risk of significant harm. You must still keep a record of every breach of security safeguards, including those you decide not to report, for 24 months.

Are companies required to disclose data breaches?

Yes, when a breach creates a real risk of significant harm. You must report it to the OPC and notify affected individuals. You are not required to disclose every incident publicly, but every breach must be recorded, and the OPC can ask to see those records.

What are the requirements for notifying individuals about a data breach in Canada?

Individuals must be directly notified as soon as possible. Be sure to explain what occurred, what personal information was affected, what actions you are taking regarding the breach, and what the individual can do to safeguard themselves. Provide relevant information concerning the notification process for complaints, as well as how they can file a complaint to the OPC.

What should a PIPEDA data breach notification include?

Use plain language and be specific: the circumstances of the breach, the personal information involved, the steps you have taken to reduce harm, and practical steps the person can take, such as watching for phishing or monitoring credit reports. Add a named contact for questions. Prepare a template in advance.

How long do I need to keep breach records under PIPEDA?

Maintain a written account of all instances of failure in securing information protection measures for 24 months from the date of discovery of such failure. This must contain the details of the occurrence, the type of information involved, your RROSH assessment, and other notifications. This is subject to review by the OPC.Keep a record of every breach of security safeguards for 24 months after the day you determine the breach occurred. It should show what happened, what data was involved, your RROSH assessment and any notifications made. The OPC can ask to see these records, so keep them organized.

Who is responsible for enforcing PIPEDA in Canada?

PIPEDA is supervised by the Office of the Privacy Commissioner of Canada. It has the authority to investigate complaints and perform audits, but it cannot impose fines. For binding orders, an application must be made to the Federal Court. There are provincial commissioners in Quebec, Alberta, and British Columbia.

Leave a Comment

Your email address will not be published. Required fields are marked *