Territory 4 · Privacy duties
Client Consent for AI Meeting Recording in Canada: A Three-Layer Guide for Advisors
Recording a client meeting with an AI note-taker triggers three Canadian rules. The Criminal Code, PIPEDA and CIRO each ask a separate question.

Do I need client consent to record a meeting with AI in Canada?
Recording a client meeting with an AI note-taker engages three Canadian rules: two about consent and one about records. Criminal Code section 184 makes the recording lawful when one party consents. PIPEDA requires the client's meaningful consent to the collection, use, and AI processing of the personal information in the recording. Both apply on every recorded meeting, and CIRO's recordkeeping rules apply to the resulting records.
Canadian advisors often hear their country described as a "one-party consent" jurisdiction, meaning one participant in a conversation can lawfully record it without telling the other. That framing is accurate for the Criminal Code. It covers one layer of the stack. The Criminal Code addresses whether the recording itself is lawful. PIPEDA governs what the advisor can then do with the personal information the recording contains. CIRO's books-and-records rules apply once that information becomes a firm record. Each layer has its own statute and its own duties. Consent to record, under the Criminal Code, covers only that layer.
The three-layer consent stack every Canadian advisor needs to know
Three separate layers of Canadian law apply to a recorded AI-assisted client meeting. Northern Catalyst calls it the three-layer consent stack. This is a synthesis of the underlying law, rather than an official CIRO framework. Each layer has its own question, its own statute, and its own duty on the advisor.
- Layer 1: The act of recording. The Criminal Code governs whether the recording itself is lawful. Section 184(1) prohibits the interception of private communication; section 184(2)(a) creates a one-party consent exception when a participant in the communication agrees.
- Layer 2: The handling of personal information. PIPEDA governs what can be collected, used, disclosed, and processed, including by an AI tool. The client's consent must be meaningful under the OPC's Guidelines for obtaining meaningful consent (external site, opens in a new tab) (24 May 2018, issued with the Alberta and British Columbia commissioners), which set out elements the advisor should name up front.
- Layer 3: What the recording becomes once it enters the firm. CIRO's IDPC rules govern books-and-records, supervision, retention, and outsourcing obligations once the recording or the AI-generated summary becomes a firm record.
Layer 1
The act of recording
Is the recording itself lawful?
Statute
Criminal Code s. 184
Layer 2
The handling of personal information
Has the client meaningfully agreed to what we do with what we capture?
Statute
PIPEDA meaningful consent
Layer 3
What the record becomes
Does the record meet the firm's books-and-records standard?
Rules
CIRO IDPC 3800 and 3900
One consent does not cover three obligations.
Layer 01
Criminal Code section 184 and one-party consent
One-party consent in Canada means that one participant in a private communication can lawfully record it even where the other party has not been told. Criminal Code section 184(2)(a) creates this exception to the general rule in section 184(1). A CIRO-registered advisor who takes part in a client meeting is a participant for this purpose.
The Supreme Court considered the consent exception in Goldman v. The Queen (external site, opens in a new tab), [1980] 1 S.C.R. 976. The majority held that the consent of the originator or of the intended recipient may be express or implied, and that it must be voluntary.
Turning on an AI note-taker during a client call you are part of falls within section 184(2)(a) (external site, opens in a new tab): you are a party to the conversation, and your consent covers the interception. Every other consent question is still open. The exception follows the consent of a party to the conversation, not the hand that starts the recorder. What it does not reach, on its words, is conversation that takes place before you join, between people who have not agreed to be recorded. If someone else starts the recorder for you, have it started when you join, and take the edge cases to firm counsel.
A note on Duarte
Advisors who have heard of Canadian recording case law have usually heard of R. v. Duarte (external site, opens in a new tab) (1990). The case is often paraphrased as the Supreme Court saying judicial authorization is needed to record a private conversation. Duarte involved an undercover police officer; the Supreme Court held that state-actor recording engages section 8 of the Charter and requires prior judicial authorization. A financial advisor recording a client meeting is a private party. The Charter analysis in Duarte applies only to state actors.
A note on Fliss
In R. v. Fliss (external site, opens in a new tab), 2002 SCC 16, the trial judge had ruled a police recording and its transcript inadmissible. The Supreme Court held that the undercover officer could still testify to what he remembered of the conversation, and could refresh his memory from the transcript, though not recite it in full. Fliss is a criminal case about police evidence. It is cited here for one narrow point: a participant's own recollection of a conversation is evidence in its own right, separate from any recording of it.
Layer 02
PIPEDA meaningful consent for AI processing
PIPEDA requires meaningful consent before client personal information is collected, used, or disclosed, including when an AI tool processes it. The OPC's 2018 Meaningful Consent Guidelines name four key elements the advisor must cover up front: what information is collected, with whom it will be shared, the purposes, and the risks of harm.
The Criminal Code addresses whether the recording is lawful. PIPEDA governs what happens to the personal information inside the recording. These are separate consent questions, with separate standards.
The trigger stack
PIPEDA Principles 4.3.4 and 4.3.6 (external site, opens in a new tab) allow consent to be implied or express depending on the circumstances and the type of information. The OPC's Meaningful Consent Guidelines name three triggers that generally require express consent: sensitive information, collection or use outside reasonable expectations, or meaningful residual risk of significant harm. All three fire for advisor AI meeting recording.
What clients must be told
Meaningful consent under Principle 4.3.2 requires the client to receive the information in a form they can reasonably understand. The Guidelines name four elements the advisor must cover up front:
- What is collected. Audio of the meeting, a transcription, and any data derived from them.
- With whom it will be shared. The vendor, any sub-processors, and the geographic location of processing.
- Purposes. Summarization, CRM record creation, compliance documentation, and whether data trains the vendor's models.
- Risks. Inaccurate summaries in regulatory documentation, vendor retention, cross-border transmission, and residual harm from vendor breach.
Withdrawal, and the honest tension with CIRO retention
Principle 4.3.8 gives clients the right to withdraw consent at any time, subject to legal or contractual restrictions and reasonable notice. PIPEDA Case Summary #2003-249 (external site, opens in a new tab) held that informing a customer of the right is insufficient when the operational mechanism does not work. Applied to AI recording, that points to a withdrawal the advisor can carry out in practice: stopping mid-meeting on request, deleting the audio, the transcript, and anything the vendor derived from them, and confirming the deletion to the client.
A genuine tension sits between Principle 4.3.8 and CIRO recordkeeping. A client may withdraw consent after the meeting summary has become firm books-and-records material. The resolution is asymmetric: the regulated summary stays; the supporting AI artifacts come out. Firm counsel is the right place to confirm which records belong in which bucket.
Layer 03
CIRO supervision once the recording becomes a record
CIRO has not published a rule that prescribes a particular form of client consent for meeting recordings. Once the recording or an AI-generated summary enters the firm's books and records, CIRO recordkeeping, supervision, and retention rules apply. The consent itself sits under PIPEDA and, where applicable, Quebec Law 25, BC PIPA, or Alberta PIPA.
The four buckets
Bucket 01
Records
IDPC Rule 3800 / MFD Rule 5
Fires when
the audio, transcript, or summary becomes a firm record.
Bucket 02
Supervision
IDPC Rule 3900
Fires when
the record informs suitability, KYC, or trade instructions.
Bucket 03
Outsourcing
GN-2300-21-003
Fires when
the vendor contract is signed.
Bucket 04
Material change
CIRO's Compliance Report for 2026
Fires when
before the tool goes live.
The buckets fire at different moments
Records and supervision: first call. Outsourcing: contract signing. Material change: before go-live.
Records. An audio recording, a transcript, or an AI-generated summary becomes a firm record when its content relates to the firm's business or a client transaction. IDPC Rule 3800 is the books and records rule for investment dealers, and Rule 5 of the Mutual Fund Dealer Rules is its counterpart, with retention at Rule 5.6 (CIRO's Dealer Member Rules (external site, opens in a new tab)). A registered firm must keep its required records for seven years from the date the record is created (NI 31-103 (external site, opens in a new tab), s. 11.6(1)).
Supervision. Where a recording or summary informs a suitability decision, KYC update, or trade instruction, it joins the supervisory file under IDPC Rule 3900.
Outsourcing. Where an AI vendor performs a function for the dealer, CIRO's Guidance Note GN-2300-21-003, Outsourcing arrangements (external site, opens in a new tab), applies to investment dealers. It says the outsourced functions "should be set out in a written, legally binding contract", expects the dealer "to formally assess the initial and ongoing appropriateness of the outsource service provider", says the firm, its regulator, and its auditors "should have the same access to the work product of a third-party service provider as they would if the firm itself performed the activities", and says dealers "must, at a minimum, supervise the activities performed on their behalf". The dealer "retains the responsibility to ensure" that outsourced activities meet CIRO's rules and securities legislation.
Material change. Deploying a new AI tool may be a material change to the firm's business that calls for notice to CIRO. CIRO's Compliance Report for 2026 (external site, opens in a new tab) (Administrative Bulletin 26-0034, released 17 February 2026) says dealers "should also assess whether any use of AI and/or automation of its regulatory functions is a material business change thereby requiring advance written notification to CIRO and/or an update to firm registration information through filing a Form 33-109F5 Change of Registration Information."
What credible documentation looks like
CIRO's Re White (external site, opens in a new tab) (2024 CIRO 67) considered an advisor's handwritten notes. The panel found that the notes, combined with his oral testimony, "tip the balance strongly in favour of Mr. White's narrative" on one client (para. 125), having recorded that the notes stayed in the dealer's custody until the dealer produced them to CIRO (para. 97). What transfers to an AI workflow is the credibility architecture Northern Catalyst reads in the decision, by analogy rather than by holding. The architecture has three parts: contemporaneity, custody, and corroboration.
Where recording consent ends and processing consent begins
A common consent script in advisor practice is a single line at the start of the meeting: "I'm recording this, is that OK with you?" If the client says yes, the advisor moves on. That single yes handles one Canadian obligation. It does not handle the other.
Criminal Code s.184
Recording consent
PIPEDA Principle 4.3
Processing consent
One question covers recording. Another covers processing.
What differs when you cross the provincial line
The three-layer stack applies everywhere in Canada. What differs by province is whether additional obligations sit on top.
Alberta
Alberta's PIPA requires an organization that uses a service provider outside Canada to tell the individual, before or at the time the information is collected or transferred, how to obtain its policies about service providers outside Canada and whom to ask (Government of Alberta summary (external site, opens in a new tab)).
British Columbia
BC PIPA has no cross-border notice equivalent. The reasonable-person test governs whether collection, use, or disclosure is appropriate in the circumstances.
Quebec
Quebec's private-sector privacy Act (external site, opens in a new tab), as amended by Law 25, requires express consent to use sensitive personal information for a new purpose or to communicate it to a third party, and names biometric information as sensitive. Quebec's privacy regulator, the CAI, lists the voice (external site, opens in a new tab) among the characteristics biometric systems analyze. A tool that identifies speakers by voice needs a closer look: Quebec law (external site, opens in a new tab) requires express consent, and prior disclosure to the CAI, before identity is verified by biometric means.
Ontario
Ontario has no private-sector privacy statute equivalent to BC's or Alberta's. PIPEDA applies to commercial activity in Ontario directly.
When the client says yes to the meeting but no to the AI
Client responses cluster into three patterns: a clean no, a withdrawal partway through, and a yes-with-limits. Each has a different next move for the advisor.
If the client says no
If the client says no to the AI tool, the meeting proceeds without it. The client's refusal has no regulatory cost to them and leaves a complete record for the advisor, provided non-AI notes meet the contemporaneity, custody, and corroboration standard.
If the client withdraws consent partway through
If the client asks partway through to stop recording, the advisor stops. PIPEDA Principle 4.3.8 treats withdrawal as operational: the recording ends, and anything captured from that point forward is not retained.
If the client says yes to some but not all
If the client is comfortable with the advisor recording for note-taking purposes but not with the transcript going to a third-party AI vendor, the request is coherent under the two-consent structure. What the advisor cannot do is assume the first yes covers the second question.
Start
Meeting consent question
New client?
Script A
New client opening
Existing client?
Script B
Existing client, new tool
Already started talking?
Script C
Mid-meeting reset
Provincial check
Quebec client?
No
Standard variant
One yes for recording, processing and cross-border (where AB)
Bundled in one conversation.
Yes
Quebec variant
Three separate yeses
Recording, AI processing, cross-border. Put the request in writing as well.
- Decision: question to ask
- Script: what you say
- Variant: how to deliver it
What to say: practical consent scripts
The three-layer stack collapses in practice into a consent conversation that takes under a minute. The three scripts below handle new clients, existing clients starting to use an AI tool mid-relationship, and meetings where the question comes up after the conversation is already underway.
Each script has one bracketed line. Complete it from your own tool's terms before using the script, and check that every other sentence is true of the tool you use.
Script A: With a new client
Advisor
"Before we start, I'd like to tell you how I handle meeting notes. With your permission, I'd record this conversation and use an AI tool to help me write up a summary afterwards. It helps me stay present in the conversation, and the summary captures the detail accurately, which means less follow-up. The recording and the summary stay under my firm's control. [State, from your own tool's terms, what information goes to the AI provider and where it is processed.] You can ask me to stop recording at any time, or to delete what has been recorded. Would you like me to work that way, or would you prefer I take notes manually?"
Offer separate yes or no for recording, for AI processing, and for the cross-border disclosure, rather than bundling them into a single yes.
Script B: With an existing client
Advisor
"I wanted to tell you about something new in how I work. I've started using an AI tool that helps me write summaries of our meetings from a recording. It lets me focus more on our conversation and less on my screen. I kept typed notes before. If you prefer that, that is what we will do. With your permission, the recording and the summary stay under my firm's control. [State, from your own tool's terms, what information goes to the AI provider and where it is processed.] You can ask me to stop using the tool at any time."
Present the new practice in writing as well as verbally, and keep the three consents separate.
Script C: Mid-meeting
Advisor
"Before we go further, I want to mention something I should have covered at the start. I'd like to record our conversation and use an AI tool to help me write a summary afterwards. The recording and the summary stay under my firm's control. [State, from your own tool's terms, what information goes to the AI provider and where it is processed.] Two options: I can do that from this point forward, or I can stop the meeting here, send you a short written note about it, and we can restart when you've had time to consider. Either works for me."
The mid-meeting path is difficult to defend to the CAI. Default to the clean-start option and restart with a written consent request.
What to write down: the CRM audit trail
The record is what an examiner reconstructs. For AI meeting recording, ten categories of CRM fields together build the audit trail that shows consent was obtained, documented before processing began, and honoured through withdrawal and retention.
- Identity and versionConsent form version, Quebec client flag, AI tool version.
- Consent eventSeparate decisions for recording, AI processing, and cross-border disclosure.
- Meeting and processing timestampsIncluding whether consent was confirmed before processing began.
- Data location and routingPrimary storage region, inference routing jurisdictions.
- Withdrawal and partial consentScope of consent, scope of refusal, mid-meeting requests.
- Evidence artifactsSigned PDF, consent form template version, privacy policy version.
- Retention specificationSeven years from the date the record is created, for the records a registered firm must keep.
- Workflow integrationWhen each field is populated across the meeting lifecycle.
- Reconstruction bundleThe set of records you would hand a regulator to show what happened.
- Refusal and withdrawalWhat to document when a client declines or withdraws.
What US vendors tell you, and what they cannot
US AI vendors market to a landscape where wiretap law varies by state, privacy statutes are fragmented, and "no recording" can be a marketing advantage. None of those frames translate cleanly to Canada.
"No recording, no consent question"
Some AI vendors market products that process audio in real time without persisting a recording file. The framing implies that if no recording exists, no consent question arises. That framing does not hold in Canada. Criminal Code section 184 prohibits the interception of a private communication, and "intercept" is defined in section 183 to include listening to a communication, not only recording it.
Brewer v. Otter.ai and US litigation
Brewer v. Otter.ai (United States District Court, Northern District of California, filed August 2025; now In re Otter.AI Privacy Litigation, No. 25-cv-06911) is a class action alleging that Otter recorded meetings without all parties' consent. On 13 August 2026 the court let the federal and California wiretap claims and the Illinois biometric claims proceed and dismissed several other claims with leave to amend (the most recent ruling found as at 13 November 2026). United States wiretap statutes do not bind Canadian practice. The order (external site, opens in a new tab) shows that claims of this kind can pass the pleading stage in a United States court.
What to do with this
Three-layer consent looks heavier on paper than it has to feel in practice. A one-minute conversation at the start of the meeting, a written acknowledgement on file, and a CRM record that shows consent preceded processing are the working parts. Each layer of the stack carries its own regulator, but the advisor's daily handling is one conversation, one document, and one field in the CRM.
Approval of the tool itself is a separate conversation with the firm. The free Compliance Conversation Kit is built for it.
An advisor who builds the three-layer practice now has a consent record that stands on its own, whatever tool produced the notes.
The tool is optional. The record is not.
This is educational content based on published regulatory sources as at the page's last-updated date. It is not legal, compliance, or financial advice. Review specific compliance decisions with your compliance officer and qualified legal counsel before implementation.