EnglishEspañol
AI Meeting Recording LawsMichigan Laws flagMichigan Laws
Michigan flag

Michigan

Michigan AI Meeting Recording Laws (2026)

Independently fact-checkedEditor-reviewedLaw current as of August 16, 2026By Recording Law Editorial TeamReviewed August 30, 202613 min read

Independently fact-checked against primary sources (last audited August 16, 2026). · Reviewed by the RecordingLaw editorial team. · Law checked current as of August 16, 2026. · 3 primary sources cited on this page. How we verify our legal content

Michigan AI Meeting Recording Laws (2026)

AI meeting recorders occupy a legal gray zone in Michigan. MCL 750.539c requires all-party consent on its face, but courts treat the law as one-party consent for human participants. Whether an AI bot qualifies as a participant or a third-party eavesdropper under the statute remains unresolved.

Michigan's eavesdropping law occupies a rare legal gray zone. The statute at Mich. Comp. Laws Section 750.539c prohibits using any device to eavesdrop on a private conversation "without the consent of all parties," which reads like an all-party consent requirement. But Michigan courts have interpreted the law differently for decades, holding that a participant in a conversation cannot "eavesdrop" on their own conversation. That judicial interpretation effectively makes Michigan a one-party consent state for participants, while maintaining all-party consent requirements for non-participants.

This ambiguity matters enormously for AI meeting recording tools. When Otter.ai, Fireflies.ai, or another AI notetaker joins a video call, is the bot a "participant" in the conversation or a third-party eavesdropper? The answer determines whether the bot can legally record without everyone's consent, and no Michigan court has directly resolved this question as of April 2026.

This article covers Michigan's consent framework, the participant exception, how the ambiguity applies to AI meeting tools, penalties for violations, and what employers need to know. Consult an attorney for advice specific to your situation, as this article provides general legal information and not legal advice.

The Statutory Text vs. Judicial Interpretation

Michigan's eavesdropping statute reaches, in its own words, "any person who is present or who is not present during a private conversation and who wilfully uses any device to eavesdrop upon the conversation without the consent of all parties thereto, or who knowingly aids, employs or procures another person to do the same." Read alone, that sentence covers people who are in the room as readily as outsiders, and it requires the consent of everyone.

The participant exception does not come from that sentence. It comes from the separate definitions section. MCL 750.539a(2) defines "eavesdrop" or "eavesdropping" as "to overhear, record, amplify or transmit any part of the private discourse of others without the permission of all persons engaged in the discourse." Michigan courts have treated the words "of others" as the limiting language: someone who is part of a conversation is not capturing the private discourse of others, but taking part in their own. That reading, established in Sullivan v. Gray (Mich. Ct. App. 1982), has been the governing interpretation for over four decades.

The Sullivan court found that "the statutory language, on its face, unambiguously excludes participant recording from the definition of eavesdropping by limiting the subject conversation to 'the private discourse of others.'" A participant recording their own conversation is not intercepting the discourse of "others." Note what the exception has to work around: the phrase "who is present or who is not present" in MCL 750.539c is the strongest textual argument on the other side, and it is the phrase the exception's critics have leaned on.

Fisher v. Perron: A Federal Prediction, Not a Michigan Ruling

In March 2022, the U.S. Sixth Circuit Court of Appeals directly addressed this question in Fisher v. Perron, 30 F.4th 289 (6th Cir. 2022). The case involved siblings in a dispute over their late mother's estate. Michelle Perron recorded phone conversations with her brother Frank Fisher and other siblings without their knowledge, then attempted to use those recordings in estate proceedings.

The Sixth Circuit rejected Fisher's claim, agreeing with the district court that "under the current law in Michigan, a participant does not violate Michigan's eavesdropping statute by recording a conversation without the consent of the other participants."

The court was explicit about the limits of what it was doing. It stated that "the Michigan Supreme Court has yet to determine whether this statutory language allows for secret participant recordings or requires the consent of all parties to record a call," and that the panel therefore "must predict how the Michigan Supreme Court would rule based on 'all the available data.'" That is an Erie prediction of state law by a federal court. It resolved the case in front of it, but it does not bind any Michigan court and it did not settle the question as a matter of Michigan law. For an article about a question a Michigan court has not yet reached, that distinction matters.

The Michigan Supreme Court Has Not Answered the Question

The participant exception has been challenged, and the challenge was serious. Sullivan v. Gray itself drew a dissent. In 2019, a federal district court in AFT Michigan v. Project Veritas, 397 F. Supp. 3d 981 (E.D. Mich. 2019), worked through the same "available data" and reached the opposite conclusion, holding that the Michigan Supreme Court would read the statute to require the consent of all parties. That court reasoned that Sullivan's construction "contravenes the Legislature's intent made clear" by the statutory phrase covering "any person who is present." It then certified the question to the Michigan Supreme Court.

The Michigan Supreme Court declined in May 2021 to answer it. In re Certified Question, 959 N.W.2d 172 (Mich. 2021). A declination is not an endorsement: the court simply did not take the question. In November 2021 the same district court granted reconsideration and reversed itself, holding that "the statute is not violated when a conversation is recorded by one of its participants," which is why there is no live contrary holding today.

So the accurate statement as of April 2026 is narrower than "settled." Every currently operative decision points the same way, and the Legislature has not amended the statute in six decades of judicial interpretation. But the state's highest court has never ruled, one federal court reached the opposite result before withdrawing it, and the textual argument against the exception has never been answered by a Michigan court of last resort. Anyone planning around the exception should treat it as the prevailing interpretation, not as a closed question.

The Sullivan Limitation: Third-Party Agents

Sullivan v. Gray did include one important limitation: while a participant may record their own conversation, they cannot direct a third party to record on their behalf without the consent of all parties. This limitation is directly relevant to AI meeting tools. If an AI bot is classified as a third-party agent rather than a participant, it could fall outside the participant exception and require all-party consent.

Empty corporate boardroom with leather chairs around a long table, a dark blank wall screen at the end

How Michigan's Ambiguity Applies to AI Meeting Bots

The Central Question: Participant or Eavesdropper?

Michigan's participant exception creates a binary legal test for AI meeting recording tools:

If the AI bot is a "participant": It can record the conversation without the consent of other parties, just like any human participant. Under this classification, tools like Otter.ai and Fireflies.ai would be legal in Michigan as long as the account holder (who is a participant) authorized the recording.

If the AI bot is a "third-party eavesdropper": It requires consent from all parties to the conversation. Under this classification, an AI bot that joins a meeting and records without everyone's knowledge would violate MCL 750.539c, and the person who deployed it could also be liable for procuring an illegal eavesdrop.

No Michigan court has directly ruled on this question. The answer likely depends on several factors.

Factor 1: How the Bot Joins the Meeting

An AI bot that joins a meeting as a visible participant with its own name displayed (such as "Otter Notetaker") has a stronger argument for participant status than a bot that operates invisibly in the background. However, "joining" a meeting may not be enough. Sullivan v. Gray defined a participant as someone engaged in the "private discourse," which implies active communication rather than passive observation.

Factor 2: Whether the Bot Acts Independently

The Sullivan limitation against third-party agents is significant. If an AI bot merely records on behalf of the meeting host (acting as a tool or extension of the host), it might be treated as the host's recording device rather than a separate entity. But if the bot processes recordings independently, sends them to the vendor's servers for AI training, or generates outputs that the host did not direct, courts may view it as an independent third party.

Factor 3: The Ambriz v. Google "Capability Test"

The February 2025 ruling in Ambriz v. Google (N.D. Cal.) provides a potential framework for Michigan courts. The court held that an AI vendor qualifies as a third-party eavesdropper if it has the technical capability to use intercepted data for its own purposes (such as model training), regardless of whether it actually does so.

Under this test, most commercial AI meeting tools would likely be classified as third-party eavesdroppers in Michigan, because they have the capability to use recorded data for model improvement. This would place them outside the participant exception and require all-party consent.

Factor 4: The Brewer v. Otter.ai Litigation

The August 2025 Brewer v. Otter.ai class action further illustrates the risk. The complaint alleges that Otter.ai's Notetaker joins meetings without obtaining consent from all participants, records conversations of non-account holders, and uses the data to train machine learning models. While the case was filed in California, its legal theories would apply in Michigan for meetings involving Michigan participants.

ToolDefault BehaviorMichigan Risk Assessment
Otter.aiBot joins automatically via calendar integration; host controls consent settingsUncertain: likely treated as third-party agent, not a participant
Fireflies.aiBot joins as named participant; Zoom may show recording pop-upUncertain: visible presence strengthens participant argument, but independent data processing weakens it
Zoom AI CompanionBuilt-in feature; shows recording indicatorLower risk: integrated into the platform rather than joining as a separate entity
Microsoft CopilotIntegrated into Teams; transcription notification displayedLower risk: built-in feature rather than third-party bot
Google Gemini in MeetBuilt-in summarization; recording banner shownLower risk: native platform feature
Read.aiBot joins meetings; sends consent requestsModerate: proactive consent reduces risk, but third-party classification still possible

Built-in platform features (Zoom AI Companion, Microsoft Copilot, Google Gemini) carry lower risk in Michigan because they function as extensions of the recording platform rather than independent third-party entities. Third-party bots that join meetings as separate participants and process data on their own servers face the highest legal uncertainty.

Two monitors on a desk both showing soft abstract glows with no readable content, a keyboard in front

Penalties for Violating Michigan Eavesdropping Laws

Criminal Penalties

OffenseClassificationMaximum PrisonMaximum Fine
Eavesdropping on a private conversation, MCL 750.539cFelony2 years$2,000
Installing or using a device in a private place, first offense, MCL 750.539d(3)(a)(i)Felony2 years$2,000
Installing or using a device in a private place, after a prior conviction, MCL 750.539d(3)(a)(ii)Felony5 years$5,000
Distributing or transmitting a recording obtained in violation of MCL 750.539d, under MCL 750.539d(3)(b)Felony5 years$5,000
Using or divulging information known to have been obtained in violation of MCL 750.539b, 539c, or 539d, under MCL 750.539eFelony2 years$2,000

Under MCL 750.539c, violations are classified as felonies. The device offenses in MCL 750.539d escalate: the 2-year exposure is the first-offense tier, and both a repeat violation and distributing the resulting recording carry up to 5 years and $5,000. Both the person who deploys the AI recording tool and the vendor whose tool performs the recording could potentially face liability.

Civil Remedies

MCL 750.539h provides a private right of action for victims of illegal eavesdropping. A person whose private conversation is illegally recorded may sue for an injunction against further eavesdropping, actual damages, and punitive damages as determined by the court or jury. In the context of AI meeting tools, each recorded participant who did not consent could potentially bring a separate civil claim.

Evidentiary Impact

Michigan's eavesdropping act contains no suppression rule. Sections 750.539a through 750.539i create criminal penalties and the civil remedies in MCL 750.539h, but none of them directs a court to exclude a recording made in violation of the act. MCL 750.539i points the other way entirely: it provides that proof of the installation of such a device in a private place is prima facie evidence of a violation of MCL 750.539d, which is a presumption against the person who installed it rather than a bar on the recording.

Whether a particular recording comes into evidence therefore turns on the ordinary rules of evidence and on the judge hearing the matter, not on an automatic statutory exclusion. Do not assume an AI meeting transcript will be kept out of a proceeding because it was captured without consent, and do not assume it will be let in.

The Bullard-Plawecki Act

Michigan's Bullard-Plawecki Employee Right to Know Act adds an additional layer of protection in the employment context. The Act prohibits employers from gathering or maintaining records of employees' non-employment activities, associations, or political activities without consent. AI meeting tools that capture conversations beyond their intended business scope could implicate this statute.

Employer and Workplace Recording Rules

The Workplace Recording Dilemma

Michigan employers face a particular challenge with AI meeting recording. While the participant exception allows an employee who is part of a conversation to record it, deploying an AI bot to record on the employer's behalf raises the Sullivan limitation against third-party agents.

Employers should not assume that because Michigan is effectively a one-party consent state for participants, they can freely deploy AI recording tools without disclosure. The prudent approach is to treat AI bots as potential third-party eavesdroppers and obtain consent from all meeting participants.

A smartphone resting on a notebook showing a single abstract glowing toggle and no text

Best Practices for Michigan Employers

Employers using AI meeting tools in Michigan should consider several compliance measures. Written policies should clearly state that AI recording tools may be used in workplace meetings. Verbal announcements at the start of each recorded meeting provide real-time notice. Meeting invitations should note that AI transcription will be active. Opt-out mechanisms should be available for participants who do not wish to be recorded.

Video Surveillance Considerations

Michigan law permits employers to use video surveillance in the workplace for legitimate business purposes, but cameras may not be installed in areas where employees have a reasonable expectation of privacy (such as restrooms, locker rooms, and changing areas). Audio recording through workplace surveillance systems is subject to the eavesdropping statute and its participant exception ambiguity.

Remote and Multi-State Meetings

When Michigan employees participate in meetings with colleagues in other states, the strictest applicable law governs. If any participant is located in an all-party consent state like Massachusetts, California, or Illinois, all participants must be notified. Michigan employers with distributed workforces should implement a universal disclosure policy requiring announcement of AI recording at the start of every meeting.

Federal Law and Michigan's Framework

18 U.S.C. Section 2511

The federal Wiretap Act follows a one-party consent standard. A person who is party to a communication, or who has the consent of one party, may lawfully intercept it under federal law. Federal penalties for violations include up to 5 years in prison and fines up to $250,000.

Michigan's eavesdropping statute and the federal Wiretap Act can apply simultaneously to the same recording. When state and federal law conflict, the stricter standard governs. For AI meeting recording in Michigan, the participant exception creates functional one-party consent for human participants, but the unresolved question of AI bot classification means the state standard could be stricter than federal law for AI tools.

Cross-Border Implications

AI meeting recordings frequently involve participants in multiple states. A Michigan-based company recording a meeting with participants in California (all-party consent) or Illinois (which has its own Biometric Information Privacy Act) must comply with the strictest applicable law. The safest approach is to adopt all-party consent practices regardless of Michigan's participant exception.

Looking Ahead: Michigan's AI Recording Landscape

Michigan's eavesdropping statute was written long before AI meeting assistants existed. The participant exception, crafted in 1982 for human conversations, does not map cleanly onto AI bots that join meetings, process audio through machine learning models, and store data on vendor servers.

Several developments could resolve the current ambiguity. The Michigan Legislature could amend MCL 750.539c to explicitly address AI recording tools and clarify whether they fall within or outside the participant exception. Michigan courts could rule directly on whether an AI bot qualifies as a participant or a third-party eavesdropper. Federal litigation like Brewer v. Otter.ai and Ambriz v. Google could establish precedents that Michigan courts adopt.

Filing cabinet drawer pulled open showing hanging folders with short two-letter state-abbreviation tabs

Until one of these developments occurs, businesses and individuals using AI meeting recording tools in Michigan should err on the side of disclosure and consent. The legal ambiguity itself is a risk factor, as it means any recording made without all-party consent could be challenged if a court later determines that AI bots fall outside the participant exception.

More Michigan Laws

Explore other Michigan law topics on Recording Law:

More Michigan Laws

Frequently Asked Questions

Is it legal to use an AI meeting recorder like Otter.ai in Michigan?

The answer is unsettled. Michigan's eavesdropping statute, MCL 750.539c, requires all-party consent on its face, but Michigan courts since Sullivan v. Gray (1982) have read the definition of eavesdropping in MCL 750.539a(2), which covers only 'the private discourse of others,' to exclude participant recording. The Sixth Circuit predicted the same result in Fisher v. Perron (2022) while noting that the Michigan Supreme Court has never decided the question. Whether an AI bot counts as a participant or a third-party eavesdropper has not been decided by any Michigan court as of April 2026.

Do I need to disclose that an AI notetaker is recording a meeting in Michigan?

It is not strictly required for a human participant recording their own conversation, under the participant exception established in Sullivan v. Gray. However, because it is unresolved whether the AI bot itself counts as a participant or as a third party the host directed to record, disclosure is generally the safer practice. Sullivan also limits the exception. A participant cannot direct a third party to record on their behalf without consent from everyone involved.

What is the difference between an AI bot being a participant versus a third-party eavesdropper under Michigan law?

If a court treats the AI bot as a participant, it may record without the other parties' consent, similar to a human participant relying on the Sullivan exception. If a court instead treats the bot as a third-party eavesdropper, such as under the capability test used in Ambriz v. Google, all-party consent would likely be required. Relevant factors discussed include how visibly the bot joins the meeting and whether it processes or stores data independently of the person who activated it.

What are the penalties for illegal eavesdropping in Michigan?

Violations of MCL 750.539c are felonies, punishable by up to two years in prison and a fine of up to $2,000. The related device offenses in MCL 750.539d run higher: a repeat violation, or distributing a recording obtained through one, carries up to five years and a $5,000 fine. MCL 750.539h also provides a private right of action, letting a person whose private conversation was illegally recorded sue for an injunction, actual damages, and punitive damages. The act contains no suppression rule, so whether an unlawfully made recording is admissible is decided under the ordinary rules of evidence rather than by an automatic statutory bar.

Has a Michigan court ruled on whether AI meeting bots are participants or eavesdroppers?

No. As of April 2026, no Michigan court has directly addressed whether an AI meeting bot qualifies as a participant or a third-party eavesdropper under MCL 750.539c. Until that question is resolved, businesses and individuals using AI meeting tools in Michigan are generally advised to err on the side of disclosure and all-party consent.

Updates

Corrected the quotation of Michigan’s eavesdropping statute and its penalty ranges, clarified that Fisher v. Perron was a federal prediction rather than a binding Michigan ruling, added the AFT Michigan challenge and the Michigan Supreme Court’s declination to answer it, and removed an unsupported claim that illegally obtained recordings are generally inadmissible.

Independently fact-checked against the cited primary sources; governing law re-checked for recent changes

Corrected the civil remedies listed under MCL 750.539h: the statute authorizes an injunction, actual damages, and punitive damages, not attorney's fees, which the article had incorrectly listed while omitting the actual punitive-damages remedy.

Governing law re-checked for recent changes

Reviewed and approved by an editor

Sources and References

  1. Mich. Comp. Laws Section 750.539c - Eavesdropping(legislature.mi.gov).gov
  2. Sullivan v. Gray, 117 Mich. App. 476 (1982) - Participant Exception(law.justia.com)
  3. Fisher v. Perron, 30 F.4th 289 (6th Cir. 2022) - One-Party Consent Affirmed(butzel.com)
  4. Brewer v. Otter.ai Class Action (NPR, August 2025)(npr.org)
  5. Ambriz v. Google - AI Wiretapping Ruling (Courthouse News, 2025)(courthousenews.com)
  6. Michigan Bullard-Plawecki Employee Right to Know Act(legislature.mi.gov).gov
  7. 18 U.S.C. Section 2511 - Federal Wiretap Act(law.cornell.edu)
  8. MCL 750.539h - Civil Remedies for Eavesdropping(legislature.mi.gov).gov
  9. MCL 750.539a - Definitions, including eavesdrop as the private discourse of others(legislature.mi.gov)
  10. MCL 750.539d - Devices in a private place, penalty tiers up to 5 years and $5,000(legislature.mi.gov)
  11. MCL 750.539e - Using or divulging information obtained in violation of the act(legislature.mi.gov)
  12. MCL 750.539i - Prima facie evidence provision; the act contains no suppression rule(legislature.mi.gov)
  13. Fisher v. Perron, 30 F.4th 289 (6th Cir. 2022) - published opinion(opn.ca6.uscourts.gov)
Share: