Law 25

Law 25 and your customer data: what your software vendor must guarantee

Are you having software built, bought, or rebuilt that holds information about your customers or employees? In Quebec, Law 25 places specific obligations on you, the business. Your vendor cannot meet them for you, but it must give you the means to meet them. Here is what the law says, section by section, and the eight guarantees to demand. This article summarizes the law; it is not legal advice.

What the law requires of your business

Law 25 amended the Act respecting the protection of personal information in the private sector. Its obligations came into force in three stages, in 2022, 2023, and 2024.

Law 25 obligations that affect a software project
Obligation Section In force since
Designate a person in charge of the protection of personal information (by default, the person with the highest authority), and publish their title and contact information on your website 3.1 September 22, 2022
When an incident presents a risk of serious injury, notify the Commission d'accès à l'information and the people concerned. Keep a register of all incidents 3.5 to 3.8 September 22, 2022
Adopt governance policies and publish detailed information about them, in clear terms, on your website 3.2 September 22, 2023
Conduct a privacy impact assessment (PIA) for any project to acquire, develop, or overhaul an information system 3.3 September 22, 2023
Before communicating information outside Quebec, conduct a PIA and sign a written agreement 17 September 22, 2023
Entrust in writing any mandate given to a vendor with access to the information, with the required protection measures 18.3 September 22, 2023
Set technological products or services offered to the public to the highest level of confidentiality by default 9.1 September 22, 2023
Destroy or anonymize information once the purpose for which it was collected has been achieved 23 September 22, 2023
At a person's request, provide their information in a structured, commonly used technological format 27 September 22, 2024

Act respecting the protection of personal information in the private sector (CQLR, c. P-39.1). Effective dates set out in section 175 of Law 25.

Your software project triggers a PIA

This is the obligation that affects a software project most directly. Section 3.3 requires a privacy impact assessment for any project to acquire, develop, or overhaul an information system or an electronic service delivery system that involves personal information. The Commission d'accès à l'information itself gives a members' area on a website and a mobile app as examples.

In practice:

  • The person in charge of privacy must be consulted from the start of the project, not at the end.
  • The assessment is proportionate to how sensitive the information is, how much of it there is, and how it will be used. A small internal tool does not require the same work as a public platform.
  • The law does not say how to do it, but the Commission publishes a free guide and a report template.
  • The system must be designed for portability: information collected from a person must be able to be given back to them in a structured, commonly used format (section 3.3, third paragraph).

The 8 guarantees to demand from your vendor

  • A written contract that spells out the protection measures. The law requires the mandate to be given in writing and to specify the measures the vendor must take: information used only for the mandate, and not kept afterward (s. 18.3).
  • The obligation to notify you without delay of any breach or attempted breach of confidentiality. It is a legal obligation of the vendor; write it into the contract anyway (s. 18.3).
  • Knowing where the data is. Hosting, backups, third-party services: ask where they are located. "Outside Quebec" includes the other provinces. If information is entrusted there, you need a PIA and a written agreement (s. 17).
  • Its cooperation on your PIA, from the start: a description of the data processed, how it flows, who has access, and the security measures.
  • Export in a structured format, such as CSV or JSON, to answer a portability request (ss. 3.3 and 27).
  • Deletion and anonymization, built into the software with retention periods, to comply with section 23.
  • Privacy by default for any service offered to the public: the most protective settings from the start, without the user having to turn them on (s. 9.1). And if the software locates or profiles people, it must inform them (s. 8.1).
  • Access logs. The law requires a register of incidents (s. 3.8). Without a log of who viewed what, you can neither detect an incident nor assess it.

What a business risks

The Commission can impose a monetary administrative penalty of up to $10,000,000 or 2% of worldwide turnover, whichever is greater (s. 90.12). Penal fines range from $15,000 to $25,000,000, or 4% of worldwide turnover (s. 91), and double for a repeat offence (s. 92.1). These are maximums; the real reason to comply is to protect your customers and your reputation.

Our take

Law 25 is not a reason to avoid software projects, but a reason to plan them properly. Ask every vendor these eight questions, including us. At AltaCodis, we have designated a person in charge of the protection of personal information (see our legal notice), and your software's hosting is chosen based on your requirements, in Quebec or in Canada if needed. To discuss it, write to us.

Sources

  1. LégisQuébec: Act respecting the protection of personal information in the private sector (CQLR, c. P-39.1), ss. 1, 3.1, 3.2, 3.3, 3.5 to 3.8, 8.1, 9.1, 10, 17, 18.3, 23, 27, 90.12, 91, and 92.1
  2. Publications du Québec: Law 25 (S.Q. 2021, c. 25), section 175, effective dates (PDF, in French)
  3. LégisQuébec: Regulation respecting confidentiality incidents (in French)
  4. Commission d'accès à l'information: person in charge of privacy and PIAs, with examples of systems covered (in French)
  5. Commission d'accès à l'information: use and communication of information, including outside Quebec (in French)
  6. Commission d'accès à l'information: guide to conducting a PIA (PDF, in French)
  7. Commission d'accès à l'information: penalties and proceedings (in French)

Sources checked on November 12, 2026. Programs and prices change, so always check the official page before you decide.

Common questions about Law 25 and software

Does Law 25 apply to small businesses?

Yes. The law covers personal information collected in the course of carrying on an enterprise (s. 1), regardless of size. Some obligations, such as governance policies, are however proportionate to the nature and scope of the business's activities (s. 3.2).

Do we need a PIA for a small internal tool?

If the tool is an information system that handles personal information, section 3.3 applies. The assessment is proportionate: for a small tool, it can be short.

Can I host my data in Ontario or the United States?

It is possible, but it counts as communicating information outside Quebec: you first need a PIA showing adequate protection, and a written agreement (s. 17).

Who is responsible if my vendor gets hacked?

The law applies to your information whether it is held by the business or by a third party (s. 1), and your business must take reasonable security measures (s. 10). Entrusting the data to a vendor does not relieve you of that responsibility, which is why the written contract and the duty to notify matter.

How quickly must the Commission be notified of an incident?

The law requires prompt notification, with no set deadline, when the incident presents a risk of serious injury.

A project that involves customer data?

Let's talk at the start, while it is still simple to build in the Law 25 requirements.