By the LookTech Team
Under Law 25, every Quebec business is responsible for the personal information it holds. For an SMB, that means four concrete things: a designated person in charge, a register of confidentiality incidents, a privacy impact assessment (PIA) before any new system, and reasonable security measures, starting with access management.
Law 25, adopted in 2021, modernized Quebec’s Act respecting the protection of personal information in the private sector. Its obligations came into force in stages, from September 2022 to September 2024. Many SMBs updated their privacy policy, but not their security practices. That is often where the real risk lies: a booby-trapped email, a forgotten account, a fake wire transfer request.
This guide connects what the law requires with what your team can do this week.
What Law 25 actually requires from an SMB
A person in charge of the protection of personal information
Within a business, the person with the highest authority ensures the law is respected and, by default, acts as the person in charge of the protection of personal information. In an SMB, that is usually the president or general manager. The function can be delegated in writing, in whole or in part, to another person. The title and contact information of the person in charge must be published on the company’s website (section 3.1).
Policies, practices and security measures
The business must establish governance policies and practices proportionate to its activities: retention and destruction of information, staff roles and responsibilities, and complaint handling (section 3.2). It must also take security measures that are reasonable given the sensitivity, quantity and medium of the information (section 10). This is where compliance meets cybersecurity.
The confidentiality incident register
What is a confidentiality incident?
The law covers four situations (section 3.6): unauthorized access to personal information, unauthorized use, unauthorized communication, and its loss or any other breach of its protection. A stolen laptop with the client list, an email with statements sent to the wrong person, or a compromised mailbox are all common examples.
What the register must contain
Under the Regulation respecting confidentiality incidents, each entry describes, among other things:
- the personal information involved and the circumstances of the incident;
- the date or period of the incident and the date the business became aware of it;
- the number of people affected (or an estimate);
- the factors leading to the conclusion that there is, or is not, a risk of serious injury;
- the dates of any notices sent, and the measures taken to reduce the risk.
The register must be kept up to date and retained for at least five years after the business became aware of the incident. On request, a copy is sent to the Commission d’accès à l’information (CAI), Quebec’s privacy regulator.
The register is not only for serious incidents. According to the CAI, businesses must also record incidents that do not present a risk of serious injury. A register that stays empty for years usually means incidents are not being detected, not that they never happen.
When to notify the CAI and the people affected
If an incident presents a risk of serious injury, the business must promptly notify the CAI and the people whose information is involved (section 3.5). To assess that risk, it considers the sensitivity of the information, the anticipated consequences of its use and the likelihood it will be used for harmful purposes, and it consults its person in charge (section 3.7). In every case, it must take reasonable measures to reduce the risk and prevent a similar incident.
The PIA: before you buy, build or overhaul a system
A privacy impact assessment (in French, évaluation des facteurs relatifs à la vie privée, or ÉFVP) is mandatory for any project to acquire, develop or overhaul an information system or electronic service delivery involving personal information (section 3.3). The person in charge must be consulted from the start of the project. A PIA is also required before communicating personal information outside Quebec (section 17), which often applies to cloud software hosted elsewhere.
The good news: the assessment must be proportionate to the sensitivity, quantity and use of the information. For a new CRM or AI tool, an SMB should at least document what information is processed, where it is hosted, who can access it, how long it is kept, and what the vendor contract says. For more on adding tools, see our article on integrating AI with your existing tools.
Access management: the most cost-effective security measure
The law provides that, within a business, personal information is accessible only to people who need it to perform their duties (section 20). In practice, this is often the weak link in SMBs: shared accounts, former employees still active, everyone an administrator. A few simple measures go a long way:
- Named accounts: one account per person, never a shared password.
- Multi-factor authentication (MFA) on email, CRM, accounting and remote access.
- Need-to-know access: everyone sees what their role requires, nothing more.
- Quarterly access reviews, and accounts closed on an employee’s last day.
- Logging: keep a record of who views or exports sensitive data.
- Retention and destruction: delete or anonymize what is no longer needed, subject to retention periods set by law (section 23). Less data means less risk.
AI-powered fraud: phishing, voice deepfakes and CEO fraud
What AI changes
Fraudsters no longer need to write well: AI produces flawless emails in your company’s tone. It can also imitate a voice from a few public clips. CEO fraud, where a criminal poses as an executive or supplier to obtain a transfer or information, is described by the RCMP as one of the most financially damaging online crimes. The classic scenario: an “urgent and confidential” email or call from the president, or a notice that a supplier’s banking details have changed.
If a fraudster gets into a mailbox containing client or employee personal information, it is no longer just a financial loss: it is also a confidentiality incident to assess and record in the register.
Simple defences
- Every transfer or banking change request is confirmed through another channel, at a number you already know, never the one in the message.
- Dual approval for transfers above a threshold set by the business.
- An internal code word for urgent requests made by phone or video.
- A short training session twice a year, with recent phishing examples.
- A clear reflex: when in doubt, stop and report it to the person in charge.
Adopt a written rule: “no banking change and no urgent transfer without a call-back to a known number.” It costs nothing, and it defeats most CEO fraud, even when the voice on the phone sounds real.
A generic case: a 40-employee services SMB
Take a fictional professional services firm with 40 employees. It keeps client contact details and history in a cloud CRM, and employee files in payroll software. Its internal review reveals a common situation:
- the president is the person in charge by default, but nobody knows it, and her contact information is not on the website;
- three former employees still have CRM access;
- MFA is enabled on only half of the email accounts;
- there is no incident register, even though a laptop was lost last year;
- Excel exports of the client list circulate by email.
Within a month, without a major project, the firm delegates the function in writing to its operations director, publishes her contact information, closes unnecessary access, turns on MFA everywhere, opens a register (recording the lost laptop), and adopts the call-back rule for transfers. This is a generic example, not based on any real client.
Your 30-day starter plan
- Week 1: confirm or delegate in writing the person in charge, and publish their title and contact information on your website.
- Week 2: list the systems that hold personal information and who has access to them.
- Week 3: turn on MFA, close unnecessary accounts and put the call-back rule for transfers in place.
- Week 4: open the incident register, plan a simple PIA for your next software purchase and train your team.
Law 25 does not ask an SMB to have bank-level security. It asks it to know who is responsible, know where the information is, limit who can access it, record incidents and respond promptly. Most of these measures are about organization, not a big budget.
This article is general information, not legal advice. For your specific situation, consult a qualified legal advisor and the official resources of the Commission d’accès à l’information, including its page on confidentiality incidents (in French), and the official texts on LégisQuébec. On CEO fraud, see the RCMP; to report fraud, contact the Canadian Anti-Fraud Centre.
The LookTech diagnostic
Want to know where your personal information lives, who can access it and which measures to prioritize? The LookTech diagnostic reviews your tools (email, CRM, accounting, shared files), your access rights and your data flows, then gives you a clear prioritization and a roadmap. It does not replace legal advice, but it gives you a concrete view of your technical situation. For a broader starting point, also read AI for SMBs: where to start.
The diagnostic starts at $1,500. The scope is refined after a first conversation.
Discover the LookTech diagnostic, write to us, or call us at +1 438 800 7272.