·
12 minute read
·
By
Yes. Recording a client meeting with AI is legal in Canada when your client knows and agrees, and the tool meets your privacy-law duties. Criminal law lets a participant record a conversation. Privacy law is what governs you as a business. You tell the client what you record and why, you get their consent, and you protect what you keep. The catch is the AI tool. It's part of what the client agrees to.
On average, I speak with a hundred Canadian financial and insurance advisors every month. When the talk turns to recording, three questions come first: whether the client has to be told, where the recording goes, and whether it trains someone's AI. This guide answers all three, with the rules checked on the regulators' and legislators' own pages on 6 November 2026.
Is it legal to record client meetings with AI in Canada?
It's legal in Canada to record a client meeting with AI, as long as your client knows and agrees and the tool meets your privacy-law duties. Two sets of rules apply. The Criminal Code makes it an offence to intercept a private communication, but not for someone who has the consent of one of the parties. Recording your own meeting isn't a crime. Privacy law goes further. Under the Personal Information Protection and Electronic Documents Act (PIPEDA), you need your client's consent, as a rule, to collect, use or disclose their personal information. The Office of the Privacy Commissioner of Canada (OPC) says financial information is generally sensitive, which generally calls for express consent. In Québec, Law 25 adds stricter consent rules and generally an assessment before you adopt the tool (section 3.3). So the one-party rule keeps you out of criminal court. It doesn't let you record a client who wasn't told.
Criminal law. Section 184 of the Criminal Code covers intercepting private communications. One party's consent is enough, and you're a party to your own meeting. That's the part people quote. For an advisor, it's only the start.
Privacy law. You collect your clients' personal information as a business, so privacy law applies. Under PIPEDA, the client's knowledge and consent are required to collect, use or disclose their personal information, except where inappropriate, such as fraud prevention or law enforcement (Principle 4.3). You also identify your purposes at or before the time you collect it (Principle 4.2).
Financial information raises the bar. The OPC's guidelines for obtaining meaningful consent say financial information will generally be considered sensitive, and that sensitive information generally calls for express consent. A sign on the wall is unlikely to be enough for information this sensitive. Ask, and get a clear yes.
Which privacy law applies depends on where your practice is based. The OPC says Alberta, British Columbia and Québec have private sector privacy laws deemed substantially similar to PIPEDA. In many cases, the provincial law applies instead. When more than one applies, you comply with both.
Where your practice is based | Main private sector privacy law |
|---|---|
Other provinces and the territories | PIPEDA (federal) |
Alberta | Personal Information Protection Act (PIPA) |
British Columbia | Personal Information Protection Act (PIPA) |
Québec | Act respecting the protection of personal information in the private sector, as amended by Law 25 |
PIPEDA still applies in Alberta, British Columbia and Québec when personal information crosses provincial or national borders, and to federally regulated businesses such as banks. All of these laws are built on consent. Québec's adds specific steps of its own, so it gets its own section below.
What do you have to tell clients before you record?
Tell them the four things the OPC asks organizations to make clear: what you collect, who you share it with, why, and the risk of harm. For an AI recording, that means:
What: the audio of the meeting, the transcript, and the notes made from it.
Who: the AI tool that processes it, and where that company stores it.
Why: to document the meeting, prepare the follow-up and keep their file current.
Protection: how the recording is kept secure, and who can access it.
It also helps to say how long you keep the recording, and what you keep after it's deleted.
The second point matters more than it looks. Your client agrees to more than you listening back: a company they may not know will handle their voice and their numbers. It helps to name it.
Consent covers the purposes you named when you asked. Using the recording for a new purpose generally needs new consent (PIPEDA Principle 4.2.4). In Québec, section 12 allows a few exceptions, such as a purpose consistent with the original one.
What consent process should an AI note taker have?
A good AI note taker makes consent part of the record, not a checkbox you tick once. You're the one who asks the client. The tool's job is to make asking easy, remember the answer, and act on it. Expect six things:
It asks before the meeting, not after. The client hears about the recording before it starts: in the invitation, or in a consent email sent ahead of the meeting. Ideally you choose how far ahead that email goes out. Then ask again at the start, so the answer is on the record: "I record our meetings with an AI tool so my notes are complete. It's stored in [where the tool stores it]. Are you comfortable with that?" If a spouse or another advisor joins, ask each person. A line in a privacy notice signed two years ago is unlikely to be enough on its own.
Consent is set per client. One client is fine with recording. Another wants it off, and that's their call: take notes by hand, no reason needed. The tool should let you turn capture off for one relationship without touching the others.
Your practice picks the method. Some advisors announce recording out loud. Some collect express consent at onboarding. The tool should fit how you work, not the other way around.
Withdrawing is as easy as agreeing. When a client asks you to stop, you change the setting for that relationship and it applies from the next meeting. No support ticket.
The consent is saved with the meeting. Each recording shows when consent was given, how, and with which tool. A reviewer reading the file years from now should find it next to the notes.
It works wherever you meet. Online calls, in person and phone calls each need their own way of telling the client. Ask how the tool handles all three.
Here's what that looks like in one tool. Bloks, which publishes this blog, sends clients a consent email ahead of each meeting, and the advisor sets how far ahead, from 3 to 24 hours. Hold any tool you're considering, ours included, to the six points above.
What does Law 25 change in Québec?
Law 25 makes consent stricter and adds paperwork before you start. It amended Québec's Act respecting the protection of personal information in the private sector, and three of its sections matter for recording.
Consent has to be clear, free and informed and given for specific purposes (section 14). It's requested for each purpose, in clear and simple language, and it lasts only as long as needed for that purpose.
A privacy impact assessment comes first for any project to acquire or overhaul an information system that handles personal information (section 3.3). Adding an AI meeting tool to your practice is likely to be one. The assessment can be proportionate to how sensitive the information is, why you use it, how much of it there is and where it's stored.
Data leaving Québec needs an assessment first (section 17). The information can be communicated if the assessment shows it would be adequately protected, and the communication must be covered by a written agreement. That includes entrusting a vendor outside Québec with collecting, using, communicating or keeping the data on your behalf. Outside Québec means the rest of Canada too, not only the United States.
That last one surprises people. A tool hosted in Ontario or Alberta still triggers section 17 for a Québec practice. The Commission d'accès à l'information summarizes the main changes in French.
Québec's Civil Code applies too. Nobody's privacy may be invaded without their consent or authorization by law, and intentionally intercepting or using someone's private communications, or appropriating or using their image or voice while they're in private premises, may be considered an invasion of privacy (Civil Code of Québec, articles 35 and 36). One more reason to ask before you record.
Is it safe to use AI note takers for confidential client meetings?
It can be, and a practical test is whether the vendor answers five questions in writing. They cover storage, the AI model behind the tool, training, retention and the SOC 2 Type 2 report. In my view, safety here is less a feature than what the contract says about where your client's words go.
Under PIPEDA, storing data outside Canada isn't forbidden. The OPC's guidelines on processing across borders treat it as a use of the data, not a disclosure. You stay accountable for it, and you protect it by contract. You also tell clients it may be processed in another country, where that country's courts, law enforcement and national security authorities may be able to access it. That's legal. It's one more thing to mention when you ask for consent. Alberta's private sector privacy law adds its own rules: an organization that uses a service provider outside Canada must name the countries involved in its policies, and tell individuals how to get that information and who can answer their questions (Personal Information Protection Act, ss. 6 and 13.1). British Columbia's private sector law has no rule specific to cross-border processing, but you stay responsible for information under your control and must protect it with reasonable security arrangements (Personal Information Protection Act, ss. 4 and 34).
Ask any vendor these five questions before your first client meeting:
Ask | A good answer | Dig deeper if |
|---|---|---|
Where are recordings and transcripts stored? | A named country, in the contract | "In the cloud", with no country |
Which AI model provider processes the audio? | Named, with its own retention and training terms | They can't or won't name it |
Is any of my data used to train a model? | No, written into the contract or data processing agreement | It's only on the marketing page, or it's an opt-out you have to find |
How long is a recording kept, and can I delete one? | You set the retention, and deletion on request works | Kept indefinitely, no way to delete |
Can I see the SOC 2 Type 2 report? | Yes, the report itself | Only a badge on the website |
A SOC 2 Type 2 report covers how the vendor's controls are designed and whether they actually worked. A Type 1 covers design only. Read the scope too: the report should cover the product you're buying. The compliance guide to AI note takers goes through SOC 2, PIPEDA and Canadian data residency in more detail.
Which AI meeting tools don't use your data to train their models?
The ones that commit to it in the contract. A "we don't train on your data" line on a website is a good start, but the contract is what binds the vendor, and it should cover the AI model behind the tool too. This guide doesn't rank tools: a list dates fast, and the contract is what counts. Check two places.
The vendor's own terms. Look for the no-training commitment in the terms of service or the data processing agreement, not only the FAQ. The clearest version says your content won't be used to train or improve any model, the vendor's or its suppliers'. A setting you have to switch off is weaker than a clause in the contract.
The model behind the tool. The tool may send your audio or transcript to a large language model run by another company. Ask which one, and whether that company keeps or trains on what it receives. The vendor's promise is only as strong as its supplier's terms.
Canada's privacy regulators set out their expectations in their principles for generative AI, released in December 2023. They say everyone involved should limit the personal information used to train AI tools to what's necessary. Developers and providers should tell users when personal information from prompts is used for further training. For organizations using these tools, prompts should not be retained, used for secondary purposes or disclosed, unless otherwise required. That's the bar to hold a vendor to.
How do you use AI without getting in trouble with regulators?
Use it the way you'd use any other system: you stay responsible for what it does. The Canadian Securities Administrators say securities laws are generally technology-neutral (CSA Staff Notice and Consultation 11-348, December 2024). Registrants stay responsible and accountable for anything they outsource to a service provider. The same notice says AI systems used by registrants should be explainable enough for firms to meet their record-keeping requirements.
The Canadian Investment Regulatory Organization (CIRO) is watching too. Its 2026 compliance report says CIRO will ask dealers about their use of AI in its financial and operations examinations. Where they use it, CIRO will review the operational controls in place to make sure it works as designed. That review lands on your dealer, which is why your dealer has a say in which tools you use.
If you only sell insurance, your conduct rules come from your provincial insurance regulator, such as the Autorité des marchés financiers (AMF) in Québec. Your managing general agency (MGA) and the insurers you place business with may add their own. Privacy law applies either way.
Three habits keep you out of trouble:
Use the tools your dealer or MGA approves. In November, an advisor told me that their compliance team hadn't banned Copilot. It had been very clear, though, that client data can't end up saved in the wrong place. That's the right line. A general AI assistant isn't the same as a tool vetted for client data.
Read before it becomes the record. An AI note is a draft until you approve it. The record is still yours, and so is any mistake in it.
Keep the consent with the file. A reviewer should find the consent next to the meeting it covers. What to document after a meeting, under CIRO's rules and NI 31-103, is in this guide to documenting client meetings.
What happens to the recording after the meeting?
Decide that before your first client asks. In October, an advisor asked me what happens to the recordings if a client leaves and wants them deleted. It's a fair question, and it pulls two ways.
Privacy law says personal information you no longer need for its purpose should be destroyed, erased or made anonymous (PIPEDA Principle 4.5.3). In Québec, it must be destroyed, or anonymized to be used for serious and legitimate purposes, subject to any preservation period provided for by law (section 23).
Securities law pulls the other way. Under National Instrument 31-103 (NI 31-103), a registered firm keeps the records it's required to keep for 7 years from the date each record is created (section 11.6). The copy the OSC posts is a September 2023 consolidation. Whether the raw recording is one of those records, the rule doesn't say outright. It requires records that document correspondence with clients (section 11.5). Ask your dealer how it treats recordings. If you sell insurance, ask your MGA.
One workable setup: the approved notes stay in the client file for the full retention period. The audio is kept for a shorter, stated period. Whatever you choose, mention it when you ask for consent and make sure the tool can actually do it. Check it with your compliance team before you promise anything.
What are the limits?
AI gets things wrong. It can mishear a name, a number or an account type, so nothing it writes should reach the file until you've read it.
A recording also cuts both ways. One advisor put it well in a demo: a complete record protects you, and it can also show your mistakes. That's not a reason to avoid it. It's a reason to review what goes in the file.
This guide isn't legal advice. It covers the federal rules and Québec in detail, and Alberta's and British Columbia's laws only briefly. Your dealer or MGA may also set stricter rules than the law. Check both with your compliance team.
One more limit worth naming: mine. I'm Head of Advisor Growth at Bloks, which builds an Un-CRM that records client meetings, so I'm not neutral on this question. That's why this guide sticks to what the law says and what to ask any vendor. Hold every vendor to those five questions, us included.
Tell your client first, and the rest follows.
- Criminal Code, section 184
- PIPEDA, Schedule 1
- Office of the Privacy Commissioner of Canada, Guidelines for obtaining meaningful consent
- Office of the Privacy Commissioner of Canada, Guidelines for processing personal data across borders
- Office of the Privacy Commissioner of Canada, Provincial laws that may apply instead of PIPEDA
- Act respecting the protection of personal information in the private sector (Québec)
- Commission d'accès à l'information du Québec, Law 25
- Principles for responsible, trustworthy and privacy-protective generative AI technologies (December 2023)
- CSA Staff Notice and Consultation 11-348 (December 2024)
- CIRO Compliance Report 2026
- National Instrument 31-103, OSC unofficial consolidation
Frequently asked questions
As a business, you generally need your client's informed consent to record a meeting in Canada, under PIPEDA, Alberta's or British Columbia's privacy act, or Québec's private sector act. Under the Criminal Code alone, the consent of one party to the conversation is enough, but that doesn't cover your privacy-law duties. Your client can also say no: take notes by hand and note the refusal in the file.
Whether it's safe to use AI note takers for confidential client meetings comes down, in practice, to five answers the vendor should put in writing: where recordings are stored, which AI model provider processes them, whether any data trains a model, how long recordings are kept, and whether you can see its SOC 2 Type 2 report.
Whether AI meeting tools train on your client data depends on the vendor. The most reliable answer is a no-training clause in the terms of service or data processing agreement, and it should cover the AI model provider behind the tool too.
Law 25 applies if your practice is in Québec and the recording is stored in Ontario. Section 17 covers personal information communicated outside Québec, including to the rest of Canada. It calls for a privacy impact assessment first; the information may then be communicated if the assessment establishes that it would be adequately protected, and the communication must be covered by a written agreement with the vendor.
Keep reading
Every client, your only client.
The person across from you won’t know why. They’ll just feel it.
No setup, no training, and a dedicated team walking you through it if you want one. Encrypted at rest and in transit. You own your data.
