On this page
Your SituationWe had a privacy incident →
In the middle of a breach?
ClearBreach shows whether you must report, to whom and by when, under each law that applies, and writes the reports.
Vendor or Third-Party Breach, What Canadian Organizations Must Do
By Yong Du · Updated June 13, 2026
When your IT provider, SaaS platform, or payroll processor is breached, your PIPEDA and PIPA accountability does not transfer to them.
⚡ In an active breach right now?
Use the quick reference guide, built for use during an incident.
This playbook 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.
When a vendor holding your data is breached, the duty to assess, report and notify stays with you, not the vendor. Find out what you shared with it, get the scope in writing, and decide whether there is a real risk of significant harm. Do not wait for the vendor's report or its forensics.
Which laws apply
| Jurisdiction | Applies when | Regulator |
|---|---|---|
| PIPEDA | The vendor processed personal information in the course of your commercial activity; or the breach involves personal information about individuals in provinces without substantially similar legislation (Ontario, Manitoba, New Brunswick, and others) | Office of the Privacy Commissioner of Canada (OPC), priv.gc.ca |
| Alberta PIPA | The breach involves your organization's activity in Alberta, including its employees there | OIPC Alberta, oipc.ab.ca / breachnotice@oipc.ab.ca |
| BC PIPA | The breach involves your organization's activity in BC, including its employees there | OIPC BC, oipc.bc.ca |
More than one of these can apply. If the threshold is met, report separately to the OPC and the OIPC Alberta where each applies; a report to the OIPC BC is voluntary.
What makes this scenario different
In most breaches, you know what happened on your own systems. Here, the breach happened at a supplier: your IT provider, a SaaS platform, a payroll processor, a cloud storage service or a bookkeeper. Your data was caught in it.
You depend on someone else to tell you what happened, what data was affected and what they are doing. That makes it tempting to wait and assume the vendor will handle it. Waiting is the most common and most costly mistake here.
Your accountability did not move when the data did. Under PIPEDA clause 4.1.3, Alberta PIPA s.5(2) and BC PIPA s.4(2), you stay accountable for personal information you gave a third party to process, whatever your contract says. If the data was exposed and there is a real risk of significant harm (RROSH), the duty to report and notify is yours. The vendor's own notice does not meet it.
Immediate steps, this scenario specifically
1. Confirm what personal information you transferred to the vendor. You cannot assess the risk without knowing what was exposed. Pull your record of what you share with this vendor. If you have none, rebuild it from contracts, onboarding records and how you actually work. What kinds of personal information did it receive, and whose: customers, staff, patients, clients?
2. Get written confirmation of the breach scope from the vendor. Contact the vendor now. Ask in writing which systems were affected, what kinds of data were involved, whether your data was confirmed accessed or only at risk, and the timeline of the breach and their response. Do not accept a verbal summary; keep everything in writing from here on.
3. Check your contract and DPA. Your contract or data processing agreement may require the vendor to tell you within a set time, give breach details in a set form, and help with your regulatory response. Check whether it has. If not, put it on notice in writing.
4. Do not issue a public statement or notify individuals yet. Notice sent before you know what was affected causes confusion and may be wrong. Assess the risk first, then notify.
What drives RROSH in this scenario
The test turns on what the vendor actually held for you, and whether the breach really exposed the people it was about.
Factors that push toward RROSH:
- The vendor held sensitive categories of information: health data, financial records, SINs, passwords, government-issued ID numbers, or information about minors
- The breach involved confirmed unauthorized access, not just a system vulnerability
- The vendor held a combination of information types that together enable identity theft or fraud (name + SIN + date of birth is more dangerous than any single field)
- The individuals at risk are vulnerable, patients, employees, clients with high-value financial information
- The vendor is an IT managed service provider who held credentials or system access beyond just data files, compromised credentials may give attackers access to your own systems
Factors that push against RROSH:
- The vendor held only basic contact information (name and email) with no financial, health, or identity-enabling data
- The vendor confirmed the breach was limited to systems that did not contain your organization's data
- The breach involved an encrypted dataset and the encryption key was not compromised
- The vendor held aggregated or anonymized data with no individual identifiers
The combination effect. A vendor often holds several kinds of information. An HR platform may hold staff names, addresses, SINs, direct-deposit banking and emergency contacts. Each alone may seem low risk; together they create a real risk.
Likely verdict range
| Vendor type and data held | Typical verdict |
|---|---|
| IT MSP with access to systems containing customer records, employee data, or financial files | RROSH, access to systems is access to data |
| Payroll processor holding employee SINs, banking details, salary information | RROSH, combination of SIN + financial data is high-risk by definition |
| SaaS CRM holding customer name, email, and phone number only | Case-by-case, depends on volume and whether additional context was stored |
| Cloud storage holding encrypted files where key was not compromised | Likely no reporting obligation, but confirm encryption scope |
| Bookkeeping platform holding client financial records and SINs | RROSH, financial data + SINs |
| Email marketing platform holding name and email only | Likely no reporting obligation for most scenarios, but assess volume and targeting risk |
Does your vendor's breach need reporting by you? It turns on what you shared with them. That is the decision ClearBreach makes, under PIPEDA, Alberta PIPA and BC PIPA at once. See it made on a real case →
Scenario-specific obligations and complications
If RROSH is determined:
- OPC notification (PIPEDA): Report to the Office of the Privacy Commissioner of Canada as soon as feasible after determining RROSH. Use the OPC breach report form. Do not wait for the vendor to report on your behalf.
- OIPC Alberta notification (AB PIPA): Notify the OIPC Alberta without unreasonable delay.
- OIPC BC (BC PIPA): No legal duty to report; a voluntary report is encouraged for a significant breach in your BC activity.
- Individual notification: Notify each affected individual directly (required under PIPEDA; in Alberta when the commissioner directs, and best sent with the report; expected in BC). Describe what happened, what information was involved, what your organization and the vendor are doing, and what the individual can do to protect themselves.
If RROSH is not determined:
- No regulator notification required under PIPEDA or Alberta PIPA.
- No individual notification required.
- Internal breach record, required under PIPEDA and good practice otherwise: document your assessment and your reasoning.
- Consider whether the vendor relationship needs to be reviewed or additional safeguards added.
BC PIPA, voluntary reporting option. BC PIPA has no breach reporting or notification duty, so any report to the OIPC BC is voluntary. For a significant breach in your BC activity, the BC Commissioner encourages a report and expects the people affected to be told where there is a risk of harm. See BC PIPA Breach Reporting.
For Ontario organizations. Ontario has no provincial private-sector privacy legislation, PIPEDA is the applicable framework. Report to the OPC at priv.gc.ca. No separate provincial regulator report is required. See Ontario Data Breach Reporting Requirements.
Complications specific to this scenario:
The vendor notifies regulators. Does that meet your duty? No. The vendor may have duties for its own information, such as its staff records. For information it held for you, the duty to assess, report and notify is yours, as the organization that controls it.
The vendor is not a Canadian organization. Your accountability does not stop at the border. If a US platform or payroll processor holding your data is breached, your Canadian duties still apply. The vendor meeting US breach laws does not meet yours.
You cannot reach the vendor or the vendor has gone out of business. Assess the risk on what you know. Your duties do not pause because the vendor cannot be reached. Record your attempts to contact it, and assess on the last known scope of what you shared.
The breach is a supply chain breach, your vendor's vendor was breached. Your accountability covers the data however many layers of subcontractors it passed through. Assess the risk on what personal information reached the affected systems, even with no direct relationship with the breached company.
Documents you will need
Regardless of RROSH determination:
- Internal breach record: date discovered, vendor involved, data categories affected, number of individuals, RROSH assessment and outcome, actions taken
- Written correspondence with the vendor documenting what they disclosed and when
If RROSH is determined, also:
- OPC breach report (PIPEDA)
- OIPC Alberta breach report (AB PIPA), if the breach involves your Alberta activity; email breachnotice@oipc.ab.ca
- OIPC BC voluntary report (BC PIPA), if the breach involves your BC activity and is significant
- Individual notification letters, one per affected individual or one per household
ClearBreach tells you which of these you need, and gives you the regulator reports and notification letters from your assessment answers.
Common mistakes in this scenario
Waiting for the vendor to report for you. The vendor's report covers its accountability, not yours. If the test is met, you notify on your own. Regulators have had complaints from people never told, because the vendor and its client each assumed the other had done it.
Treating the data processing agreement as a shield. An agreement requiring the vendor to tell you promptly and help you respond is a contract. It does not remove your legal duty to the people whose data was exposed. If the vendor breaks it, you have a claim against the vendor. You still owe the affected people.
Not knowing what data you shared. Many organizations cannot say, in the first day, what personal information the vendor holds for them. The assessment cannot go ahead without that answer. No law names a vendor data inventory, but you cannot meet your breach duties without one.
Assuming encrypted data is safe. Encryption protects stored data only if the key was not compromised. If the attackers reached both data and keys, or the vendor cannot say, treat the data as exposed.
Waiting for the vendor's forensics report. Those investigations can take months. Organizations often tell people nothing until the report arrives, then find the OPC expected notice as soon as feasible after the risk was determined. Notify when you determine the risk, not when the vendor finishes. If important new facts emerge, send a follow-up.
What regulators have found
OIPC Alberta: An Alberta insurance brokerage's cloud hosting provider was hit by ransomware. The provider held driver's licences, driving records, and banking and card details for up to 7,000 people, and could not say what had been taken. OIPC Alberta found the duty to notify belonged to the brokerage, not the vendor. The brokerage had collected the information and passed it on under a service arrangement. The data moved; the accountability did not. That holds in every sector: if your vendor is breached, you notify.
Sources: OIPC Alberta, Decision P2023-ND-016, Breach notification decisions
MSP note
If you are an MSP managing this response on behalf of a client:
The client stays accountable under PIPEDA, Alberta PIPA and BC PIPA. Your job is to help it find what was affected, assess the risk and meet its notice duties, not to take on its accountability.
If your own systems were breached, you are the vendor here. Tell your clients promptly, as your contracts likely require, so each can assess and report for the data it controls. You may also have duties of your own for information you control, such as your staff records.
Keep the two roles clearly separate in your records: what you do for the client, and what you do as the breached party. Regulators expect to see which organization is making which notice.
Ready to assess this breach? Find out whether you must report it, to whom and by when, under each law that applies, with the regulator reports and notification letters to send. See it done on a worked case →
The demonstration is the real assessment, already answered for a fictional company, with three answers left for you to change. It ends on the verdict and the documents it produced. See a real verdict → to run it on your own breach.
This playbook covers PIPEDA, Alberta PIPA, and BC PIPA obligations for private-sector organizations. If your organization handles personal health information under provincial health legislation, such as Alberta's Health Information Act or BC's E-Health (Personal Health Information Access and Protection of Privacy) Act, additional obligations may apply when a vendor holding that information is breached. Those obligations are not covered here.
Related guides
- How Canadian Regulators Decide Whether a Breach Must Be Reported. More real regulator decisions, across every type of breach
- PIPEDA Breach Reporting Requirements, when and how to notify the OPC under PIPEDA
- Alberta PIPA Breach Notification, AB PIPA notification obligations and OIPC process
- BC PIPA Breach Reporting, what BC PIPA does and does not require after a breach, and the OIPC BC process
- What Is RROSH?, the real risk of significant harm standard explained
- Vendor / Third-Party Breach, Quick Reference, checklist for use during the incident
Frequently asked questions
My vendor was breached, do I have to report it?
It depends on what personal information the vendor held on your behalf and whether its exposure creates a real risk of significant harm (RROSH) to the individuals whose information it was. The breach happening at the vendor's systems does not change your accountability. Under PIPEDA clause 4.1.3, Alberta PIPA s.5(2) and BC PIPA s.4(2), you remain responsible for personal information you transferred to a third party for processing. If RROSH is present, you must notify the applicable regulator and affected individuals, whether or not the vendor also reports.
Does a Data Processing Agreement mean the vendor handles the breach notification, not me?
No. A DPA allocates contractual responsibility and may require the vendor to notify you promptly and assist with your response. It does not transfer your statutory accountability to the individuals whose information was exposed. Under PIPEDA, you are the organization accountable for the personal information, the vendor processed it on your behalf. Two separate obligations may result: the vendor's own regulatory notification (if they are also a covered organization) and your notification as the accountable organization.
What if my vendor will not tell me exactly what data was accessed?
You cannot wait indefinitely for vendor confirmation. If the vendor confirms a breach occurred and your data was held in the affected systems, you have enough information to begin your RROSH assessment based on what you know you shared with them. Document your data-sharing inventory, what the vendor has disclosed so far, and the date you began your assessment. If the vendor's disclosure remains incomplete after a reasonable period, contact them formally in writing and consider whether your DPA gives you audit or access rights.
Can I wait for the vendor's investigation to complete before deciding whether to report?
No. PIPEDA requires you to report to the OPC as soon as feasible after determining RROSH is present, not after the vendor closes their investigation. You assess RROSH yourself based on what you know. If RROSH is determined, you notify. You do not need the vendor's investigation report to fulfill your own statutory obligation. Waiting months for a vendor forensics report while affected individuals remain unnotified is not a defensible compliance position.
Ready to assess this breach?
See whether you must report, to whom and by when, under each privacy law that applies to you, with the reports and letters to show for it.
How ClearBreach handles a breach →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