Minnesota
Minnesota AI Meeting Recording Laws (2026)
Independently fact-checked against primary sources (last audited November 1, 2026). · Reviewed by the RecordingLaw editorial team. · Law checked current as of November 1, 2026. · 4 primary sources cited on this page. How we verify our legal content

Minnesota is a one-party consent state under Minn. Stat. Section 626A.02, meaning a meeting participant who activates an AI recording tool does not need to notify other attendees. The recording is lawful as long as the authorizing participant is present and active in the conversation and the recording is not made for a criminal or tortious purpose.
Minnesota's recording law offers more flexibility than many states. Under Minn. Stat. Section 626A.02, only one party to a conversation needs to consent to the recording. This one-party consent framework means that a meeting participant who activates an AI recording tool is generally on solid legal ground, provided they are genuinely part of the conversation being recorded.
That relative simplicity comes with significant caveats. Minnesota treats wiretap violations as felonies: up to $20,000 in fines, up to 5 years in prison, or both. And the Minnesota Consumer Data Privacy Act (MCDPA), enacted in 2024 and effective July 31, 2025, introduced obligations for AI tools that process personal data. Those obligations reach consumer-facing recordings rather than ordinary workplace meetings, a distinction explained below.
This article covers Minnesota's consent framework, how it applies to AI meeting recorders, the MCDPA's impact, penalties, employer considerations, and compliance strategies. As of November 2026, this information reflects current law, but consult an attorney for advice specific to your situation.
Minnesota's Consent Framework for Recording
One-Party Consent Standard
Minnesota's wiretap statute follows the federal model. Under Minn. Stat. Section 626A.02, subdivision 2(d), it is not unlawful for a person who is not acting under color of law to intercept a wire, electronic, or oral communication where that person is a party to the communication, or where one of the parties to the communication has given prior consent to the interception.
In practical terms, this means a meeting participant who turns on an AI notetaker like Otter.ai or Fireflies.ai is generally permitted to do so without notifying other participants. The participant's own consent satisfies the one-party requirement, subject to the purpose limit below.
The Criminal Intent Exception
Minnesota's one-party consent rule includes a critical limitation. The exception does not apply if the communication is intercepted "for the purpose of committing any criminal or tortious act in violation of the constitution or laws of the United States or of any state." Recording a conversation to gather information for blackmail, fraud, or harassment would not be protected by one-party consent, even though the person recording is a participant.
This exception could affect AI meeting recording in specific scenarios. If an employer deploys AI recording tools to gather evidence for use in retaliating against an employee, or if a competitor records a business meeting to steal trade secrets, the criminal intent exception would strip away one-party consent protection.
What Counts as a "Party" to the Communication
The one-party consent exception applies to a "person" who is a "party to the communication." For human participants, this is straightforward: if you are in the meeting, you are a party. The more complex question, as in every state, is whether an AI bot qualifies as a "party."
Minnesota's statute does not define "party" in a way that includes or excludes automated systems. The bot may not need party status at all: subdivision 2(d) also permits an interception by anyone when one of the parties has given prior consent, so a participating host's consent can extend to a tool the host directs. The limit is purpose. That consent does not protect an interception made for a criminal or tortious purpose, and if the AI vendor uses recordings for its own ends (for example, to train machine learning models), a court could find that purpose tortious, as the federal court in the Otter.ai case allowed plaintiffs to argue under the identical federal wording.

How Minnesota Law Applies to AI Meeting Recorders
The Account Holder's Consent
In a typical AI meeting recording scenario, a human participant (the account holder) integrates an AI tool with their calendar or meeting platform. When a meeting starts, the AI bot joins automatically or at the account holder's direction. The account holder is a party to the communication and has consented to the recording.

Under Minnesota's one-party consent framework, this arrangement is generally lawful for the account holder. The account holder's status as a party and their consent to the recording satisfies the statutory requirement, and other participants do not need to be notified. The exception still fails if the interception is made for a criminal or tortious purpose, which is the argument now being litigated against AI vendors that reuse recordings for their own purposes.
When the Account Holder Is Not Present
A more complicated scenario arises when an AI bot joins a meeting but the account holder who authorized the tool is not a participant. Some AI meeting tools can be configured to record meetings on the account holder's calendar even when the account holder does not attend. In this situation, the absent account holder is not a party, so their own consent does not count.
Unless another participant consents, the recording likely does not qualify for the one-party consent exception and can violate Section 626A.02. Two questions remain open in Minnesota: whether participants who see a named bot or a recording notice and keep talking have impliedly consented, and whether the account holder or the vendor is the one intercepting.
The Otter.ai Litigation
In re Otter.AI Privacy Litigation (N.D. Cal., No. 5:25-cv-06911, formerly Brewer v. Otter.ai) consolidates four class actions filed against Otter.ai in 2025. One plaintiff participated in a Zoom meeting where the Otter Notetaker joined automatically because the host had integrated the tool, and the plaintiffs allege that Otter.ai recorded without obtaining meaningful consent from non-account-holder participants and used the conversations to train its own AI models.
In August 2026 the court let the core federal Wiretap Act, California privacy and Illinois biometric claims proceed past a motion to dismiss. The federal claim survived on the theory that using meeting conversations without consent to train Otter's own AI models could be a tortious purpose that defeats the one-party consent exception, even if Otter counted as a party. The case is now in discovery, and no court has decided whether Otter actually violated the law.
Minnesota's one-party exception in Section 626A.02, subdivision 2(d) has the same criminal-or-tortious-purpose limit as the federal law. So in Minnesota, a present host's consent probably protects the host, but it does not simply cover the recording: consent is defeated if the interception is made for a criminal or tortious purpose, and the Otter ruling shows that argument surviving a motion to dismiss against a vendor that uses recordings for its own ends. No Minnesota court has decided the question. Whether the MCDPA (discussed below) adds any data processing obligation depends on whether the recorded participants were acting in an individual or household context rather than a work one.
The Ambriz v. Google Precedent
In Ambriz v. Google (N.D. Cal., Feb. 10, 2025), a federal judge refused to dismiss California wiretapping claims over Google's contact-center AI. On whether a software vendor is a third-party eavesdropper under California Penal Code 631, the court noted that trial courts are split: some require that the vendor actually use the recordings for its own purposes, while others ask only whether it is capable of doing so. The court applied the broader capability approach, first used in Javier v. Assurance IQ (N.D. Cal. 2023). The ruling bound no other court, and in October 2026 the same judge dismissed the remaining plaintiffs' claims on consent and intent grounds (with leave to amend) and sent others to arbitration.
Minnesota's statute does not turn on whether the vendor is a third party, because a participant's prior consent covers the interception unless it is made for a criminal or tortious purpose. For Minnesota, the vendor's purpose matters more than its label.
Popular AI Meeting Recording Tools and Minnesota Compliance
| Tool | Default Behavior | Minnesota Risk Level |
|---|---|---|
| Otter.ai | Bot joins meetings automatically via calendar integration | Low for a present host; vendor reuse of recordings is the open question; MCDPA obligations only where recordings capture consumers, not workplace participants |
| Fireflies.ai | Bot joins as named participant; platform may show recording indicator | Low for a present host; vendor reuse of recordings is the open question; same narrow MCDPA exposure |
| Zoom AI Companion | Built-in transcription; recording indicator displayed | Low: native feature with clear notification |
| Microsoft Copilot | Integrated into Teams; transcription notification shown | Low: built-in feature with disclosure |
| Google Gemini in Meet | Built-in summarization; recording banner visible | Low: native feature with visible notification |
| Read.ai | Bot joins meetings; sends consent requests | Low: proactive consent exceeds Minnesota's one-party requirement |
Minnesota's one-party consent framework means that AI meeting tools carry lower wiretap risk than in all-party consent states. For recordings of consumers, the compliance focus shifts toward data privacy under the MCDPA. For internal workplace meetings, the MCDPA's employment exclusion means the wiretap statute and the employer's own notice practices remain the operative constraints.
Minnesota Consumer Data Privacy Act (MCDPA)
Overview
The Minnesota Consumer Data Privacy Act was enacted in 2024, as Laws 2024, chapter 121, article 5, and took effect July 31, 2025. It applies to businesses that control or process personal data of 100,000 or more Minnesota consumers annually, or that control or process data of 25,000 or more Minnesota consumers and derive over 25 percent of gross revenue from selling personal data.
Whether an AI meeting recording vendor is actually covered turns less on those size thresholds than on who is in the meeting. Minn. Stat. Section 325M.11 defines a consumer as "a natural person who is a Minnesota resident acting only in an individual or household context," and adds that a consumer "does not include a natural person acting in a commercial or employment context." Minn. Stat. Section 325M.12, subdivision 2(a)(13) goes further and excludes from the Act entirely any data collected or maintained "in the course of an individual acting as a job applicant to or an employee, owner, director, officer, medical staff member, or contractor of a business if the data is collected and used solely within the context of the role."
Those two provisions do most of the work here. In the ordinary case, an employer's AI notetaker recording a staff meeting or an internal project call, the participants are acting in an employment or commercial context and the recording data sits inside the exclusion. Those attendees generally have no MCDPA rights over the recording, and the vendor owes them no MCDPA duties. The Act becomes relevant when an AI tool captures a Minnesota resident acting in an individual or household context, such as a customer support call or a consumer consultation, or when a vendor reuses recording data outside the employment role it was collected for.
Relevance to AI Meeting Recording
Where the MCDPA does apply, meaning the recorded person is a consumer rather than a workplace participant, it grants rights relevant to AI meeting tools:
Right to question automated decisions: This right is narrower than its name suggests. Minn. Stat. Section 325M.14, subdivision 1(g) attaches only where a consumer's personal data "is profiled in furtherance of decisions that produce legal effects concerning a consumer or similarly significant effects concerning a consumer," and Section 325M.11 limits that phrase to the provision or denial of financial or lending services, housing, insurance, education enrollment or opportunity, criminal justice, employment opportunities, health care services, or access to essential goods or services. A meeting summary or a sentiment score is not itself a decision of that kind. If an employer feeds AI meeting analysis into a hiring or termination decision, the employment-opportunity category is in play, but the person being assessed at work is not a consumer under Section 325M.11, so the MCDPA right generally still does not attach.
Right to opt out: Consumers can opt out of targeted advertising and certain data processing activities. AI meeting tools that use recorded consumer data for purposes beyond transcription (such as training machine learning models or generating analytics) may need to honor opt-out requests.
Right to delete: Consumers can request deletion of personal data. Recordings and transcriptions that contain personal information from Minnesota consumers are subject to deletion requests.
Right to access and correct: Consumers can access their personal data and correct inaccuracies. This applies to transcripts that may contain errors in attributing statements to specific participants.

Compliance Requirements for AI Meeting Tool Vendors
The MCDPA requires covered businesses to respond to consumer rights requests within 45 days. AI meeting recording vendors must be able to identify which recordings actually contain consumer data, meaning recordings of Minnesota residents in an individual or household context rather than a workplace one, process deletion and opt-out requests for those, and provide transparent disclosures about how recording data is used.
The Minnesota Attorney General's Office received dedicated funding to hire four attorneys and an investigator focused on MCDPA enforcement, signaling that the state intends to actively enforce these requirements.
Penalties for Violating Minnesota Recording Laws
Criminal Penalties Under the Wiretap Statute
| Offense | Classification | Maximum Prison | Maximum Fine |
|---|---|---|---|
| Unlawful interception of communications | Felony | 5 years | $20,000 |
| Unlawful disclosure of intercepted communications | Felony | 5 years | $20,000 |
| Use of illegally intercepted communications | Felony | 5 years | $20,000 |
Each offense carries a fine of up to $20,000, up to 5 years in prison, or both, under Section 626A.02, subdivision 4(a).
Civil Remedies
Section 626A.13 lets a person whose communication was unlawfully intercepted, disclosed or used sue for equitable relief, damages, punitive damages in appropriate cases, and attorney fees. The court may award the greater of three times actual damages plus the violator's profits, or statutory damages of $100 a day or $10,000, whichever is higher. The award is discretionary: the statute says the court "may" assess these damages. The suit must be filed within two years after the person first had a reasonable opportunity to discover the violation.
MCDPA Penalties
The MCDPA is enforced exclusively by the Minnesota Attorney General. Minn. Stat. Section 325M.20, paragraph (d), states that nothing in the Act establishes a private right of action. Paragraph (c) makes a controller or processor that violates the Act "subject to an injunction and liable for a civil penalty of not more than $7,500 for each violation."
The Act's 30-day cure period no longer exists. Section 325M.20(a) originally required the Attorney General to send a warning letter identifying the alleged violations and to wait 30 days for a cure before suing, but that paragraph ends with the sentence "This paragraph expires January 31, 2026." Since that date the Attorney General may bring a civil enforcement action under paragraph (b) directly, with no warning letter and no cure window.
Employer and Workplace Recording Rules
Minnesota Employer Obligations
Minnesota employers can lawfully record workplace meetings under the one-party consent framework, provided that at least one party to the conversation consents. An employer representative who participates in the meeting and authorizes an AI recording tool satisfies this requirement.
However, best practices for Minnesota employers go beyond the minimum legal requirement. Providing written notice to employees about AI recording and monitoring policies promotes transparency. Documenting monitoring practices in employee handbooks establishes clear expectations. Specifying the scope and purpose of AI recording helps demonstrate that recording serves a legitimate business purpose. These are practice points rather than MCDPA duties, since the Act's employment exclusion means employees generally cannot invoke consumer rights against a workplace recording.

Video Surveillance
Minnesota permits employer video surveillance in areas where employees do not have a reasonable expectation of privacy, such as common workspaces, entrances, exits, and production floors. A camera in a restroom, locker room, or other private area is a crime under Minn. Stat. Section 609.746 when used with intent to capture someone's intimate parts without consent, so employers should keep cameras out of those areas. Audio recording through surveillance systems is subject to the wiretap statute.
Digital Monitoring
Minnesota employers may monitor company email and internet usage without explicit employee consent if the employer owns the systems and has communicated monitoring practices. AI tools that analyze workplace communications (such as Slack messages or email threads) fall under the wiretap statute's one-party consent framework. The MCDPA generally adds nothing here, because data collected in the course of someone acting as an employee or contractor, and used solely within that role, is excluded from the Act by Section 325M.12, subdivision 2(a)(13).
Multi-State Considerations
When Minnesota employees participate in meetings with colleagues in all-party consent states (such as California, Illinois, or Massachusetts), courts have not settled which state's law governs. Some courts have applied the law of the place where the recording was made (Commonwealth v. Larrison in Pennsylvania; Ditech Financial v. Buckles in Nevada, 2017), while the California Supreme Court in Kearney v. Salomon Smith Barney (2006) held that California law governs such calls going forward, though it applied Georgia law to the company's past conduct and denied damages. Minnesota employers with distributed workforces should adopt a universal disclosure policy, announcing AI recording at the start of every meeting regardless of participants' locations. This approach eliminates the need to assess each participant's state law.
Federal Law and Minnesota's Framework
Alignment with Federal Standards
Minnesota's one-party consent framework aligns with the federal Wiretap Act (18 U.S.C. Section 2511), which also follows a one-party consent standard with the same criminal-or-tortious-purpose limit (18 U.S.C. 2511(2)(d)). Federal penalties for wiretap violations include up to 5 years in prison and fines up to $250,000 for individuals.
Both state and federal law can apply to the same recording. An AI meeting recording that violates Minnesota law (for example, one made without any party's consent) could also violate federal law. In practice, prosecutors typically pursue charges under whichever statute provides the strongest case.
The ECPA and AI Meeting Tools
The federal Electronic Communications Privacy Act (ECPA) extends wiretap protections to electronic communications, including video calls and virtual meetings. The Otter.ai plaintiffs brought a federal Wiretap Act claim, and in August 2026 the court let it proceed past a motion to dismiss on the theory that training Otter's own AI models on meeting conversations could be a tortious purpose that defeats one-party consent. That is a pleading-stage ruling, not a finding that Otter broke the law.

More Minnesota Laws
Explore other Minnesota law topics on Recording Law:
- Minnesota Recording Laws
- Minnesota Data Privacy Laws
- Minnesota AI Laws
- Minnesota Alimony Laws
- Minnesota At-Will Employment Laws
- Minnesota Car Accident Laws
- Minnesota Car Seat Laws
- Minnesota Child Custody Laws
- Minnesota Child Support Laws
- Minnesota Common Law Marriage Laws
- Minnesota Deepfake Laws
- Minnesota Divorce Laws
- Minnesota Dog Bite Laws
- Minnesota Emancipation Laws
- Minnesota Expungement Laws
- Minnesota Hit and Run Laws
- Minnesota Landlord-Tenant Laws
- Minnesota Lemon Laws
More Minnesota Recording & Privacy Laws
More Minnesota Laws
- Minnesota Data Privacy Laws
- Minnesota Deepfake Laws
- Minnesota Employee Monitoring Laws
- Minnesota Recording Laws
Frequently Asked Questions
Is it legal to record a meeting with an AI notetaker in Minnesota without telling everyone?
Generally, yes, if you are a participant in the meeting. Minnesota is a one-party consent state under Minn. Stat. Section 626A.02, so a meeting participant who activates an AI recording tool like Otter.ai or Fireflies.ai does not need to notify or obtain consent from other attendees, as long as that participant is genuinely part of the conversation, unless the recording is made for a criminal or tortious purpose.
Can an AI bot record a Minnesota meeting if the person who set it up isn't actually there?
This scenario is legally risky. Minnesota's one-party consent exception requires that a consenting party actually be a party to the communication. If an AI tool is configured to join and record a meeting on the account holder's calendar while that account holder does not attend, the account holder's own consent does not count, and unless another participant consents, the recording likely does not qualify for the one-party consent exception under Section 626A.02. Whether attendees who see the bot and keep talking have impliedly consented is not settled.
What are the penalties for illegally recording a conversation in Minnesota?
Unlawful interception, disclosure, or use of an intercepted communication is a felony under Minnesota's wiretap statute, punishable by up to 5 years in prison, a fine of up to $20,000, or both. Victims can also sue under Section 626A.13, where the court may award the greater of triple actual damages plus the violator's profits or statutory damages of $100 a day or $10,000, plus punitive damages in appropriate cases and attorney fees, within two years of having a reasonable opportunity to discover the violation.
Does Minnesota's new privacy law (MCDPA) apply to AI meeting recording tools?
Less often than people assume. The Minnesota Consumer Data Privacy Act was enacted in 2024 and took effect July 31, 2025, and it applies to businesses that control or process personal data of 100,000 or more Minnesota consumers annually, or 25,000 or more consumers if the business derives over 25 percent of gross revenue from selling personal data. The bigger limit is who counts as a consumer. Section 325M.11 defines a consumer as a Minnesota resident acting only in an individual or household context and expressly excludes a person acting in a commercial or employment context, and Section 325M.12, subdivision 2(a)(13), excludes data collected while someone is acting as an employee or contractor if it is used solely within that role. Attendees of an ordinary work meeting recorded by an employer's AI notetaker therefore generally have no MCDPA rights over that recording. Where the Act does apply, it is enforced only by the Minnesota Attorney General, with civil penalties of up to $7,500 per violation, and its 30 day warning letter and cure step expired January 31, 2026.
Is it always legal to record a Minnesota meeting as long as one person consents?
Not in every case. Minnesota's one-party consent exception does not apply if the recording is made for the purpose of committing a criminal or tortious act, such as blackmail or stealing trade secrets. It is also worth noting that if a Minnesota meeting includes participants located in an all-party consent state, such as Illinois or Massachusetts, courts have not settled which state's law governs that meeting, so telling everyone is the safe practice.
Updates
Corrected the description of Kearney v. Salomon Smith Barney (California law applied only going forward), added the criminal-or-tortious-purpose limit to the summary answers and tool table, reworded the absent-account-holder scenario as a risk with open questions, and stated the intent element for workplace cameras in private areas.
We corrected this page to explain that Minnesota's one-party consent rule does not protect a recording made for a criminal or tortious purpose, which is the theory a federal court let proceed against Otter.ai in August 2026; fixed the description of Ambriz v. Google and its October 2026 dismissal; corrected the civil damages rule under Section 626A.13 (discretionary, triple damages or statutory damages, two-year deadline); replaced a 'strictest law governs' rule with the unsettled conflict-of-laws picture; and removed an unsupported ranking of Minnesota's penalties.
Independently fact-checked against the cited primary sources; governing law re-checked for recent changes
Corrected the Minnesota Consumer Data Privacy Act discussion: the Act was enacted in 2024 and effective July 31, 2025, its 30-day warning-letter and cure step expired January 31, 2026, its civil penalty is up to $7,500 per violation, and it does not give consumer rights to people acting in a commercial or employment context, so participants in an ordinary work meeting recorded by an employer AI notetaker are generally outside it.
Added the second MCDPA applicability threshold (25,000+ consumers with over 25% of revenue from data sales).
Independently fact-checked against the cited primary sources; governing law re-checked for recent changes
Removed a fabricated 'journalist exception' to Minnesota's wiretap statute -- Minn. Stat. 626A.02 Subd. 2(a)-(g) contains no news-reporting or journalism carve-out.
Governing law re-checked for recent changes
Reviewed and approved by an editor
The Law Behind This Article
This article rests on the statutory provisions below, held in our own legal record and retrieved from the official source. Tap a section to read the operative text.
Minnesota Statutes, Chapter 626A: WIRE, ELECTRONIC, OR ORAL COMMUNICATIONS; INTERCEPTION
§ 626A.02INTERCEPTION AND DISCLOSURE OF WIRE, ELECTRONIC, OR ORAL COMMUNICATIONS PROHIBITEDIn forcecited in 19 of our articles
Subdivision 1. Offenses. Except as otherwise specifically provided in this chapter any person who: (1) intentionally intercepts, endeavors to intercept, or procures any other person to intercept or endeavor to intercept, any wire, electronic, or oral communication; (2) intentionally uses, endeavors to use, or procures any other person to use or endeavor to use any electronic, mechanical, or other device to intercept any oral communication when: (i) such device is affixed to, or otherwise transmits a signal through, a wire, cable, or other like connection used in wire communication; or (ii) such device transmits communications by radio, or interferes with the transmission of such communication; (3) intentionally discloses, or endeavors to disclose, to any other person the contents of any wire, electronic, or oral communication, knowing or having reason to know that the information was obtained through the interception of a wire, electronic, or oral communication in violation of this subdivision; or (4) intentionally uses, or endeavors to use, the contents of any wire, electronic, or oral communication, knowing or having reason to know that the information was obtained through the…
Official text (excerpt) · last checked 2026-09-23 · Read the full text in our law library · Verify at revisor.mn.gov
Cited in 20 court opinions in our collectionLatest citing opinion in our collection: 2025
In the courts (editorial summary, independently checked):Copeland v. Hubbard Broadcasting, Inc. (1995) applied the 626A.02 party exemption, finding a secret recording made for commercial newsgathering was not intercepted for the purpose of a tortious act. State v. Page (1986) held an officer's use of a regular telephone extension in the ordinary course of duty was not an interception.
Opinions citing this section in our collection:
- Copeland v. Hubbard Broadcasting, Inc. (Court of Appeals of Minnesota 1995, 526 N.W.2d 402)“…l to the federal wiretapping statutes. Compare Minn.Stat. § 626A.02, subd. 1 (1992), with 18…”
- State v. Page (Court of Appeals of Minnesota 1986, 386 N.W.2d 330)“…g rule applies. See 18 U.S.C. § 2511 (1982); Minn.Stat. § 626A.02 (1984). The federal rule makes it unlaw…”
- State v. Olkon (Supreme Court of Minnesota 1980, 299 N.W.2d 89)✓An undercover deputy posing as an injury client taped his calls and office meetings with a lawyer later convicted of attempted theft by swindle; the court rejected suppression, holding one party's consent meant no warrant was needed, citing the statute's consent exception.
Identified automatically from the court opinions citing this section — not a ranking of which case controls.
Also relied on in: Minnesota Smart Glasses Recording Laws 2026, US Recording Laws by State (2026): All 50 States Explained, One-Party Consent States: Complete 2026 Guide
§ 626A.13CIVIL REMEDIESIn forcecited in 9 of our articles
Subdivision 1. In general. Except as provided in section 2511 (2)(a)(ii) of title 18 of the United States Code, a person whose wire, oral, or electronic communication is intercepted, disclosed, or intentionally used in violation of this chapter may in a civil action recover from the person or entity that engaged in that violation relief as may be appropriate. Subd. 2. Relief. In an action under this section, appropriate relief includes: (1) temporary and other equitable or declaratory relief as may be appropriate; (2) damages under subdivision 3 and punitive damages in appropriate cases; and (3) a reasonable attorney's fee and other litigation costs reasonably incurred. Subd. 3. Computation of damages.
Official text (excerpt) · last checked 2026-07-29 · Read the full text in our law library · Verify at revisor.mn.gov
Cited in 3 court opinions in our collectionLatest citing opinion in our collection: 1996
Opinions citing this section in our collection:
- Molenaar v. United Cattle Co. (Court of Appeals of Minnesota 1996, 553 N.W.2d 424)“…upp.) (false reports of maltreatment of vulnerable adults); Minn.Stat. § 626A.13, subd. 2(2) (1994) (wiretapping). [2]…”
- State v. Monsrud (Supreme Court of Minnesota 1983, 337 N.W.2d 652)“…338 A.2d 284 (1975). We decline to follow it. [4] Minn.Stat. § 626A.13 (1982), provides: Any person whose w…”
- American Computer Trust Leasing v. Jack Farrell Implement Co. (District Court, D. Minnesota 1991, 763 F. Supp. 1473)“…In Count VII, defendants seek treble damages pursuant to Minn.Stat. § 626A.13 for the alleged violation of Minn.Stat.…”
Identified automatically from the court opinions citing this section — not a ranking of which case controls.
Also relied on in: Minnesota Recording Laws (2026): One-Party Consent Rules, Minnesota Audio Recording Laws: One-Party Consent Rules and Penalties, Minnesota Phone Call Recording Laws: One-Party Consent and Interstate Rules
United States Code Title 18
§ 2511Interception and disclosure of wire, oral, or electronic communications prohibitedIn forcecited in 441 of our articles
Except as otherwise specifically provided in this chapter any person who— intentionally intercepts, endeavors to intercept, or procures any other person to intercept or endeavor to intercept, any wire, oral, or electronic communication; intentionally uses, endeavors to use, or procures any other person to use or endeavor to use any electronic, mechanical, or other device to intercept any oral communication when— such device is affixed to, or otherwise transmits a signal through, a wire, cable, or other like connection used in wire communication; or such device transmits communications by radio, or interferes with the transmission of such communication; or such person knows, or has reason to know, that such device or any component thereof has been sent through the mail or transported in interstate or foreign commerce; or such use or endeavor to use (A) takes place on the premises of any business or other commercial establishment the operations of which affect interstate or foreign commerce; or (B) obtains or is for the purpose of obtaining information relating to the operations of any business or other commercial establishment the operations of which affect interstate or foreign…
Official text (excerpt) · last checked 2026-09-17 · Read the full text in our law library · Verify at uscode.house.gov
Cited in 2,045 court opinions in our collectionLatest citing opinion in our collection: 2026
In the courts (editorial summary, independently checked):Griggs-Ryan v. Smith (1990) applied the Section 2511(2)(d) prior-consent exception, treating a tenant repeatedly told that all incoming calls were taped as having impliedly consented. United States v. United States District Court (1972) read the then-current Section 2511(3) as conferring no presidential surveillance power.
Opinions citing this section in our collection:
- Mitchell v. Forsyth (Supreme Court of the United States 1985, 472 U.S. 511)✓The Attorney General authorized a warrantless 1970 national security wiretap that caught the plaintiff's calls; the Court held the since-repealed Section 2511(3) disclaimer left the tap lawful under Title III, and that Mitchell had qualified immunity.
- United States v. United States District Court for the Eastern District of Michigan (Supreme Court of the United States 1972, 407 U.S. 297)✓The Attorney General approved warrantless wiretaps on members of a domestic group accused of bombing a CIA office; the Court read Section 2511(3) as a congressional disclaimer conferring no surveillance power, then held the Fourth Amendment required prior judicial approval.
- Forsyth v. Barr (Court of Appeals for the Fifth Circuit 1994, 19 F.3d 1527)✓Dallas police used, in an internal affairs probe of an officer, calls private parties allegedly intercepted illegally; assuming that was unlawful, the Fifth Circuit held Section 2517(1) and (2) allowed the disclosure and use, defeating the Section 2511(1)(c) and (d) claims.
Identified automatically from the court opinions citing this section — not a ranking of which case controls.
Also relied on in: Can an Employer Record Conversations Without Consent? (2026), Can I Record My Boss Harassing Me? State-by-State Legal Guide (2026), Can I Sue Someone for Recording Me on Private or Public Property?
Minnesota Statutes, Chapter 325M: CONSUMER DIGITAL AND DATA PRIVACY
§ 325M.11DEFINITIONSIn forcecited in 3 of our articles
(a) For purposes of sections 325M.10 to 325M.21, the following terms have the meanings given. (b) "Affiliate" means a legal entity that controls, is controlled by, or is under common control with another legal entity. For purposes of this paragraph, "control" or "controlled" means: ownership of or the power to vote more than 50 percent of the outstanding shares of any class of voting security of a company; control in any manner over the election of a majority of the directors or of individuals exercising similar functions; or the power to exercise a controlling influence over the management of a company. (c) "Authenticate" means to use reasonable means to determine that a request to exercise any of the rights under section 325M.14, subdivision 1, paragraphs (b) to (h), is being made by or rightfully on behalf of the consumer who is entitled to exercise the rights with respect to the personal data at issue. (d) "Biometric data" means data generated by automatic measurements of an individual's biological characteristics, including a fingerprint, a voiceprint, eye retinas, irises, or other unique biological patterns or characteristics that are used to identify a specific individual.
Official text (excerpt) · last checked 2026-07-29 · Read the full text in our law library · Verify at revisor.mn.gov
Also relied on in: Minnesota Workplace Recording Laws: Employee and Employer Rights, Minnesota Biometric Privacy Laws: Collection, Consent & Penalties (2026)
§ 325M.12SCOPE; EXCLUSIONSIn forcecited in 6 of our articles
Subdivision 1. Scope. (a) Sections 325M.10 to 325M.21 apply to legal entities that conduct business in Minnesota or produce products or services that are targeted to residents of Minnesota, and that satisfy one or more of the following thresholds: (1) during a calendar year, controls or processes personal data of 100,000 consumers or more, excluding personal data controlled or processed solely for the purpose of completing a payment transaction; or (2) derives over 25 percent of gross revenue from the sale of personal data and processes or controls personal data of 25,000 consumers or more. (b) A controller or processor acting as a technology provider under section 13.32 shall comply with sections 13.32 and 325M.10 to 325M.21, except that when the provisions of section 13.32 conflict with sections 325M.10 to 325M.21, section 13.32 prevails. Subd. 2. Exclusions.
Official text (excerpt) · last checked 2026-07-29 · Read the full text in our law library · Verify at revisor.mn.gov
Also relied on in: Minnesota Data Privacy Laws: Consumer Rights Guide (2026), Minnesota MCDPA Compliance Checklist (Minn. Stat. 325M), What Is the Minnesota Consumer Data Privacy Act (MCDPA)?
§ 325M.14CONSUMER PERSONAL DATA RIGHTSIn forcecited in 13 of our articles
Subdivision 1. Consumer rights provided. (a) Except as provided in sections 325M.10 to 325M.21, a controller must comply with a request to exercise the consumer rights provided in this subdivision. (b) A consumer has the right to confirm whether or not a controller is processing personal data concerning the consumer and access the categories of personal data the controller is processing. (c) A consumer has the right to correct inaccurate personal data concerning the consumer, taking into account the nature of the personal data and the purposes of the processing of the personal data. (d) A consumer has the right to delete personal data concerning the consumer. (e) A consumer has the right to obtain personal data concerning the consumer, which the consumer previously provided to the controller, in a portable and, to the extent technically feasible, readily usable format that allows the consumer to transmit the data to another controller without hindrance, where the processing is carried out by automated means.
Official text (excerpt) · last checked 2026-08-28 · Read the full text in our law library · Verify at revisor.mn.gov
Also relied on in: Cookie Banner Requirements: US & EU Rules (2026), How to Request Your Personal Data: US Privacy Rights by State, How to Opt Out of Data Brokers (2026)
§ 325M.20ATTORNEY GENERAL ENFORCEMENTIn forcecited in 6 of our articles
(a) In the event that a controller or processor violates sections 325M.10 to 325M.21, the attorney general, prior to filing an enforcement action under paragraph (b), must provide the controller or processor with a warning letter identifying the specific provisions of sections 325M.10 to 325M.21 the attorney general alleges have been or are being violated. If, after 30 days of issuance of the warning letter, the attorney general believes the controller or processor has failed to cure any alleged violation, the attorney general may bring an enforcement action under paragraph (b). This paragraph expires January 31, 2026. (b) The attorney general may bring a civil action against a controller or processor to enforce a provision of sections 325M.10 to 325M.21 in accordance with section 8.31. If the state prevails in an action to enforce sections 325M.10 to 325M.21, the state may, in addition to penalties provided by paragraph (c) or other remedies provided by law, be allowed an amount determined by the court to be the reasonable value of all or part of the state's litigation expenses incurred.
Official text (excerpt) · last checked 2026-07-29 · Read the full text in our law library · Verify at revisor.mn.gov
Also relied on in: Minnesota MCDPA Consumer Rights (Minn. Stat. 325M.14)
Explore the law
This article also draws on these acts and chapters (opening at their first section): Minnesota Statutes, Chapter 626A: WIRE, ELECTRONIC, OR ORAL COMMUNICATIONS; INTERCEPTION § 626A.01 (DEFINITIONS)
Related law for further reading — not part of this article’s citations.
Sources and References
- Minn. Stat. Section 626A.02 - Interception and Disclosure of Communications(revisor.mn.gov).gov
- Minnesota Consumer Data Privacy Act - Attorney General Announcement(ag.state.mn.us).gov
- Minnesota Statutes Chapter 626A - Full Text(revisor.mn.gov).gov
- Minnesota Consumer Data Privacy Act - Chapter 325M(revisor.mn.gov).gov
- In re Otter.AI Privacy Litigation, N.D. Cal., No. 5:25-cv-06911 (docket; formerly Brewer v. Otter.ai)(courtlistener.com)
- Ambriz v. Google - AI Wiretapping Ruling (Courthouse News, 2025)(courthousenews.com)
- 18 U.S.C. Section 2511 - Federal Wiretap Act(law.cornell.edu)
- AI Meeting Assistants Legal Risks (National Law Review, 2025)(natlawreview.com)
- Minn. Stat. Section 325M.20 - Attorney General Enforcement (cure period expired January 31, 2026; $7,500 per violation)(revisor.mn.gov)
- Minn. Stat. Section 325M.11 - MCDPA Definitions (consumer excludes commercial or employment context)(revisor.mn.gov)
- Minn. Stat. Section 325M.12 - MCDPA Scope and Exclusions (employment and contractor data)(revisor.mn.gov)
- Minn. Stat. Section 325M.14 - MCDPA Consumer Rights (profiling and automated decisions)(revisor.mn.gov)