Blog

Quebec's Law 25: a small and medium-sized business checklist, from policy to practice

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

You run a small or medium-sized business in Quebec or manage its systems, and you want to know what Law 25 concretely requires, then what to do about it on the IT side. This article takes the obligations described by the Commission d'accès à l'information du Québec (CAI) and turns them into verifiable tasks. It is not a substitute for legal advice or for the text of the law: if there is any discrepancy, the legislation prevails, and the CAI itself recommends consulting a lawyer who specializes in privacy and an information security specialist.

General information only; not legal advice. This article summarizes pages published by the Commission d'accès à l'information and does not take into account your business's specific situation. KTMA SOLUTIONS is not a law firm: for any decision that binds 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é, the "Private Sector Act," or "Loi sur le privé"). According to the CAI's checklist, its obligations came into force in stages: on September 22, 2022, September 22, 2023 and September 22, 2024. The main obligations introduced by Law 25 are therefore now in force. Their application nevertheless depends on the scope of the law, on the circumstances and on the exceptions provided by the applicable legislation.

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

A seven-point checklist

1. Designate and publish the person in charge of the protection of personal information

According to the CAI, the head or highest authority of the business is, by default, responsible for the protection of personal information. This function may 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 information of the person in charge on the business'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 website, that reaches someone even when the person in charge is away.

  • Person in charge designated, delegation recorded in writing
  • Title and contact information published on the website

2. Take an inventory of personal information

The CAI suggests, as an action to take, making an inventory of the personal information held by the business, or held on its behalf by a third party, and assessing its sensitivity. It specifies that this inventory is a living one and must be kept up to date, for example when information is newly 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), note: what information, for what purpose, who has access, where it is stored, and with which vendors it is shared.

  • 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 terms, on the business's website or, if it has no website, make it available by another appropriate means. According to the CAI, these policies must include, among other things, rules on retention and destruction, the roles of staff throughout the life cycle of the information, and a process for handling complaints. The person in charge approves these policies.

On the IT side, retention and destruction rules have to be turned into procedures that apply to systems, exports and backups: retention period by type of data, and effective 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 communication of personal information, or the loss of personal information, or any other compromise of the protection of personal information. Examples cited: a message sent to the wrong recipient or ransomware.

According to the CAI, as soon as the business has reason to believe that an incident has occurred, it must take reasonable measures to reduce the risk of harm and prevent a recurrence. It must assess the seriousness of the risk, taking into account the sensitivity of the information, the anticipated consequences and the likelihood of harmful use, in consultation with its person in charge. If the risk of serious harm is present, it must notify the Commission, in writing and using the prescribed form, as well as the individuals concerned.

The register: every business 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 of the circumstances;
  • the dates of the incident and of its discovery;
  • the number of individuals concerned (or an approximation);
  • the elements that justify the conclusion on the risk of serious harm;
  • the dates of the notices to the Commission and to the individuals;
  • the measures taken to reduce the risks.

It must be kept up to date, retained for at least five years after the business became aware of the incident, and sent 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 communicating information outside Quebec; for a project to acquire, develop or overhaul an information system or electronic service delivery system involving personal information; and before communicating information without consent for study, research or statistical purposes. Its scope 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 common: buying a tool or overhauling a system triggers the PIA at the start of the project. The CAI describes the basic tasks: assess compliance, identify risks, put in place measures to reduce them, then monitor and review them.

  • PIA built into the template for every system project
  • Risk-reduction measures followed up after go-live

Before collecting personal information, the business must assess whether the collection is necessary for the stated purpose: 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 terms; 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 informed of the third parties involved in the collection or communication and of the possibility that their information may be communicated outside Quebec. On request, other information must be provided to the person, including the retention period and the categories of people within the business 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 terms 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 protection, and that identification, location or profiling technologies may not be activated by default. For a decision based exclusively on automated processing, the business 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 observations 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. Individuals' rights: access, rectification, portability

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

Since September 22, 2024, an individual may ask that the computerized personal information collected from them, and not created or inferred from other personal information about them, be communicated 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 time limit manageable.

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

Service providers, cloud computing and outside Quebec

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

According to the CAI, communication to a service provider without consent is permitted if it is necessary for carrying 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 expires and allow the business to verify compliance with the applicable obligations. The mandatary must notify the person in charge of 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 communicating personal information outside Quebec, or entrusting an entity located outside Quebec with the task of collecting, using, communicating or retaining it on your behalf (a frequent 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 expiry, 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 the measures 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.

What non-compliance can cost

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

Frequently asked questions

Must every incident 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 communication may take place if adequate protection is demonstrated and a written agreement is in place.

Conclusion: where to start

Start with what the rest depends on: the published person in charge, then the inventory of information and vendors. Next, put in place the incident register and the procedure for access requests, then build the PIA into the launch of every system project. Have your texts 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