Blog

Quebec Law 25: a compliance checklist for small and medium-sized businesses, from policy to practice

For organizations · By KTMA SOLUTIONS · Published · 12 min read

You own a small or medium-sized business in Quebec or manage its systems, and you want to understand what Law 25 actually requires and what to do about it on the IT side. This article takes the obligations described by the Commission d'accès à l'information (CAI), Quebec's privacy regulator, and turns them into verifiable tasks. It does not replace legal advice or the text of the law: if the two differ, the legislation prevails, and the CAI itself encourages you to consult a lawyer who specializes in privacy and an information security specialist.

General information only; this is not legal advice. This article summarizes pages published by the Commission d'accès à l'information and does not take into account your company's particular situation. KTMA SOLUTIONS is not a law firm: for any decision that commits you, consult a lawyer.

What Law 25 changes for a small or medium-sized business

Law 25 amends the Act respecting the protection of personal information in the private sector (Loi sur la protection des renseignements personnels dans le secteur privé, referred to here as the "Private Sector Act," or "Loi sur le privé"). According to the CAI's checklist, its obligations took effect in phases: on September 22, 2022, September 22, 2023 and September 22, 2024. The main obligations introduced by Law 25 are therefore in force today. How they apply, however, depends on the scope of the law, the circumstances and the exceptions set out in the applicable legislation.

What follows is presented as an obligation where the CAI states it as one, and as a best practice where it is a suggested action from the CAI or our own technical reading. The article covers Quebec private-sector law; other regimes may also apply if you serve customers elsewhere.

A seven-point checklist

1. Designate the person responsible for the protection of personal information and publish their contact details

According to the CAI, the head or highest authority of the company is responsible for the protection of personal information by default. This function can be delegated in writing, in whole or in part, but the head remains accountable and must provide the necessary resources.

Obligation: publish the title and contact details of the person responsible on the company's website (or, if there is no website, by another appropriate means).

On the IT side: set up a dedicated email address, visible on the site, that reaches someone even when the person responsible is out of the office.

  • Person responsible designated, delegation documented in writing
  • Title and contact details published on the site

2. Inventory your personal information

The CAI suggests, as an action to take, inventorying the personal information held by the company, or held for it by a third party, and assessing how sensitive it is. It specifies that this inventory is a living document that must be kept current, for example when new information is collected for a project.

This is the most technical step, and the one on which all the others depend. For each system (CRM, accounting, email, website forms), record: what information, for what purpose, who has access, where it is stored, and which vendors it is shared with.

  • Inventory by system and by vendor

3. Establish and publish governance policies

Obligation (since September 22, 2023, according to the CAI): establish and implement governance policies and practices for personal information, then publish detailed information about them, in plain and clear language, on the company's website or, if it has none, make it available by another appropriate means. According to the CAI, these policies must include, among other things, retention and destruction rules, the roles of staff throughout the life cycle of the information, and a process for handling complaints. The person responsible approves these policies.

On the IT side, retention and destruction rules must be translated into procedures that apply to systems, exports and backups: retention period by data type, and actual deletion or anonymization. The chosen strategy must comply with the applicable retention and destruction obligations and prevent information that must be destroyed from being reintroduced during a restore.

  • Applicable retention and destruction rules implemented in the systems
  • Complaints process described and published

4. Prepare for confidentiality incidents

The CAI defines an incident as unauthorized access to, use of or disclosure of personal information, or the loss of personal information, or any other breach of its protection. Examples it cites: a message sent to the wrong recipient or ransomware.

According to the CAI, as soon as the company has reason to believe an incident has occurred, it must take reasonable steps to reduce the risk of harm and prevent a recurrence. It must evaluate how serious the risk is, taking into account the sensitivity of the information, the anticipated consequences and the likelihood that it will be misused, in consultation with its person responsible. If the risk of harm is serious, it must notify the Commission, in writing and using the prescribed form, as well as the individuals concerned.

The register: every company must keep a register of all incidents involving personal information, including those that do not present a serious risk. According to the CAI, it contains in particular:

  • a description of the information and the circumstances;
  • the dates of the incident and of its discovery;
  • the number of individuals affected (or an approximation);
  • the elements that support the conclusion on the risk of serious harm;
  • the dates of the notices to the Commission and to the individuals;
  • the steps taken to reduce the risks.

It must be kept current, retained for at least five years after the company became aware of the incident, and provided to the Commission on request.

On the IT side: the CAI recommends an incident response plan and a directive for staff. In practice, you need to be able to answer "who, how many, what, when" quickly: retained access logs, a single point of contact for reporting, a register template ready to use.

  • Response plan and directive for staff
  • Enough logging to reconstruct the facts
  • Register in place, with the fields above, retained for five years

5. Conduct a PIA when the law requires it

A privacy impact assessment (PIA; in French, évaluation des facteurs relatifs à la vie privée, or EFVP) is required, according to the CAI, in three situations: before disclosing information outside Quebec; for a project to acquire, develop or overhaul an information system or electronic service involving personal information; and before disclosing information without consent for study, research or statistical purposes. Its scale must be proportionate to the sensitivity of the information, the purpose, the quantity, the distribution and the medium.

For an SME, the second case is the most frequent: buying a tool or overhauling a system triggers the PIA at the beginning of the project. The CAI describes the basic tasks: assess compliance, identify risks, put measures in place to reduce them, then monitor and review them.

  • PIA included in the template for every system project
  • Risk-reduction measures tracked after launch

Before collecting personal information, the company must evaluate whether the collection is necessary for the stated objective: consent is not enough to justify a collection that is not necessary. Obligations according to the CAI, where consent is required: obtain separate consent for each specific purpose, in plain and clear language; present the request for consent separately from other information when it is in writing; inform the person, at the time of collection, of the purposes and means of the collection, of their rights of access and rectification and of their right to withdraw consent. Depending on the applicable requirements, the person must also be told about the third parties involved in the collection or disclosure and about the possibility that their information may be disclosed outside Quebec. On request, other information must be provided to the person, including the retention period and the categories of people within the company who have access to the information. If you collect personal information by technological means such as a website, you must publish a privacy policy in plain and clear language and notify individuals of any changes.

The CAI adds that the default settings of a technological product or service offered to the public must provide the highest level of privacy, and that identification, location or profiling technologies may not be activated by default. For a decision based exclusively on automated processing, the company must inform the person concerned no later than when it communicates the decision to them. On request, it must also give them the personal information used, the reasons and the principal factors and parameters that led to the decision, and inform them of their right of rectification. It must give them the opportunity to submit their comments to a staff member who is in a position to review the decision.

On the IT side: one consent checkbox per purpose, not pre-checked, a time-stamped record, and a simple way to withdraw consent.

  • Consent per purpose, proof retained
  • Default settings at the most protective level

7. Individual rights: access, rectification, portability

According to the CAI, an individual can ask the person responsible, in writing, for access to their information or for its rectification if it is inaccurate, incomplete or equivocal. The person responsible must respond within 30 days of receipt; no response is equivalent to a refusal. Access is in principle free; fees may not exceed the cost of transcription, reproduction or transmission, and the company must state the approximate amount in advance.

Since September 22, 2024, an individual can ask that the computerized personal information collected from them, and not created or inferred from other personal information about them, be provided to them in a structured, commonly used technological format, unless this raises serious practical difficulties. The CAI suggests informing the team that maintains or develops your systems of this business need.

On the IT side: if an individual's information is scattered across several tools, responding within 30 days becomes a manual exercise. A single entry point, a search by individual and a structured export make that deadline achievable.

  • Procedure for receiving requests and tracking the 30-day deadline
  • Ability to find all of an individual's data
  • Export in a structured, commonly used format

Vendors, cloud services and outside Quebec

Entrusting information to a vendor does not discharge you of responsibility. The CAI is clear on this: when information is entrusted to a third party, the company remains responsible for its obligations in the event of an incident (measures, register, notices). An incident can occur at a vendor, and you need to account for that.

According to the CAI, disclosure to a service provider without consent is permitted if it is necessary to carry out the mandate or contract, entrusted in writing. The written contract must provide for the measures necessary to ensure the confidentiality of the information, limit its use to the scope of the mandate, prevent its retention after the mandate ends and allow the company to verify compliance with the applicable obligations. The mandatary must notify the person responsible for the protection of personal information without delay of any breach or attempted breach of the confidentiality obligations, and allow them to carry out any verification relating to that confidentiality.

Before disclosing personal information outside Quebec, or entrusting an entity located outside Quebec with the task of collecting, using, disclosing or retaining it on your behalf (a common case with cloud services), you must carry out the required PIA, demonstrate that the information will receive adequate protection and enter into a written agreement that meets the applicable requirements.

  • List of vendors that handle personal information
  • Written contract: confidentiality, limited use, destruction at expiration, incident notice
  • Location of processing and hosting known; PIA and written agreement if outside Quebec

Security: reasonable measures

The CAI calls for "reasonable" measures based on sensitivity, purpose, quantity, distribution and medium; the higher the risk, the more robust they must be. Its technical examples: strong passwords, encryption, firewalls, access logging, software updates, de-identification of data, secure destruction. On the administrative side: staff training and access limited to the people who need it.

The cost of non-compliance

According to the CAI, administrative monetary penalties can reach 10 million dollars or 2% of worldwide turnover. In the case of a penal offense, a company found guilty can be fined up to 25 million dollars or 4% of its worldwide turnover for the preceding fiscal year, whichever amount is higher. The amounts that apply depend on the nature of the breach and on the penalty regime involved.

Frequently asked questions

Does every incident have to be reported to the CAI? No: notice is required where there is a risk of serious harm, but every incident goes in the register.

Is a host located outside Quebec prohibited? That is not what the CAI says: the disclosure can take place if adequate protection is demonstrated and a written agreement is in place.

Conclusion: where to begin

Begin with what the rest depends on: publishing the title and contact details of the person responsible, then inventorying the information and vendors. Next, set up the incident register and the procedure for access requests, then build the PIA into the kickoff of every system project. Have your documents and practices reviewed by a lawyer and, if needed, consult the CAI.

KTMA SOLUTIONS services

KTMA Solutions Inc. does not provide legal advice.

Sources

Back to the blog · Blog RSS feed