Skip to content
Cyberphore

Privacy law and breach response

Quebec Law 25 Checklist for Businesses Outside Quebec

A Law 25 compliance checklist for Ontario, BC and Alberta businesses with Quebec customers: when the act applies, what to do item by item, and PIPEDA overlap.

Published
Updated
Read time
8 min
On this page · 8 sections, 8 min read

If your business is based outside Quebec but collects personal information from Quebec residents, plan on Quebec's private sector act applying to that information. The Commission d'accès à l'information (CAI) says the act covers any business that collects, uses and communicates Quebecers' personal information, and no published decision has yet tested how far that reaches for an ordinary seller in another province. Most items on the checklist below can be applied to all your customers, so you can run one privacy program instead of two.

This is general information as of November 16, 2026, not legal advice. For background on the law, see our answer What is Quebec Law 25?, and for the CAI's penalty record and decisions, see Quebec Law 25 in 2026: what the CAI's enforcement shows. Neither is repeated here.

When the Quebec Act Likely Applies to You

The act applies to personal information that a person "collects, holds, uses or communicates to third persons in the course of carrying on an enterprise" (LégisQuébec, CQLR c P-39.1, s. 1). It does not contain a clause that sets its territorial reach. The CAI's position is broad: in a May 15, 2025 letter about 23andMe, a United States company, its president wrote that the act applies to any business that collects, uses and communicates the personal information of Quebecers (CAI, 2025).

The honest caveat: a letter is not a ruling. The CAI has used formal powers against a foreign company before: in December 2021 it ordered Clearview AI, a US facial recognition company, to stop collecting and using images of Quebecers and to destroy them (Gouvernement du Québec, 2021). That order was framed around Clearview carrying on an enterprise in Quebec, and it concerned mass collection of biometric data. We found no published decision applying the act to an ordinary seller based in another province, and enforcing an order against such a business would raise its own questions. Your exposure grows with your connection to Quebec. For example, a Calgary firm with staff working from Gatineau is in a different position from an Ontario web shop that ships an occasional order to Montreal. Both should assume the CAI considers them covered.

Two details in the law show it expects businesses outside Quebec. The CAI can formally demand documents from "any person, whether subject to this Act or not" (LégisQuébec, CQLR c P-39.1, s. 81.3). And an incident notice to the CAI must state how many affected people live in Quebec and whether a regulator outside Quebec was notified (LégisQuébec, CQLR c A-2.1, r. 3.1, s. 3).

How It Sits Alongside PIPEDA

Quebec, British Columbia and Alberta have private sector laws deemed substantially similar to PIPEDA. Even in those provinces, PIPEDA still applies to personal information transferred across borders, and the Office of the Privacy Commissioner (OPC) says more than one privacy law can apply to the same organization (OPC, 2020). An Ontario business with Quebec customers will usually be dealing with PIPEDA and the Quebec act at once; a BC or Alberta business may also have its own provincial act in the mix.

The practical differences show up most in breach handling:

Quebec private sector act PIPEDA
Reporting test Risk of serious injury (s. 3.5) Real risk of significant harm (OPC, 2025)
Who to notify CAI and the people concerned OPC, affected individuals and relevant third parties
Record of all incidents Yes, kept at least 5 years (r. 3.1, s. 8) Yes, kept 2 years (OPC, 2025)
5 years
Minimum time to keep the Quebec record of all confidentiality incidents
Source: r. 3.1, s. 8

Federal reform has not changed this yet. As of November 16, 2026, Bill C-36, which would amend PIPEDA, is at second reading in the House of Commons (LEGISinfo, 2026).

The Checklist, Item by Item

1. Name the Person in Charge and Publish Their Contact Details

By default, the person with the highest authority in the enterprise is the person in charge of the protection of personal information. They can delegate the function in writing, and the title and contact information must be published on your website (LégisQuébec, CQLR c P-39.1, s. 3.1). The CAI adds that the most senior person stays accountable after delegating, and that the CAI does not need to be told who holds the role (CAI, 2025).

  • Signed delegation letter, if the chief executive is not doing it
  • Title and a role mailbox (not a personal address) on the website

2. Adopt and Publish Governance Policies

You must establish governance policies covering the keeping and destruction of information, staff roles across the information's life cycle and a complaint process. They must be proportionate to your activities, approved by the person in charge, and described in clear language on your website (LégisQuébec, CQLR c P-39.1, s. 3.2). A 40 person firm does not need a binder; it needs a short, true document.

3. Keep an Incident Register and Know When to Report

Every confidentiality incident goes in the register: unauthorized access, use or communication, or loss (s. 3.6 and s. 3.8). When an incident presents a risk of serious injury, you must promptly notify the CAI and the people concerned, weighing the sensitivity of the data, the consequences of its use and the likelihood of misuse, and consulting your person in charge (s. 3.5 and s. 3.7). The regulation lists what the register must hold, including why you concluded there was or was not a risk of serious injury (r. 3.1, s. 7). The CAI is clear that you stay responsible when the incident happens at a supplier holding data for you (CAI, 2026).

  • One breach record with columns for both the Quebec and PIPEDA tests, kept five years
  • A field for the number of Quebec residents affected, since the CAI notice asks for it
  • Our privacy breach response guide wired into your incident plan
A Law 25 confidentiality incident register entry, completed step by step. Sample screen; data is illustrative.

4. Run Privacy Impact Assessments, Including for Transfers Out of Quebec

A privacy impact assessment (PIA) is required for any project to acquire, develop or overhaul an information system or electronic service delivery system involving personal information, with the person in charge consulted from the outset (s. 3.3). Before communicating personal information outside Quebec, or entrusting a person outside Quebec with collecting, using or keeping it for you, a PIA must consider sensitivity, purpose, protection measures and the destination's legal framework, and the transfer needs a written agreement reflecting the results (s. 17). The CAI's guide says that if the assessment finds protection would not be adequate, you must not send the data (CAI, 2024).

At collection you must tell people the purposes, the means of collection, their access and rectification rights, their right to withdraw consent and, if applicable, that their information could be communicated outside Quebec, in clear and simple language (s. 8). Anyone collecting through technological means must publish a confidentiality policy (s. 8.2). Consent must be clear, free, informed and given for specific purposes, requested for each purpose (separately from other information when in writing), and express for sensitive information (s. 12 and s. 14). The CAI reads section 14 as eight criteria and says organizations should document consent and what supports its validity (CAI, 2023).

6. Set Privacy by Default

If you offer the public a technological product or service with privacy settings, those settings must provide the highest level of confidentiality by default; browser cookie settings are excluded (s. 9.1). For a software or app company, this is a product backlog item, not a policy item.

7. Disclose Technology That Identifies, Locates or Profiles

If you use technology with functions that identify, locate or profile people, you must first tell them, and tell them how to activate those functions (s. 8.1). The CAI's reading is that such functions cannot be on by default (CAI, 2025). Review location tracking in apps, behavioural analytics and employee monitoring tools.

8. Give Notice of Automated Decisions

If a decision about a person is based exclusively on automated processing, you must tell them no later than when you tell them the decision. On request you must explain the information used, the reasons and principal factors, and their right to correction, and let them submit observations to a staff member who can review it (s. 12.1). Automated credit, pricing, fraud or hiring screens are the usual candidates.

9. Handle Access and Portability Requests

Since September 22, 2024, people can ask for computerized personal information collected from them in a structured, commonly used technological format, or have it sent to another authorized organization (CAI, 2025). The right excludes information you created or inferred (s. 27), and the CAI says it also excludes information obtained from third parties (CAI, 2025). The person in charge must answer in writing within 30 days, and silence counts as a refusal (s. 32).

10. Set Retention and Destruction Rules

When the purposes are achieved, you must destroy the information or anonymize it, subject to any legal retention period (s. 23). Information used to make a decision about a person must be kept for at least one year after the decision (s. 11). Anonymization has its own regulation: a qualified supervisor, a re-identification risk analysis and a register (LégisQuébec, CQLR c A-2.1, r. 0.1, ss. 4 to 9). If you cannot meet that bar, destroy rather than anonymize.

Where to Start

How Cyberphore Can Help

Cyberphore helps Canadian organizations work out which privacy laws apply to them and build the program behind them, including incident registers, PIAs for cloud and SaaS suppliers and breach response readiness. Our team holds industry certifications (CISSP, CISM, OSCP, GIAC and vendor certifications), and monitoring data stays in Canadian data centres by default. Learn more about our privacy compliance service.

Services for this topic

Share this article

Questions and Answers

Does Quebec Law 25 apply to an Ontario business that only sells online to Quebec residents?

The CAI's stated position is that the private sector act applies to any business that collects, uses and communicates Quebecers' personal information. The act itself has no clause setting its territorial reach, and we found no published decision applying it to an ordinary online seller in another province. Treat Quebec customers' data as covered and confirm your exposure with counsel.

Do we need a privacy impact assessment to store Quebec customer data with a US cloud provider?

Section 17 of the Quebec act requires a privacy impact assessment before communicating personal information outside Quebec, including when you entrust a provider outside Quebec with keeping it. The assessment looks at sensitivity, purpose, protection measures and the destination's legal framework, and the transfer must be covered by a written agreement that reflects the results.

If a breach affects customers in Quebec and Ontario, who do we report to?

Possibly both regulators. Quebec's act requires notice to the CAI and affected people when there is a risk of serious injury. PIPEDA requires a report to the Privacy Commissioner of Canada when there is a real risk of significant harm. Assess each test separately, record the incident in your register either way, and note in the CAI notice whether another regulator was told.

Who should be the person in charge of personal information in a small company?

By default it is the person with the highest authority in the business, usually the chief executive. That person can delegate the role in writing, in whole or in part, and the CAI recommends choosing someone with the right skills and real decision-making power. The title and contact details must be published on your website. The CAI does not need to be told.

Sources (13, primary and official first)

  1. Act respecting the protection of personal information in the private sector, CQLR c P-39.1 (up to date as of October 15, 2026) (opens in a new tab) · Ministère de la Justice du Québec (LégisQuébec),
  2. Regulation respecting confidentiality incidents, CQLR c A-2.1, r. 3.1 (up to date as of July 1, 2026) (opens in a new tab) · Ministère de la Justice du Québec (LégisQuébec),
  3. Regulation respecting the anonymization of personal information, CQLR c A-2.1, r. 0.1 (opens in a new tab) · Ministère de la Justice du Québec (LégisQuébec),
  4. Rappel de l'assujettissement de 23andMe à la Loi sur la protection des renseignements personnels dans le secteur privé (opens in a new tab) · Commission d'accès à l'information du Québec,
  5. La Commission ordonne à Clearview AI de cesser ses pratiques de reconnaissance faciale non conformes (opens in a new tab) · Commission d'accès à l'information du Québec (via Québec.ca),
  6. Responsabilité des renseignements personnels dans une entreprise (opens in a new tab) · Commission d'accès à l'information du Québec,
  7. Incidents de confidentialité et mesures de sécurité (entreprises) (opens in a new tab) · Commission d'accès à l'information du Québec,
  8. Réaliser une évaluation des facteurs relatifs à la vie privée: guide d'accompagnement, version 3.1 (opens in a new tab) · Commission d'accès à l'information du Québec,
  9. Principaux changements apportés par la Loi 25 (opens in a new tab) · Commission d'accès à l'information du Québec,
  10. Lignes directrices 2023-1: Consentement, critères de validité (opens in a new tab) · Commission d'accès à l'information du Québec,
  11. Provincial laws that may apply instead of PIPEDA (opens in a new tab) · Office of the Privacy Commissioner of Canada,
  12. What you need to know about mandatory reporting of breaches of security safeguards (opens in a new tab) · Office of the Privacy Commissioner of Canada,
  13. C-36: An Act to enact the Protecting Privacy and Consumer Data Act (opens in a new tab) · Parliament of Canada (LEGISinfo),

Changelog

  • Layout: callouts, a stat highlight and an in-body figure drawn from the existing text and sources (owner request for more visual articles); no content change.

General information for Canadian organizations, not legal advice.

Written by

Cyberphore Security Team

Certified security analysts and consultants

  • CISSP
  • CISM
  • OSCP
  • OSCE
  • GIAC GCIH
  • GIAC GCIA
  • GIAC GPEN
  • Microsoft SC-200

Articles are researched and written by Cyberphore's security team. Every team member, from analysts to leadership, holds industry certifications, and the team monitors and responds to threats for Canadian organizations 24/7/365. Every article is fact-checked against its sources and reviewed before publishing.

How we research, fact-check and update articles: editorial standards. Spotted an error? Email Use our contact form.

Incident happening now? Our team answers 24/7: +1 236 665 1165

Keep reading

Continue Reading

Book free assessment