ClearBreach
On this page

← Playbooks

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.

What to do now →
PIPEDAAB PIPABC PIPAAll sectors

Accidental Email Disclosure, What Canadian Organizations Must Do

By Yong Du · Updated June 12, 2026

Share on LinkedIn

When personal information is sent to the wrong recipient, PIPEDA and PIPA breach obligations apply, how to assess and who to notify.

⚡ In an active breach right now?

Use the quick reference guide, built for use during an incident.

Open response guide →

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.

What makes accidental email disclosure different from other breaches

Accidental email disclosure is one of the most common breach types, and one of the most likely to be mishandled in both directions. Organizations either report disclosures that do not reach the RROSH threshold, or dismiss disclosures that do.

The distinction that matters: unlike ransomware or phishing, accidental disclosure is not malicious. The recipient is usually a known individual (a colleague at the wrong company, a client whose address was transposed) not a threat actor. That changes the RROSH calculus significantly.

In most single-recipient accidental email disclosures involving non-sensitive personal information, RROSH is not present. The breach still requires internal documentation. Reporting to the OPC and notifying affected individuals is not automatic. It follows from a RROSH determination, not from the fact that personal information was disclosed.

The risk cuts the other way too. Organizations that dismiss every accidental email as "just a mistake" miss the disclosures that do cross the threshold, mass disclosures, unknown recipients, or disclosures of sensitive data that create genuine harm potential.


Most emails sent to the wrong person do not need to be reported. But a misdirected email with health, financial or ID information, an unknown recipient, or a list exposed through CC instead of BCC often does. Ask for deletion in writing, record everything, and assess before you decide. Even a list of email addresses can be sensitive when it reveals who uses a service.

Immediate containment, accidental email disclosure specifically

Do not assume the email was not read. Recall attempts across different email clients and domains are unreliable. Until you confirm the recipient did not open the email, treat the information as accessed.

Do not handle this informally. When a disclosure seems minor, it is tempting to sort it out by phone and move on. If it later draws a regulator's attention, because the recipient complained or the data was misused, you will have no record of what you did.

Containment steps specific to accidental email disclosure:

  • Contact the recipient directly and request deletion of the email and any attachments, document this contact and the response received
  • Attempt an email recall if your mail system supports it, document the attempt and whether success was confirmed
  • Identify every recipient, check To, CC, and BCC fields and any forwarding that may have occurred
  • Identify exactly what personal information was disclosed, body text and all attachments
  • Determine whether the recipient is known (a specific named individual) or unknown (domain typo, unrecognized address)
  • Assess the sensitivity of the disclosed information, contact details only, or health, financial, credential, or government-issued ID data?
  • Preserve the original sent email, any recall confirmation, and all communications with the recipient

What drives RROSH in accidental email disclosure

Accidental email disclosure has a different RROSH profile than other breach types. Because there is no malicious intent, the probability of misuse usually starts lower. The factors that actually move the assessment:

1. Sensitivity of the disclosed information. This matters most. Contact details sent to the wrong person rarely create a real risk of significant harm (RROSH). Health information, account details, SINs, passwords, or a mix that enables identity theft change the picture entirely. One health record sent to an unknown recipient is high risk, whatever the size of the organization.

2. Whether the recipient is known or unknown. An email to the wrong colleague is unlikely to be misused. A typo in the domain that sends it to an outside address you cannot verify means you cannot know who received it or whether they read it. Then you cannot judge the chance of misuse, and regulators expect you to assume the worse case.

3. Volume of recipients. A Reply All that exposes personal information to an outside mailing list is a different thing from one email to the wrong person. The number of people affected counts directly. So does exposure between recipients: using CC instead of BCC on a subscriber list shows every person on it to every other.

4. Combination effect. Information that is not sensitive alone can be sensitive together. A name, employer, salary and home address together carry real identity risk. Ask what the recipient could do with it, not just what each field is.

The factor that reduces RROSH: Written confirmation of deletion from a known, cooperative recipient is the main thing that lowers the risk. It does not remove the duty to keep a record, but it bears directly on the chance of harm. A spoken confirmation is not enough.


Likely verdict range

No duty to report is the most common outcome: one email to a wrong but identifiable recipient, information that is not sensitive, and deletion confirmed in writing.

Reporting is likely required when:

  • Sensitive personal information was disclosed, health data, financial account details, SIN, credentials
  • The recipient is unknown or has not responded
  • Multiple external recipients received the disclosure
  • The email contained attachments with personal information on multiple individuals
  • The disclosed information in combination enables identity theft or financial harm

In practice: most misdirected emails do not need reporting. But the ones that do are often underestimated, because the incident seems minor until you look at what was sent and to whom. Assess every incident. Do not decide the outcome from how accidental it was.

Most wrong-recipient emails do not need reporting. Is yours one of the ones that does? 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

Under PIPEDA, keep a record whatever the outcome. Every breach of security safeguards must be recorded and the record kept for 24 months, whether or not the risk test is met (s.10.3). Alberta and BC PIPA do not require it, but the record is your evidence of how you assessed the incident. Skipping it on minor incidents leaves a gap that shows up in OPC investigations.

A recipient's confirmation informs the assessment; it does not settle it. Record a written confirmation of deletion and weigh it in your decision. It bears on the chance of harm. It does not remove the duty to keep a record, and it does not by itself settle a disclosure of highly sensitive information.

Alberta PIPA. If the disclosure happened in your Alberta activity and the threshold is met, report to the OIPC Alberta at breachnotice@oipc.ab.ca. If PIPEDA also applies, file with the OPC at the same time.

BC PIPA, voluntary reporting option. BC PIPA has no breach reporting duty, so any report to the OIPC BC is voluntary. For a significant disclosure 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.

Repeat disclosures draw regulators' attention. One accidental disclosure is an incident. A pattern, even of minor ones, points to weak safeguards, and regulators treat it that way (PIPEDA Principle 7). If this has happened before, fix the cause, not just this disclosure.


Documents you will need

For an accidental email disclosure where RROSH is confirmed:

  • Internal Incident Record: required under PIPEDA and good practice otherwise; document the disclosure, containment steps, recipient communications, and RROSH determination; retain for 24 months
  • OPC PIPEDA Breach Report: required if PIPEDA RROSH threshold is met
  • OIPC Alberta PIPA Notification Form: required if Alberta PIPA applies; email to breachnotice@oipc.ab.ca
  • OIPC BC voluntary report: BC PIPA requires none; consider one for a significant disclosure in your BC activity
  • Individual Notification Letter: required under PIPEDA when RROSH is met; in Alberta, required when the commissioner directs it, and best sent with the report; in BC, expected where there is a risk of harm

For disclosures where RROSH is not present:

  • Internal Incident Record only: required under PIPEDA, good practice elsewhere; retain for 24 months

ClearBreach tells you which of these you need, and gives you each one from your assessment answers.


Common mistakes, accidental email disclosure specifically

Deciding before assessing. "It was just one email to the wrong person" is not an assessment. Neither is "we sent health records to the wrong address, so we must report." The outcome depends on specific factors. Assess first, then decide.

Missing recipients. CC lists, forwarded threads and shared attachments can reach more people than the original wrong recipient. Find everyone who may have seen it before you finish the assessment.

Treating a recall as the end of it. Recall is unreliable across email domains, and it cannot undo an email already opened. It is a containment step, not proof the information was not seen.

Skipping the record on minor incidents. PIPEDA's 24-month record duty has no severity threshold: every breach of security safeguards needs one. Skipping it on minor disclosures leaves a pattern you cannot explain in a regulatory review.

Accepting a verbal confirmation. A recipient saying on the phone that they deleted it leaves no record. Ask in writing and keep the reply. It belongs in your incident record and bears on your assessment.


Real-world example, accidental email disclosure

An Alberta psychology practice sent an email notification to 18 clients announcing a change to the psychologist's email address. A staff member used the "To" field instead of "Bcc," making every client's email address visible to all 18 recipients. Two clients noticed the error and reported it the same day. The practice notified all affected individuals by email the following morning.

The information disclosed was email addresses only, no health records, session notes, or financial data left the organization's control.

OIPC Alberta found a real risk of significant harm. Every recipient could now infer that each person on the list had contacted a psychology practice. That link to a mental health service is itself sensitive, and can cause hurt, humiliation and embarrassment. The practice had also not recorded whether it asked recipients to delete the email and not forward it, so the risk of further use remained.

OIPC Alberta required individual notification under PIPA s.37.1(1). Because the practice had already notified clients the following day, no re-notification was required. The corrective action adopted: no mass emails to be sent without a second person confirming the Bcc field before sending.

What a prepared organization would have done: when it first wrote to clients, ask each recipient in writing to delete the email and not share it, and keep any written confirmations. That one step would have dealt with the risk of further use that kept the finding high.

Source: OIPC Alberta, Decision P2023-ND-002, Breach notification decisions


MSP note

If you are an MSP and the disclosure came from a client's environment, your duties depend on your role. Check that your service agreement says who leads the assessment, and requires you to tell the client promptly about any incident involving its data.

If the disclosure originated from a tool or system you manage, document your involvement and cooperate fully with your client's assessment.

On an MSP plan, you can run the assessment for a client from your own account and get the documents it calls for.


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 that are not covered here.



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.

Frequently asked questions

Do I have to report an accidental email sent to the wrong person?

Not automatically. The reporting obligation depends on whether the disclosure creates a real risk of significant harm (RROSH) to the individuals whose information was exposed. Most single-recipient accidental disclosures involving non-sensitive contact information do not reach the RROSH threshold. Disclosures involving health information, financial data, SINs, or credentials, or disclosures to multiple or unknown recipients, are more likely to trigger reporting. Document the incident regardless of your RROSH determination.

What is the reporting deadline for accidental email disclosure under PIPEDA?

If RROSH is present, PIPEDA requires you to report to the OPC as soon as feasible after making the RROSH determination. There is no fixed number of days. The OPC expects prompt action once you have determined RROSH is present, not once your internal review is fully complete. Notify affected individuals on the same timeline.

Does a Reply All email to an external list require a breach report?

It depends on what was in the email and who received it. If the email contained only non-sensitive content, RROSH is unlikely. If the body or attachments contained health information, account details, financial data, or other sensitive personal information, RROSH assessment is required. The number of external recipients and whether they are known to the sender both factor into the assessment.

I recalled the email immediately, do I still have to report?

A successful recall reduces but does not eliminate the RROSH assessment obligation. You must determine whether the recipient accessed the email before the recall executed. Most recall functions are unreliable across different email clients and domains. If you cannot confirm the email was unread at the time of recall, you cannot assume it was not accessed. Document the recall attempt and its confirmed outcome as part of your internal incident record.

Does accidental email disclosure require reporting under Alberta PIPA?

Yes, if the threshold is met. Alberta PIPA uses the same real risk of significant harm test as PIPEDA, and applies to activity in Alberta. Report to the OIPC Alberta at breachnotice@oipc.ab.ca, which can then require you to notify the people affected; notifying them with the report is the better course. If PIPEDA also applies to the activity, report to the OPC too.

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 →

See plans and pricing

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