Tennessee AI Meeting Recording Laws (2026)
Tennessee's recording laws give broad latitude to individuals who want to record their own conversations. Under Tenn. Code Ann. § 39-13-601, anyone who is a party to a wire, oral, or electronic communication may record it without the knowledge of the other participants. That one-party consent framework extends to AI-powered meeting recording tools, which are increasingly common in Tennessee workplaces from Memphis to Nashville to Knoxville.
But Tennessee's statute was written decades before AI notetakers existed. The growing use of tools like Otter.ai, Fireflies.ai, and Zoom AI Companion raises questions that the legislature has not yet addressed directly. When an AI bot joins a meeting on your behalf, who is the "party" providing consent? What happens when the tool scrapes your calendar and auto-joins without explicit per-meeting authorization? These are the legal fault lines that Tennessee professionals need to understand.
Tennessee's One-Party Consent Framework
The Core Statute: § 39-13-601
Tenn. Code Ann. § 39-13-601 makes it a criminal offense to "intentionally intercept, endeavor to intercept, or procure any other person to intercept any wire, oral, or electronic communication." The statute covers phone calls, in-person conversations, and electronic communications transmitted via digital platforms.
The critical exception is consent. Under § 39-13-601(b)(5), it is lawful for a person to intercept a wire, oral, or electronic communication "where such person is a party to the communication or where one of the parties to the communication has given prior consent to such interception." This is Tennessee's one-party consent rule.
The statute also includes a criminal or tortious purpose exception. Recording is only lawful if the person making the recording is not doing so "for the purpose of committing any criminal or tortious act." An employer who records meetings to build a pretextual case for retaliatory termination, for example, could lose the protection of the one-party consent exception.
Interaction with Federal Law
Federal wiretapping law under 18 U.S.C. § 2511 also follows a one-party consent standard. A person who is a party to a communication, or who has consent from one party, may lawfully intercept it under federal law. This creates consistency for Tennessee-based recordings: a recording that complies with § 39-13-601 will also comply with the federal wiretap statute.
The alignment breaks down in cross-state scenarios. If a Tennessee participant records a call with someone in California, Florida, or Illinois, the stricter all-party consent law of that state may apply. Federal law sets the floor, not the ceiling.
How Tennessee Law Applies to AI Meeting Recorders
The Consent Analysis
When a Tennessee-based participant activates an AI meeting recorder, that participant provides the one-party consent required under § 39-13-601(b)(5). The participant is a party to the communication and has consented to the interception. Tennessee's statute does not require the consenting party to personally operate the recording device; it requires only that a party has given prior consent.
This means the human user's activation of an AI tool like Otter.ai or Fireflies.ai satisfies Tennessee's wiretapping statute. The AI tool functions as an instrument of the consenting party, not as an independent third party.
Auto-Join Features and Consent Gaps
The riskiest scenario under Tennessee law involves AI tools that auto-join meetings from calendar data without explicit per-meeting authorization. If an AI notetaker scrapes a user's calendar and joins meetings autonomously, the question becomes whether the user's general account authorization constitutes "prior consent" for each individual recording.
Tennessee's statute requires that consent be given "prior to" the interception. A conservative reading suggests that consent should be specific to each communication rather than given as a blanket authorization. The Brewer v. Otter.ai class action filed in August 2025 in California federal court alleges that Otter's auto-join features recorded conversations without proper consent from any meeting participant, including the host.
The National Litigation Landscape
Brewer v. Otter.ai (N.D. Cal., 2025)
The Otter.ai class action, filed in August 2025, alleges that Otter's notetaking tools recorded private Zoom conversations without obtaining consent from all participants. The plaintiff, who did not have an Otter account, participated in a meeting where Otter Notetaker was used. The complaint asserts violations of the Electronic Communications Privacy Act (ECPA), the Computer Fraud and Abuse Act (CFAA), and the California Invasion of Privacy Act (CIPA).
For Tennessee users, the key takeaway is the auto-join allegation: the lawsuit claims that when a meeting host has integrated Otter with their calendar, the Otter Notetaker may join meetings "without obtaining the affirmative consent from any meeting participant, including the host."
Ambriz v. Google (N.D. Cal., 2025)
In February 2025, a federal court denied Google's motion to dismiss in Ambriz v. Google LLC, a class action alleging that Google's Cloud Contact Center AI violated the California Invasion of Privacy Act. The court adopted the "capability test," holding that an AI vendor need only possess the technical capability to use intercepted data for its own purposes (such as model training) to be considered a third-party eavesdropper.
Popular AI Meeting Tools and Tennessee Compliance
| Tool | How It Records | Tennessee Compliance Notes |
|---|---|---|
| Otter.ai | Bot joins meeting as participant | One-party consent satisfied by participant activation; auto-join creates risk |
| Fireflies.ai | Bot joins meeting; calendar integration | Same consent framework; auto-join requires participant awareness |
| Zoom AI Companion | Built into Zoom platform | Host activation provides consent; notification banner displayed |
| Microsoft Copilot | Integrated into Teams | Activated by participant; Teams recording indicator shows |
| Google Gemini in Meet | Native to Google Meet | Participant activation satisfies consent; meeting notification shown |
| Fathom | Records locally on host device | Host's local recording provides strong one-party consent position |
Under Tennessee's recording laws, all these tools are compliant when activated by a meeting participant who is aware the recording is taking place. The legal risk increases when tools operate autonomously or when the activating user is unaware that a specific meeting is being recorded.
Penalties for Violations
Criminal Penalties
Unlawful interception of communications under § 39-13-601 is classified as a Class D felony under Tenn. Code Ann. § 39-13-602.
| Offense | Classification | Prison | Fine |
|---|---|---|---|
| Unlawful interception | Class D felony | 2 to 12 years | Up to $5,000 |
| Unlawful disclosure of intercepted communication | Class D felony | 2 to 12 years | Up to $5,000 |
| Use of illegally intercepted communication | Class D felony | 2 to 12 years | Up to $5,000 |
Civil Remedies
Tenn. Code Ann. § 39-13-603 provides a civil cause of action for anyone whose wire, oral, or electronic communication has been unlawfully intercepted, disclosed, or used. An aggrieved party may recover actual damages, statutory damages of $100 per day of violation or $10,000 (whichever is greater), punitive damages, and attorney fees.
Employer and Workplace Considerations
Recording Policies for Tennessee Employers
Tennessee employers may use AI meeting recording tools under the one-party consent framework, provided a meeting participant activates the tool with awareness that recording is occurring. While Tennessee law does not require employers to notify employees about recording, establishing a written recording policy is a best practice that reduces legal risk and builds trust.
A sound workplace policy should specify which AI tools are approved for use, identify who may activate recording, address data retention and access controls, and account for cross-state considerations when remote workers in all-party consent states join meetings.
HIPAA Considerations
Healthcare organizations across Tennessee, including major hospital systems in Nashville, Memphis, and Knoxville, must comply with HIPAA when AI meeting tools capture protected health information (PHI). This requires a Business Associate Agreement with the tool provider, encryption of data in transit and at rest, and assurance that recorded PHI is not used for AI model training.
Cross-State Workforce Considerations
Tennessee employers with remote workers in all-party consent states must obtain consent from all participants when those workers join recorded meetings. Tennessee's one-party consent rule protects the employer for in-state recordings, but it does not override the recording laws of other states where participants are located.
More Tennessee Laws
This article provides general legal information about Tennessee recording laws as they apply to AI meeting tools. Laws and their interpretations can change. Consult an attorney for advice specific to your situation.
Sources and References
- Tenn. Code Ann. § 39-13-601 - Wiretapping and Electronic Surveillance(womenslaw.org)
- Tenn. Code Ann. § 39-13-602 - Penalty for Violations(lawserver.com)
- Tenn. Code Ann. § 39-13-603 - Civil Actions and Damages(lawserver.com)
- 18 U.S.C. § 2511 - Federal Wiretap Act(law.cornell.edu)
- Tennessee Recording Guide - Reporters Committee for Freedom of the Press(rcfp.org)
- Brewer v. Otter.ai Class Action - NPR(npr.org)
- Ambriz v. Google - AI Wiretapping Claims(courthousenews.com)