Quebec Law 25: what the privacy law requires.
Law 25 rewrote Quebec’s private-sector privacy Act in three stages, from 2022 to 2024. Any enterprise that handles personal information in Quebec, whatever its size, must name a person in charge of privacy, publish its policies, assess new systems, report serious confidentiality incidents, ask for consent purpose by purpose, and answer access and portability requests. Penal fines reach $25,000,000 or 4% of worldwide turnover, whichever is greater.
Facts checked
What Law 25 is
“Law 25” is the usual name for Bill 64, An Act to modernize legislative provisions as regards the protection of personal information (2021, chapter 25), assented to on September 22, 2021. It is an amending Act. It changed several laws, chiefly the Act respecting the protection of personal information in the private sector (CQLR c P-39.1), which governs businesses, and the Act respecting Access to documents held by public bodies and the Protection of personal information (CQLR c A-2.1), which governs public bodies.
This page covers the private-sector Act. Section numbers are from that Act, read on LégisQuébec on 2026-11-10. Personal information is “any information which relates to a natural person and directly or indirectly allows that person to be identified” (section 2). The regulator is the Commission d’accès à l’information (CAI).
Who it applies to
Section 1: the Act covers personal information that a person “collects, holds, uses or communicates to third persons in the course of carrying on an enterprise within the meaning of article 1525 of the Civil Code.” Article 1525 is broad: an organized economic activity, “whether or not it is commercial in nature”, that produces, administers or alienates property, or provides a service. The test is the activity, not the legal form. The Act sets no threshold by size, revenue or volume of data.
It applies whether you keep the information yourself or through a third person, on any medium (section 1). Information about someone’s role at work, such as their name, title, work email and work phone, is outside the rules on collection and confidentiality (Divisions II and III).
| Situation | What applies |
|---|---|
| A business, non-profit or sole proprietor carrying on an enterprise in Quebec † † | The private-sector Act (P-39.1), as amended by Law 25 |
| A Quebec public body † | The public-sector Act (A-2.1), also amended by Law 25; the private-sector Act does not apply (section 3) |
| A federally regulated organization, such as a bank, airline or telecom † | PIPEDA, the federal Act, always applies |
| Personal information that crosses a provincial or national border † | PIPEDA applies to it, wherever the business is based |
† Competitor details come from each vendor’s own published pages on the dates shown; prices and plans change, so check the vendor before you decide. A business, non-profit or sole proprietor carrying on an enterprise in Quebec (2026-11-10) · A business, non-profit or sole proprietor carrying on an enterprise in Quebec (2026-11-10) · A Quebec public body (2026-11-10) · A federally regulated organization, such as a bank, airline or telecom (2026-11-10) · Personal information that crosses a provincial or national border (2026-11-10)
The obligations at a glance
Each row is a section of the private-sector Act, with the date Law 25 brought it into force (section 175 of Law 25). Some of these sections existed before in a shorter form; the date is when the Law 25 version took effect.
| Section | What it requires | In force |
|---|---|---|
| 3.1 † † | A person in charge of the protection of personal information, with title and contact information published on your website | Sept. 22, 2022 |
| 3.5–3.8 † † | Notify the CAI and the people concerned of a confidentiality incident that presents a risk of serious injury; keep a register of every incident | Sept. 22, 2022 |
| 3.2 † † | Governance policies and practices, approved by the person in charge and described on your website | Sept. 22, 2023 |
| 3.3, 17 † † | A privacy impact assessment for each new or overhauled information system, and before communicating personal information outside Quebec | Sept. 22, 2023 |
| 8, 8.1, 8.2 † † | Tell people why and how you collect; tell them first about technology that identifies, locates or profiles; publish a privacy policy | Sept. 22, 2023 |
| 9.1 † † | Privacy settings at the highest level of confidentiality by default | Sept. 22, 2023 |
| 12, 14 † † | Consent that is clear, free, informed and requested per purpose; express consent for sensitive information | Sept. 22, 2023 |
| 12.1 † † | Tell people when a decision about them is based exclusively on automated processing | Sept. 22, 2023 |
| 23 † † | Destroy or anonymize information once its purposes are achieved | Sept. 22, 2023 |
| 28.1 † † | Stop disseminating, or de-index, information on request in the cases the Act sets | Sept. 22, 2023 |
| 27 † † | Give people the information they provided in a structured, commonly used technological format | Sept. 22, 2024 |
† Competitor details come from each vendor’s own published pages on the dates shown; prices and plans change, so check the vendor before you decide. 3.1 (2026-11-10) · 3.1 (2026-11-10) · 3.5–3.8 (2026-11-10) · 3.5–3.8 (2026-11-10) · 3.2 (2026-11-10) · 3.2 (2026-11-10) · 3.3, 17 (2026-11-10) · 3.3, 17 (2026-11-10) · 8, 8.1, 8.2 (2026-11-10) · 8, 8.1, 8.2 (2026-11-10) · 9.1 (2026-11-10) · 9.1 (2026-11-10) · 12, 14 (2026-11-10) · 12, 14 (2026-11-10) · 12.1 (2026-11-10) · 12.1 (2026-11-10) · 23 (2026-11-10) · 23 (2026-11-10) · 28.1 (2026-11-10) · 28.1 (2026-11-10) · 27 (2026-11-10) · 27 (2026-11-10)
A person in charge of privacy (section 3.1)
By default, the person with the highest authority in the enterprise, usually the owner or chief executive, is the person in charge of the protection of personal information. They can delegate all or part of the function in writing to any person. The title and contact information of the person in charge must be published on the enterprise’s website, or made available by other appropriate means if there is no website.
The role is not a formality. The person in charge approves the governance policies (section 3.2), is consulted from the start of every privacy impact assessment (section 3.3) and on the risk of each confidentiality incident (section 3.7), and receives and answers access and rectification requests (sections 30 and 32).
Governance policies and a privacy policy (sections 3.2, 8 and 8.2)
Section 3.2 requires governance policies and practices that, in particular, frame the keeping and destruction of information, define staff roles and responsibilities through the information’s life cycle, and set a process for privacy complaints. They must be proportionate to the nature and scope of your activities and approved by the person in charge. Detailed information about them must be published on your website “in simple and clear language”.
Section 8.2 is a separate document: if you collect personal information through technological means, such as a web form or an app, you must publish a confidentiality policy in clear and simple language, and give notice of any change to it. Section 8 sets what you tell people when you collect: the purposes, the means, their rights of access and rectification, their right to withdraw consent and, if applicable, who you share with and the possibility that the information is communicated outside Quebec.
Privacy impact assessments (sections 3.3 and 17)
Section 3.3 requires a privacy impact assessment for “any project to acquire, develop or overhaul an information system or electronic service delivery system” that involves personal information. The person in charge is consulted from the outset. The assessment must be proportionate to the sensitivity of the information, the purposes, the quantity and distribution of the information and the medium it is stored on, so a contact form needs far less than a health record. The project must also let people get the information they provided in a structured, commonly used technological format.
Section 17 requires an assessment, and a written agreement that reflects it, before personal information is communicated outside Quebec, including when a provider outside Quebec keeps it for you. Law 25 and hosting covers section 17 in detail.
Confidentiality incidents (sections 3.5 to 3.8)
A confidentiality incident is access, use or communication of personal information not authorized by law, or its loss or any other breach of its protection (section 3.6). When you have cause to believe one has occurred, you must take reasonable measures to reduce the risk of injury and to prevent new incidents of the same kind (section 3.5).
If the incident presents a risk of serious injury, you must promptly notify the CAI and the people whose information is concerned (section 3.5). To assess that risk, consider the sensitivity of the information, the anticipated consequences of its use and the likelihood it will be used for injurious purposes, and consult the person in charge (section 3.7). Every incident, serious or not, goes in a register, and the CAI can ask for a copy (section 3.8). A government regulation may set the content of the notices and of the register; the Regulation respecting confidentiality incidents is listed with the Act on LégisQuébec.
Consent and sensitive information (sections 12, 13 and 14)
Consent must be “clear, free and informed and be given for specific purposes”. It is requested for each purpose in clear and simple language and, when requested in writing, “presented separately from any other information” (section 14). It is valid only for the time needed to achieve those purposes, and consent not given in line with the Act is without effect. For a minor under 14, consent comes from the person having parental authority or the tutor.
Information may be used only for the purposes it was collected for, unless the person consents or an exception in section 12 applies, such as a consistent purpose, fraud prevention or providing a service the person asked for. Commercial or philanthropic prospection is never a consistent purpose. Consent must be express for sensitive information: information that, because of its medical, biometric or otherwise intimate nature, or the context of its use or communication, “entails a high level of reasonable expectation of privacy” (section 12). The same rule applies to communicating it to a third person (section 13).
Privacy by default and tracking technology (sections 8.1 and 9.1)
If you offer the public a technological product or service with privacy settings, those settings must provide “the highest level of confidentiality by default, without any intervention by the person concerned” (section 9.1). Browser cookie settings are excluded.
If you collect information with technology that can identify, locate or profile a person, you must tell them first, and tell them how to activate those functions (section 8.1). Profiling means collecting and using personal information to assess characteristics such as work performance, economic situation, health, preferences, interests or behaviour. The CAI’s reading: these functions cannot be on by default. Law 25 for developers shows both rules as code.
Automated decisions (section 12.1)
If you use personal information to make a decision based exclusively on automated processing, you must tell the person no later than when you tell them the decision. On request, you must also tell them what personal information was used, the reasons and the principal factors and parameters behind the decision, and their right to have that information corrected. They must be able to submit observations to a member of staff who is in a position to review the decision.
Access, portability and de-indexation (sections 27, 28.1 and 32)
People can ask you to confirm whether you hold personal information about them and get a copy (section 27). Since September 22, 2024, computerized information collected from them, not created or inferred from it, must on request be given to them “in a structured, commonly used technological format”, unless that raises serious practical difficulties, and also to any person or body authorized by law to collect it. The person in charge must reply in writing within 30 days; no reply in that time is deemed a refusal (section 32).
Section 28.1 lets a person require you to stop disseminating their information, or to de-index a hyperlink attached to their name, when the dissemination breaks the law or a court order. They can also do so when it causes serious injury to their reputation or privacy that clearly outweighs the public’s interest in knowing, as long as the request goes no further than needed to stop the injury.
Destruction and anonymization (section 23)
When the purposes for which information was collected or used are achieved, you must destroy it, or anonymize it to use it for serious and legitimate purposes, subject to any retention period another Act sets. Anonymized has a strict meaning: it must be reasonably foreseeable at all times that the information “irreversibly no longer allows the person to be identified directly or indirectly”. Anonymization must follow generally accepted best practices and the criteria set by regulation; the Regulation respecting the anonymization of personal information is listed with the Act on LégisQuébec.
The three dates
Section 175 of Law 25 brought it into force in stages. A handful of provisions took effect on assent in 2021; the rest followed on these dates.
| Date | Main changes to the private-sector Act |
|---|---|
| September 22, 2022 † † | Person in charge (section 3.1); confidentiality incidents, notices and register (sections 3.5 to 3.8); communication without consent for a commercial transaction (section 18.4) and for research (section 21) |
| September 22, 2023 † † | Everything else: governance policies, privacy impact assessments, section 17, transparency and the privacy policy, consent, privacy by default, automated decisions, de-indexation, destruction and anonymization, and the new penalties |
| September 22, 2024 † † | Data portability (third paragraph of section 27) |
† Competitor details come from each vendor’s own published pages on the dates shown; prices and plans change, so check the vendor before you decide. September 22, 2022 (2026-11-10) · September 22, 2022 (2026-11-10) · September 22, 2023 (2026-11-10) · September 22, 2023 (2026-11-10) · September 22, 2024 (2026-11-10) · September 22, 2024 (2026-11-10)
Penalties
Since September 22, 2023, the CAI can impose administrative monetary penalties for failures such as not informing people as sections 7 and 8 require, collecting, using, communicating, keeping or destroying information in contravention of the law, not reporting an incident when required, not taking the security measures section 10 requires, and breaching the automated-decision rules (section 90.1). It has published a general framework for how it applies them (section 90.2).
| Mechanism | Who imposes it | Maximum for an enterprise |
|---|---|---|
| Administrative monetary penalty (sections 90.1 and 90.12) † † | A person designated by the CAI | $10,000,000 or 2% of worldwide turnover for the preceding fiscal year, whichever is greater |
| Penal fine (section 91) † | A court, on proceedings the CAI can institute (section 92) | $15,000 to $25,000,000 or 4% of worldwide turnover, whichever is greater; doubled for a subsequent offence (section 92.1) |
| Punitive damages (section 93.1) † | A court, when a person sues | At least $1,000, when an unlawful infringement causes injury and is intentional or results from gross fault |
† Competitor details come from each vendor’s own published pages on the dates shown; prices and plans change, so check the vendor before you decide. Administrative monetary penalty (sections 90.1 and 90.12) (2026-11-10) · Administrative monetary penalty (sections 90.1 and 90.12) (2026-11-10) · Penal fine (section 91) (2026-11-10) · Punitive damages (section 93.1) (2026-11-10)
What this means for hosting
Law 25 does not require Canadian servers. It requires a privacy impact assessment before personal information leaves Quebec, including to a host outside Quebec that keeps it for you (section 17); Law 25 and hosting walks through it.
Canner hosts in Montréal, so hosting on Canner does not trigger section 17 for the hosting itself. The section 3.3 assessment still applies to any new system, on any host.
Questions
Does Law 25 apply to small businesses?
Yes. The private-sector Act applies to anyone carrying on an enterprise within the meaning of article 1525 of the Civil Code, commercial or not, and sets no threshold by size, revenue or volume of data. Some obligations scale: governance policies are proportionate to the nature and scope of your activities (section 3.2), and assessments to the sensitivity of the information (section 3.3).
When did Law 25 come into force?
In three stages: September 22, 2022 (person in charge, confidentiality incidents), September 22, 2023 (most obligations and the penalties) and September 22, 2024 (data portability).
Who is the person in charge of the protection of personal information?
By default, the person with the highest authority in the enterprise. That person can delegate all or part of the function in writing to any person. The title and contact information must be published on your website (section 3.1).
Do I have to report every confidentiality incident?
No. You notify the CAI and the people concerned when an incident presents a risk of serious injury (section 3.5). You record every incident in your register, serious or not (section 3.8).
What are the fines under Law 25?
For an enterprise, administrative monetary penalties up to $10,000,000 or 2% of worldwide turnover (section 90.12), and penal fines from $15,000 to $25,000,000 or 4% of worldwide turnover (section 91), whichever is greater in each case. Courts also award punitive damages of at least $1,000 when an infringement is intentional or results from gross fault (section 93.1).
Is this legal advice?
No. It is our summary of the Act, with the sources linked. For a decision about your data, ask your person in charge of the protection of personal information or a lawyer.
Related
- GuideQuebec’s digital sovereignty statement
- BlogCanada's AWS Alternative — By Accident
- BlogWhy We Moved Canner Off a Fleet of Virtualized Servers and Onto Our Own Hardware
- BlogHow to Build a 100% Canadian Stack
- BlogA Weekend on the Wrong End of the Stack
- BlogShared Services Canada Wants a Sovereign Cloud. What Would That Actually Take?
Keep the hosting in Quebec.
Apps, Postgres, files and backups on Canner stay in Montréal. Start free.