Internet Lawyer Blog
An AI meeting assistant can create a transcript, identify action items, and distribute a summary before participants return to their desks. Those conveniences also create legal questions about recording consent, confidential information, and control over the resulting records. California businesses should review these questions before allowing a meeting bot to join customer calls, employee interviews, or discussions with counsel.
The relevant analysis depends on what the tool actually does. Capturing audio, transmitting it to a vendor, generating text, and sharing a summary are separate activities. A meeting participant’s agreement to one activity may not address the others. A useful policy therefore explains the entire information flow and gives hosts a practical way to manage it.
Understand California Consent Requirements
California Penal Code section 632 generally prohibits intentionally recording or electronically eavesdropping on a confidential communication without every party’s consent. Confidentiality turns on the circumstances and reasonable expectations. A discussion does not have to involve a trade secret or intimate personal information to warrant analysis under the statute. Ordinary commercial conversations may involve a reasonable expectation against undisclosed recording.
The presence of a bot’s name on a participant list does not automatically resolve consent. People may not see the list, understand what the bot does, or know that a third party receives the audio. A transcription-only setting also deserves technical review. The absence of a saved audio file does not, by itself, answer whether the system recorded or electronically listened to the communication.
Address Calls Involving Participants Outside California
A meeting host should not assume that the law of the recording location always controls. In Kearney v. Salomon Smith Barney, Inc.(2006) 39 Cal.4th 95, the California Supreme Court examined calls between California clients and a Georgia brokerage office. The decision illustrates why an out-of-state recording practice can still implicate California privacy protections.
Identify where participants are located when that information is reasonably available. For recurring meetings involving several jurisdictions, obtain advice about a consistent consent procedure that accommodates the applicable rules. A vendor’s contract selecting another state’s law should not be treated as a complete answer to the rights of participants who never agreed to that contract.
Obtain Consent Before Activating the Tool
A practical workflow begins with advance notice in the meeting invitation and a clear explanation before capture starts. Identify whether the tool will record, transcribe, or summarize, and explain who will receive the results. Obtain and document participants’ agreement through an appropriate method. Written advance consent or an unrecorded consent exchange can help avoid beginning the recording before consent is obtained.
Plan for late arrivals and people joining by telephone. The host should know how to pause capture, explain the practice, and address an objection. Where appropriate, offer a meeting without the assistant or a different way to exchange information. Do not rely exclusively on a disclosure that appears only on a screen a dial-in participant cannot see.
Separate Recording Permission From Information Use
Consent to a meeting recording does not necessarily authorize training an unrelated model, publishing excerpts, or placing the transcript in a broadly accessible workspace. Review the vendor’s terms, account settings, and actual service configuration. Ask whether information is used to improve products, which subcontractors receive it, and whether different subscription plans provide different protections.
Consider a hypothetical sales discussion about a customer’s unreleased product. All participants may agree to a private transcript for preparing a proposal. Automatically sending the transcript to every account holder at the seller’s company could exceed the customer’s expectations and conflict with an existing confidentiality agreement. The intended audience should inform the tool’s distribution settings before the meeting begins.
Protect Privileged and Other Sensitive Conversations
Attorney-client discussions require a separate privilege assessment. Evidence Code section 952 recognizes certain disclosures to people assisting the consultation or reasonably necessary to transmit information or accomplish its purpose. That framework does not make every technology vendor an appropriate recipient of privileged material. Nor does using an outside tool invariably waive privilege. Purpose, access, confidentiality protections, and the surrounding facts matter.
Consult counsel before enabling an assistant for legal strategy, internal investigations, or similarly sensitive discussions. Establish which meetings require prior approval and which should proceed without a bot. The State Bar of California’s 2026 generative AI guidance also emphasizes confidentiality and meaningful lawyer oversight. Those professional duties are distinct from obtaining meeting participants’ consent to recording.
Review Privacy Notices and Retention Practices
Businesses subject to the CCPA should evaluate whether meeting data collection is accurately described in their notices and whether vendor contracts satisfy applicable requirements. Civil Code section 1798.100 addresses collection notices and limits on collection, use, and retention. Recording an entire conversation may capture substantially more personal information than the business needs to complete the underlying task.
Choose retention periods by record category and purpose. A final action list, raw audio, and an uncorrected transcript may serve different needs. Confirm how deletion works across the vendor’s system, integrations, and employee downloads. Apply legal holds when preservation is required. A routine deletion schedule should not continue unchecked after the business identifies a relevant dispute.
Check Accuracy Before Acting on a Summary
AI-generated minutes can omit qualifications, attribute a statement to the wrong speaker, or describe a tentative idea as a final commitment. Require an appropriate person to review consequential summaries before they become instructions, customer promises, or personnel records. Identify the summary as a draft when it has not been checked. Give participants a practical route for raising corrections.
For example, a discussion about possibly extending a project may become a summary stating that an extension was approved. If a manager relies on that summary to change billing, the error can spread into a contract dispute. Reviewers should compare important commitments against reliable source information and record corrections without silently replacing evidence relevant to an existing disagreement.
Set Access Controls and Assign Responsibility
Decide who may connect meeting assistants to company calendars, authorize integrations, and change sharing defaults. Limit access according to job responsibilities and review it when personnel leave or change roles. Test whether a bot can join meetings without the account owner being present. Check whether an automatically generated link permits access beyond the intended recipients.
Give hosts a short procedure they can actually follow. It should explain how to identify an unapproved bot, stop capture, obtain assistance, and report accidental disclosure. Periodically test the process using a fictional meeting. Vendor settings can change, and an old screenshot of a configuration does not establish how today’s meetings are being handled.
Respond Promptly to Recording Problems
An unexpected recording should trigger a documented review of what was captured, who received it, and what restrictions or notifications are appropriate. Preserve relevant evidence while limiting further distribution. Penal Code section 637.2 permits specified civil remedies for qualifying privacy violations, including statutory damages of $5,000 per violation or three times actual damages, whichever is greater. Liability depends on the claim and facts.
Our law firm assists businesses with AI policies, California privacy requirements, confidentiality agreements, and technology vendor contracts. We can review a proposed meeting-assistant workflow and help address recording disputes or unintended disclosures. Please contact our law firm to schedule a free initial consultation about using AI meeting tools responsibly in your business.