Data Breach Class Actions in Canada
Data breach class actions follow most major cyber incidents in Canada, but the law has shifted since Owsianik v. Equifax closed the door on intrusion upon seclusion claims against hacked organizations. This guide explains the remaining causes of action, PIPEDA's breach rules, proof of loss at certification, Quebec claims and how settlements are valued.

Key takeaways
- Owsianik (2022 ONCA 813): hacked database defendants do not commit intrusion upon seclusion.
- Jones v. Tsige set non-pecuniary intrusion damages at up to CAD 20,000.
- Negligence and contract claims require proof of compensable loss.
- PIPEDA s. 10.1 requires reporting and notification of breaches posing a real risk of significant harm.
- Quebec's low authorization threshold and Law 25 make it a frequent forum.
The landscape for data breach class actions in Canada
Data breach class actions follow most significant cyber incidents in Canada. Once an organization reports a breach to regulators and notifies affected individuals, proposed class actions are often filed within weeks, sometimes in several provinces at once. The legal theories have narrowed since 2022, when the Court of Appeal for Ontario held that the privacy tort of intrusion upon seclusion is not available against organizations whose databases were hacked by third parties. Claims now turn mostly on negligence, contract, consumer protection and statutory theories, and on whether class members suffered compensable loss.

For organizations, the practical stakes are defence costs, settlement exposure and the interaction with regulatory investigations. Decisions taken in the first days after an incident, about notification wording, credit monitoring offers, forensic reports and privilege, often shape the class action that follows.
Intrusion upon seclusion after Owsianik
The Court of Appeal for Ontario recognized the tort of intrusion upon seclusion in Jones v. Tsige, 2012 ONCA 32, where a bank employee repeatedly looked at the banking records of her partner's former spouse. The Court described three elements: the defendant's conduct must be intentional, which includes reckless; the defendant must have invaded, without lawful justification, the plaintiff's private affairs or concerns; and a reasonable person would regard the invasion as highly offensive, causing distress, humiliation or anguish. Proof of economic harm is not required, but the Court fixed the range of damages, where there is no pecuniary loss, at up to CAD 20,000.
Because the tort does not require proof of loss, plaintiffs sought to use it in data breach class actions against the organizations that held the data. In Owsianik v. Equifax Canada Co., 2022 ONCA 813, decided on 25 November 2022 with two companion appeals (Obodo v. Trans Union of Canada, Inc., 2022 ONCA 814, and Winder v. Marriott International, Inc., 2022 ONCA 815), the Court of Appeal held that a "database defendant" whose systems were breached by an outside hacker does not itself commit intrusion upon seclusion: the intrusion is the hacker's act, and a failure to prevent it, even a reckless one, is not the defendant's invasion of privacy.
The Supreme Court of Canada dismissed the application for leave to appeal in Owsianik (SCC docket 40577), as it did in the two companion cases.
| Defendant | Intrusion upon seclusion? | Other likely theories |
|---|---|---|
| Hacker or malicious insider | Yes, if the elements are met | Conversion, breach of confidence; often judgment-proof |
| Organization whose database was hacked by a third party | No, after Owsianik (Ontario) | Negligence, breach of contract, consumer protection, statutory privacy claims |
| Organization whose own employee deliberately accessed records | Possible vicarious liability, depending on the facts | Negligent supervision, breach of confidence |
| Organization that intentionally collected or used data unlawfully | Potentially, since the organization is the intruder | Statutory privacy torts in some provinces; consumer protection |
Negligence, contract and statutory claims
With intrusion upon seclusion largely unavailable against database defendants, data breach class actions focus on other causes of action:
- Negligence, alleging the organization failed to take reasonable security measures. Courts must consider whether a duty of care exists, what the standard of care required, and whether class members suffered compensable damage caused by the breach.
- Breach of contract, based on privacy promises in terms of service, privacy policies or customer agreements. The terms must actually create contractual obligations, and limitation of liability clauses may apply.
- Consumer protection statutes, alleging misrepresentations about security practices.
- Statutory privacy torts in British Columbia, Saskatchewan, Manitoba and Newfoundland and Labrador, which create causes of action for wilful privacy violations in some circumstances.
- Breach of confidence and fiduciary duty, in particular relationships such as health care.
Federal privacy law shapes these claims without creating a direct private right to sue in court for most breaches. Under s. 10.1 of the Personal Information Protection and Electronic Documents Act (PIPEDA), organizations must report to the Privacy Commissioner, and notify affected individuals of, any breach of security safeguards where it is reasonable to believe the breach creates a real risk of significant harm. Breach reports, notification letters and Commissioner findings are routinely relied on by plaintiffs as evidence of what happened and of the standard of care. Our insight on real risk of significant harm covers the notification test.
Proof of loss and certification
Proof of compensable loss is the central battleground in negligence-based data breach class actions. Courts have generally held that mere exposure of information, without more, is not compensable damage, and that ordinary upset or inconvenience falls short of the psychological harm required. Plaintiffs therefore point to time spent protecting themselves, out-of-pocket costs, actual fraud or identity theft, and the value of credit monitoring. Defendants point to the absence of evidence that data was misused and to remedial measures such as free monitoring.
At certification, the questions are whether the pleadings disclose a cause of action, whether there is some basis in fact for common issues, and whether a class proceeding is the preferable procedure. In Ontario, the 2020 amendments to the Class Proceedings Act, 1992 require that a class proceeding be superior to other reasonably available means and that common issues predominate over individual ones (s. 5(1.1)). In breach cases, individual questions about loss and causation can make that test hard to meet, particularly where only a small fraction of class members suffered any misuse of data.
Treat the breach notification letter as a future exhibit. Accurate, measured wording about what was accessed, what is known about misuse and what the organization is doing, combined with practical remediation such as monitoring, reduces both regulatory risk and the damages theory available to a class.
Quebec claims
Quebec is a frequent forum for data breach class actions. Authorization under art. 575 of the Code of Civil Procedure is generally treated as a low threshold, and Quebec's civil law framework assesses fault, injury and causation under the Civil Code rather than common law tort categories.
Quebec's private-sector privacy statute, as amended by Law 25, requires organizations to take measures to reduce the risk of injury after a confidentiality incident and to notify the Commission d'accès à l'information and affected persons where an incident presents a risk of serious injury. The CAI can impose administrative monetary penalties of up to the greater of CAD 10 million and 2% of worldwide turnover, and the statute also includes a private right of action for punitive damages in cases of intentional or grossly negligent infringement. Organizations with Quebec customers should expect a Quebec action to proceed alongside any common law province claims, as discussed in our insight on multi-jurisdictional class actions.
Incident response decisions that shape litigation
The first days after an incident create most of the evidence that will be examined in later litigation. Several decisions deserve legal input before they are made:
- Engaging forensic investigators. Who retains the investigator, under what terms and for what purpose affects whether the resulting reports can be withheld as privileged. Reports prepared for regulators or for business remediation are much harder to protect.
- Ransom decisions. Whether to engage with threat actors raises legal, sanctions and insurance issues, and the decision-making record may later be scrutinized. Our insight on ransomware payments covers the considerations.
- Scope of notification. Notifying too narrowly risks regulatory criticism; notifying too broadly, with alarming language, can inflate class size and the damages narrative. The real risk of significant harm test should be applied carefully and documented.
- Remediation offers. Credit monitoring, identity theft insurance and dedicated call centres help affected individuals and are often cited in defence of certification and in settlement negotiations.
- Record keeping. PIPEDA requires organizations to keep records of every breach of security safeguards, whether or not it meets the reporting threshold, and the Commissioner can request them. Under s. 10.3, those records must be kept and provided to the Commissioner on request, so they should be accurate and measured.
Timing matters as well. The longer an organization takes to detect, contain and disclose an incident, the more plaintiffs will argue that delay itself caused harm, for example by denying individuals the chance to change passwords or watch for fraud. A documented timeline showing when the organization learned each key fact and what it did in response is one of the most useful defence exhibits.
Boards should also consider governance exposure. Securities class actions can follow breaches at public companies if disclosure about cyber risk or the incident itself is alleged to have been misleading. Directors should ensure that cyber risk oversight is documented and that incident disclosure is coordinated between legal, investor relations and the security team.
Settling and defending data breach class actions
Settlement values in Canadian data breach class actions vary widely and depend on the sensitivity of the data, evidence of actual misuse, the number of class members, the strength of the remaining causes of action after Owsianik, and the defendant's remediation. Many settlements combine a modest fund for documented losses, extended credit monitoring and payment of class counsel fees approved by the court. Because loss evidence is often thin, some proposed class actions are discontinued or narrowed after certification challenges.
A defence strategy usually involves several workstreams:
- Privilege from day one. Retain forensic investigators through counsel so that the investigation is structured for privilege, recognizing that regulators may still require factual reports.
- Consistent public statements. Align regulatory reports, notification letters and media statements.
- Vendor claims. Review contracts with service providers whose systems were involved, for indemnities and notice requirements.
- Insurance. Notify cyber insurers immediately and coordinate counsel approvals.
- Early certification strategy. Focus on loss, causation and the preferability of individual or regulatory remedies.
Illustration: a hypothetical national retailer suffers a ransomware attack that exposes names, email addresses and partial payment card data of two million customers. It reports to the Privacy Commissioner and the CAI, notifies customers and offers two years of credit monitoring. Class actions are filed in Ontario, British Columbia and Quebec. Relying on Owsianik, the retailer moves to strike the intrusion claims in Ontario; the remaining negligence and contract claims proceed to a contested certification motion focused on whether class members suffered compensable loss, and the parties later negotiate a national settlement built around documented losses and extended monitoring.
How TRW & Co helps
We advise organizations on data breach class actions and the incidents behind them as part of our class actions, privacy and data protection and cybersecurity work. That includes privileged incident response, breach notification and regulator engagement, vendor and insurance claims, certification strategy and national settlement structuring, including Quebec. Court proceedings in Canada require Canadian-licensed counsel, and we work alongside them. This page is general information rather than legal advice. If you are responding to an incident or a claim, contact us.
Frequently asked questions
Can a company be sued for intrusion upon seclusion after a hack?
In Ontario, generally not where the company's database was breached by an outside hacker. In Owsianik v. Equifax Canada Co., 2022 ONCA 813, the Court of Appeal held that the hacker, not the database defendant, commits the intrusion. Leave to appeal to the Supreme Court of Canada was dismissed. Claims in negligence, contract and under statutes remain possible.
Do class members have to prove they suffered a loss?
For negligence and most contract claims, yes. Courts have generally held that exposure of information alone is not compensable damage. Plaintiffs therefore rely on evidence of fraud, out-of-pocket costs, time spent mitigating or significant psychological harm, which often raises individual issues at certification.
Does PIPEDA give individuals a right to sue for a data breach?
Not directly in most cases. PIPEDA requires organizations to report breaches creating a real risk of significant harm to the Privacy Commissioner and to notify affected individuals. Individuals can complain to the Commissioner and, after a report, seek a Federal Court remedy, but most class actions rely on common law and provincial claims.
Why are data breach class actions often filed in Quebec?
Quebec's authorization threshold under art. 575 of the Code of Civil Procedure is relatively low, its civil law framework differs from common law tort, and its private-sector privacy law, as amended by Law 25, includes breach obligations and a right to punitive damages for intentional or grossly negligent infringements.
What drives settlement values?
The sensitivity of the data, evidence of actual misuse, class size, the strength of remaining causes of action and the company's remediation. Many Canadian settlements combine a fund for documented losses, credit monitoring and court-approved class counsel fees.
Sources
- Supreme Court of Canada docket 40577 (Owsianik v. Equifax Canada Co., 2022 ONCA 813)
- Jones v. Tsige, 2012 ONCA 32
- Personal Information Protection and Electronic Documents Act, S.C. 2000, c. 5, s. 10.1
- Commission d'accès à l'information: main changes under Law 25
- Class Proceedings Act, 1992, S.O. 1992, c. 6
General information only, not legal advice. References to statutes, courts and authorities describe published law and practice at the date shown.


