productivityatlas.

Platform change / Retrospective

A two-party-consent law applies to a bot as much as a human

California's recording statute and the federal wiretap act show why a meeting assistant needs a consent policy, not just a toggle.

From the archive · Method record

Retrospective analysis prepared Sep 16, 2026. Not a hands-on review; historical plans and interfaces may differ from today's product.

What a two-party-consent statute actually requires

California's Penal Code section 632 makes it an offence to use an electronic recording device to record a confidential communication without the consent of all parties to it. A confidential communication is defined as one carried on in circumstances suggesting a party wants it confined to those present, which covers most private business calls and meetings that are not open sessions. The statute sets a first-offence penalty of a fine of up to $2,500, up to a year in county jail, or both, rising for a repeat violation. Federal law, at 18 U.S.C. section 2511, sets a lower bar: recording is not unlawful if the person recording is a party to the call or if one participant has consented, which is why this is described as one-party consent. Where a state statute like California's is stricter than the federal floor, the state rule controls for calls it covers.

What a meeting bot changes, and does not change

Products such as Zoom's AI Companion are described by the vendor as joining a meeting to take notes, summarise discussion and answer questions asked during the call. Functionally, an assistant that listens to a call in order to produce a transcript or summary is capturing the same confidential communication a human note-taker would capture with a recorder. The consent statute does not have a carve-out for software; it asks whether a communication was recorded and who consented, not what device or program did the recording. A host who enables an AI note-taker without telling other participants is in the same legal position as a host who presses record without telling them, in any jurisdiction that requires all-party consent.

What a team policy needs to cover

A policy that only says to get consent is not specific enough to follow consistently. It needs to say who is responsible for disclosure before a bot or recording starts, what the disclosure has to say, how external participants who are not employees are handled, and what happens when a meeting spans participants in different states or countries with different consent rules. It also needs a default: whether recording and AI note-taking are opt-in per meeting or a standing setting a host can leave on without thinking about it.

  • Does your meeting tool announce an AI assistant's presence clearly enough that every participant would notice it?
  • Who is responsible for knowing which consent rule applies when call participants are in different jurisdictions?
  • Does your policy treat a transcript-generating bot the same way it treats an audio recording?

The statute was written for tape recorders and now governs software that listens on a company's behalf; the obligation has not moved even though the technology has.

Source receipts

California Penal Code section 632 ↗

States California's requirement of consent from all parties before recording a confidential communication, and the penalties for violating it.

Source date: Undated / living document · Retrieved Sep 16, 2026

Zoom AI Companion ↗

Describes what a meeting assistant does when it joins a call to summarise and answer questions, the kind of automated participant the consent question applies to.

Source date: Undated / living document · Retrieved Sep 16, 2026