Maryland AI Meeting Recording Laws: All-Party Consent Required

Maryland is one of the strictest recording consent states in the country, and that strictness creates serious obstacles for AI meeting tools. Under Md. Code, Cts. & Jud. Proc. Section 10-402, recording any wire, oral, or electronic communication requires the consent of all parties. Not one participant. Not a majority. Every single person on the call.
For organizations deploying Otter.ai, Fireflies.ai, or Microsoft Copilot in Maryland, this means a Zoom meeting with 15 participants requires 15 affirmative consents before the AI recorder activates. A single holdout makes the recording unlawful. And the penalties are severe: violations are felonies carrying up to 5 years in prison and $10,000 in fines. Maryland also bars illegally obtained recordings from being used as evidence in court, eliminating even the potential upside of unauthorized recording.
The state legislature has considered narrowing the all-party consent requirement in recent sessions, particularly for domestic violence evidence. But as of April 2026, the core framework remains intact. Anyone using AI meeting tools in Maryland operates under one of the most demanding consent regimes in the nation.
Maryland's All-Party Consent Framework
Md. Code, Cts. & Jud. Proc. Section 10-402 establishes the foundation of Maryland's recording law. The statute makes it unlawful for any person to willfully intercept, endeavor to intercept, or procure any other person to intercept any wire, oral, or electronic communication. The consent exception requires that all parties to the communication agree before any interception occurs.
What the Statute Covers
Section 10-402 applies broadly to three categories of communication:
Wire communications include any aural transfer made in whole or in part through wire, cable, or other similar connection. This encompasses traditional phone calls, VoIP services, and video conferencing platforms like Zoom, Microsoft Teams, and Google Meet.
Oral communications cover spoken words uttered by a person exhibiting an expectation that the communication is not subject to interception. This includes face-to-face conversations in settings where participants reasonably expect privacy.
Electronic communications encompass any transfer of signs, signals, writing, images, sounds, data, or intelligence transmitted electronically. This broad definition captures text-based chat, screen sharing, and data streams within virtual meeting platforms.
AI meeting tools that record, transcribe, or analyze any of these communication types fall within Section 10-402's scope.
The All-Party Consent Standard
Maryland's consent requirement is absolute. Unlike one-party consent states where a single participant's agreement authorizes recording, Maryland demands that every party to the communication consent. The statute does not specify a particular form of consent, but courts have held that consent must be knowing and voluntary.
Implied consent can satisfy the statute in some circumstances. If a meeting host announces that the session will be recorded and participants continue to engage without objection, a court may find implied consent. But relying on implied consent carries significant risk in Maryland. The safer approach is explicit, affirmative consent from each participant.
The all-party standard means that a single participant who objects to recording prevents the AI tool from lawfully operating. In a virtual meeting with 20 participants, 19 affirmative consents and 1 objection means the recording cannot proceed.

Law Enforcement Exception
Section 10-402 includes an exception for law enforcement and investigative officers. An interception is lawful when the officer is a party to the communication, or one of the parties has given prior consent. This exception does not extend to private employers, individuals, or AI vendors.
How AI Meeting Recorders Interact with Maryland Law
Maryland's all-party consent requirement fundamentally changes the compliance calculus for AI meeting tools compared to one-party consent states.
The Core Legal Problem
In a one-party consent state like Louisiana, an employee activating Otter.ai satisfies the statute by being a consenting participant. In Maryland, that employee's consent is necessary but insufficient. Every other participant must also consent before the tool records.
This creates friction that AI meeting tools are not designed to handle. Otter.ai's notetaker joins meetings automatically through calendar integrations. Fireflies.ai's bot enters calls without individual participant approval. Microsoft Copilot processes Teams audio streams without per-participant consent gates. Each of these workflows assumes that one participant's activation is enough. In Maryland, it is not.
The Third-Party Vendor Problem
Beyond participant consent, Maryland's statute raises questions about AI vendors as third parties to the communication. When Otter.ai receives and processes a meeting recording on its servers, it accesses the contents of a wire or electronic communication. Under Section 10-402, this access requires consent from all parties.
The Ambriz v. Google "capability test" (N.D. Cal. 2025) deepens this concern. The court held that a vendor's technical capability to use communication data for its own benefit was sufficient to establish third-party interception, regardless of whether the vendor actually used the data. If Maryland courts adopted this reasoning, an AI vendor that receives meeting data and has the capability to use it for model training or product improvement could be treated as an interceptor under Section 10-402.
This means that even in a meeting where all participants consent to recording, the AI vendor's access to the communication could constitute a separate interception requiring separate consent. Participants would need to consent not only to the recording itself but to the vendor's receipt and processing of the communication.
The Otter.ai Litigation Connection
The Brewer v. Otter.ai class action (N.D. Cal., filed August 2025) alleges conduct that would unambiguously violate Maryland law. The complaint claims Otter's notetaker joined meetings without obtaining consent from non-account holders, transmitted recordings to Otter's servers in real time, retained recordings indefinitely, and used audio data to train AI models.
Each of these allegations describes an interception without all-party consent. Under Maryland law, every affected participant would have both criminal and civil claims. The potential liability exposure for AI vendors whose tools operate in Maryland without proper consent protocols is enormous.
The Walker v. Otter.ai complaint adds a biometric dimension, alleging that Otter captures and stores "voiceprints" during meetings. While Maryland does not have a dedicated biometric privacy law like Illinois' BIPA, the unauthorized collection of voiceprints during unconsented recordings would compound the underlying wiretapping violation.
Popular AI Meeting Tools and Maryland Compliance
| Tool | How It Records | Maryland Compliance |
|---|---|---|
| Otter.ai | Joins as meeting participant via calendar integration | Requires consent from ALL participants before activation |
| Fireflies.ai | Joins as bot participant on Zoom, Teams, Meet | Requires ALL participants to consent before bot joins |
| Microsoft Copilot | Processes Teams audio natively | Requires all meeting participants to consent to Copilot transcription |
| Google Gemini | Integrates within Google Meet | Requires all participants to agree before feature activates |
| Zoom AI Companion | Built into Zoom for meeting summaries | Requires consent from every participant; Zoom's built-in notification helps but may not constitute consent |
No AI meeting tool currently offers a consent workflow that automatically satisfies Maryland's all-party standard. Platform-level recording notifications (the pop-up banner in Zoom or Teams saying "This meeting is being recorded") may help establish implied consent, but organizations operating in Maryland should not rely solely on passive notifications.

Criminal Penalties
Section 10-402 classifies willful wiretapping violations as felonies. The penalties include:
- Up to 5 years in prison
- Fines up to $10,000
- Or both
Maryland does not distinguish between first-time and repeat offenders for sentencing purposes under the wiretapping statute. A first violation carries the same maximum penalty as subsequent offenses.
The "willful" element requires proof that the violator intentionally intercepted the communication and knew the interception was unauthorized. For AI meeting tool deployments, this element is typically satisfied when a user activates a recording tool while aware that not all participants have consented. Ignorance of Maryland's all-party consent requirement is generally not a defense.
Suppression of Evidence Under Section 10-405
Maryland law takes the additional step of excluding illegally obtained recordings from court proceedings. Under Section 10-405, any aggrieved person may file a motion to suppress the contents of any wire, oral, or electronic communication intercepted in violation of Section 10-402.
If the court finds the interception was unlawful, the evidence is inadmissible. This rule eliminates a potential incentive for unauthorized recording. Even if a recording captures evidence of wrongdoing by another party, the recording cannot be used in court if it was made without all-party consent.
This suppression rule has particular significance for workplace disputes. An employer who records meetings without employee consent to gather evidence of misconduct will find that evidence unusable in any Maryland court proceeding.
Civil Liability Under Section 10-410
Section 10-410 provides civil remedies for victims of unauthorized interception. Any person whose communication is intercepted, disclosed, or used in violation of the wiretapping statute may bring a civil action and recover:
- Actual damages but not less than liquidated damages of $100 per day of violation or $1,000, whichever is greater
- Punitive damages for willful or egregious violations
- Reasonable attorney's fees and litigation costs
The willfulness requirement for punitive damages means that organizations deploying AI tools with knowledge of Maryland's all-party consent requirement face enhanced exposure. An employer who implements company-wide AI meeting recording without obtaining all-party consent has acted with knowledge of the legal requirement, satisfying the willfulness standard.
The per-day damages structure creates rapid accumulation. An AI tool that records meetings over a 90-day period generates at least $9,000 in statutory damages per affected participant. For a tool recording meetings across a department of 50 employees, the baseline statutory exposure reaches $450,000 before punitive damages and legal fees.
Employer and Workplace Considerations
Maryland's all-party consent requirement imposes specific obligations on employers that go beyond the technical setup of AI meeting tools.

Mandatory Consent Protocols
Employers in Maryland must establish consent protocols before deploying any AI meeting recording tool. These protocols should include:
Pre-meeting disclosure. Meeting invitations should state that the session will be recorded and transcribed by a specific AI tool. This written notice provides a foundation for claiming implied consent, though explicit consent remains safer.
Verbal confirmation at meeting start. The meeting host should announce that recording will occur, identify the tool being used, and ask all participants to confirm their consent. A clear statement followed by a pause for objections satisfies the minimum standard.
Opt-out mechanism. If any participant objects, recording must not proceed. The employer cannot require employees to consent to recording as a condition of attending required meetings, though this area involves workplace law considerations beyond the wiretapping statute.
Documentation. Maintain records of when and how consent was obtained for each recorded meeting. If a dispute arises, documentation demonstrates compliance with Section 10-402.
Platform Consent Features
Zoom, Teams, and Google Meet offer built-in recording notifications. In Maryland, employers should configure these features to require active consent rather than passive notification:
- Zoom allows hosts to require participants to click a consent button before the meeting begins recording. Enable this feature for all Maryland-based meetings.
- Microsoft Teams displays a banner notification when recording starts. Consider requiring a verbal confirmation in addition to the banner, as passive notification may not constitute consent under Maryland law.
- Google Meet notifies participants that recording is active. Similar to Teams, supplementing the notification with explicit consent is advisable.
Cross-Border Meeting Dynamics
Maryland's all-party consent requirement follows Maryland participants into interstate calls. When a Maryland employee joins a virtual meeting with participants in one-party consent states, Maryland law still applies to the Maryland participant.
A practical example: a Zoom meeting includes employees in Maryland, Louisiana, and Maine. Louisiana and Maine follow one-party consent. But because a Maryland participant is on the call, recording without the Maryland participant's consent violates Section 10-402. The Maryland participant has criminal and civil claims regardless of the other states' standards.
This dynamic means that any organization with employees or clients in Maryland must treat all meetings involving Maryland participants as subject to the all-party consent requirement.
Employee Rights and Employer Recording
Maryland employees have strong protections against unauthorized employer recording. An employer who records workplace meetings, phone calls, or conversations without all-party consent commits a felony under Section 10-402. The employee can file a criminal complaint with law enforcement and pursue civil damages under Section 10-410.
This applies to AI monitoring tools as well. An employer who deploys AI-powered call analytics, sentiment analysis, or productivity monitoring that intercepts employee communications without consent faces the same criminal and civil liability as traditional wiretapping.

Recent Legislative Developments
Maryland's all-party consent requirement has faced legislative scrutiny in recent sessions, driven partly by domestic violence advocacy and partly by the practical challenges of modern communication technology.
HB 314 (2025-2026)
Delegate Robin Grammer Jr. sponsored HB 314, which would allow intercepted oral or electronic communications to be received as evidence in court when "the interest of justice will be served." The bill specifically targets situations where victims of domestic violence record their abusers without consent. Under current law, these recordings are inadmissible under Section 10-405.
SB 661 and HB 802 (2026)
Companion bills SB 661 and HB 802 in the 2026 session would allow intercepted communications to be received as evidence in criminal proceedings under specified circumstances. SB 661 had a hearing before the Senate Judicial Proceedings Committee on February 24, 2026.
Status and Impact
As of April 2026, none of these bills have been enacted. Maryland's all-party consent requirement remains unchanged. Even if evidence admissibility exceptions pass, they would not alter the underlying consent requirement for recording. Making an unauthorized recording would remain a felony; the bills would only affect whether that recording could later be used as evidence.
Baltimore City Public Defender Marguerite Lanaux has argued that all-party consent protects against "fabricated evidence" through AI-generated deepfakes, noting that AI audio manipulation is growing more sophisticated. This argument has given some legislators pause about weakening the consent standard.
Federal Law Interaction
The federal Wiretap Act at 18 U.S.C. Section 2511 sets a one-party consent baseline. Federal law permits recording when one participant consents, provided the recording is not made for criminal or tortious purposes. Federal penalties include up to 5 years in prison and fines up to $250,000.
Maryland's all-party consent requirement is stricter than federal law. When state law imposes a higher standard, state law governs. Complying with Maryland's Section 10-402 automatically satisfies the federal Wiretap Act, but complying with federal law alone does not satisfy Maryland's requirements.
For interstate meetings, the interaction is straightforward: if a Maryland participant is on the call, Maryland's all-party standard applies to any recording that captures the Maryland participant's communication, regardless of where other participants are located.
Penalties at a Glance
| Category | Details |
|---|---|
| Consent Standard | All-party consent (Section 10-402) |
| Criminal Penalty | Felony: up to 5 years, $10,000 fine |
| Civil Damages | $100/day or $1,000 minimum, plus punitive damages, attorney's fees (Section 10-410) |
| Evidence Suppression | Illegally obtained recordings inadmissible (Section 10-405) |
| Federal Floor | 18 U.S.C. Section 2511: up to 5 years, $250,000 fine |
| Key Distinction | Applies to wire, oral, AND electronic communications |
| Legislative Activity | HB 314, SB 661 propose limited evidence exceptions (not enacted as of April 2026) |
More Maryland Laws
- [Maryland Data Privacy Laws](/us-laws/data-privacy-laws/maryland-data-privacy-laws/data-breach-notification)
- Maryland Recording Laws
- Maryland Data Privacy Laws
- Maryland Recording Laws
- Maryland Recording Laws
- Maryland Data Privacy Laws
- Maryland Recording Laws
- Maryland Recording Laws
This article provides general legal information about Maryland's recording laws as they apply to AI meeting tools. Maryland's all-party consent requirement creates one of the most demanding compliance environments in the country for AI meeting technology. Laws evolve, and the legislative efforts to create limited exceptions may change the landscape. Consult an attorney licensed in Maryland for advice specific to your situation.
Sources and References
- Md. Code, Cts. & Jud. Proc. Section 10-402 - Wiretapping and Electronic Surveillance(mgaleg.maryland.gov).gov
- Maryland Department of IT - Communication Recordings Policy(doit.maryland.gov).gov
- Maryland General Assembly - HB 314 (2026 Session)(mgaleg.maryland.gov).gov
- 18 U.S.C. Section 2511 - Federal Wiretap Act(law.cornell.edu)
- Brewer v. Otter.ai Class Action (NPR, August 2025)(npr.org)
- Ambriz v. Google - AI Wiretapping Ruling (Courthouse News, 2025)(courthousenews.com)
- Maryland Recording Consent and Evidence Law Reform (WYPR, 2025)(wypr.org)
- Maryland Recording Guide - Reporters Committee for Freedom of the Press(rcfp.org)
- AI Meeting Assistants Legal Risks (Fisher Phillips, 2025)(fisherphillips.com)