Last updated 2026-07-10

TL;DR
Minnesota follows one-party consent under Minn. Stat. § 626A.02, meaning you can record a phone call if you are a party to it, without telling the other person. Federal wiretapping law sets the same floor. But if you call someone in a two-party consent state, that state's stricter rule applies. Outbound sales teams still face TCPA exposure on top of state recording rules.
Is Minnesota a one-party or two-party consent state for recording calls?
Minnesota is a one-party consent state. Under Minnesota Statutes § 626A.02, it is unlawful to intercept a wire, oral, or electronic communication, but the statute carves out a clear exception: interception is permitted when one party to the communication has given prior consent. [1] If you are on the call, you can record it. You do not need to tell the other party.
The federal Wiretap Act (18 U.S.C. § 2511) sets the same one-party consent floor nationwide. [2] Minnesota mirrors the federal baseline rather than adding a stricter requirement, which puts it in the majority of U.S. states.
For context, roughly 38 states and D.C. use one-party consent. The rest, including California, Florida, Pennsylvania, Maryland, and Washington, require all-party consent. You can find a full breakdown in our guide to telephone call recording laws.
Here is the practical bottom line. A Minnesota-based sales rep recording her own outbound calls to other Minnesota residents is completely legal under state law, no disclosure required. The problems start when the call crosses state lines.
What does Minnesota Stat. § 626A.02 actually say?
The statute is part of Minnesota's version of the Uniform Electronic Surveillance Act. The core prohibition covers any person who intentionally intercepts, tries to intercept, or gets another person to intercept any wire, oral, or electronic communication. That is a crime. [1]
The consent exception in § 626A.02, subdivision 2(d) says it is not unlawful for "a person not acting under color of law 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 unless such communication is intercepted for the purpose of committing any criminal or tortious act."
Two things in that language matter for business teams. First, the exemption disappears if you are recording for a criminal or tortious purpose, so recording a competitor's confidential pitch and then using it against them in litigation could expose you even though you were on the call. Second, "prior consent" can be implicit from context in some readings, but you should not rely on implicit consent in a business setting. Written or verbal on-record consent is always safer.
Violating § 626A.02 is a felony in Minnesota, not a civil infraction. [1] The criminal exposure alone is reason to take the statute seriously.
What are the penalties for illegal call recording in Minnesota?
Criminal penalties under § 626A.02 can reach imprisonment of up to five years, a fine up to $10,000, or both for a first offense. [1] Minnesota also provides a civil remedy: any person whose wire, oral, or electronic communication is intercepted can sue for actual damages (but not less than $100 a day for each day of violation or $10,000, whichever is greater), punitive damages, and attorney fees. [3]
That $10,000 statutory floor per violation is the number that gets businesses in trouble. A single recorded call to someone who did not consent and who lives in a two-party consent state can trigger both that state's civil claims and a federal Wiretap Act claim. Stack those on top of each other and the exposure grows fast.
The federal Wiretap Act (18 U.S.C. § 2520) also allows civil suits with damages of the greater of actual damages or $100 per day (minimum $10,000 per violation) plus attorney fees, which mirrors what Minnesota provides. [2] You often face parallel liability under both frameworks.
For outbound sales teams, see also the recorded phone call laws overview, which covers how multi-state calls layer these exposures.
How does the one-party consent rule work when you call someone in another state?
This is where most businesses get caught. Minnesota's one-party consent rule governs calls where Minnesota law applies, but courts and regulators look at the law of the state where the other party is located when deciding which rule controls.
The majority rule in federal courts is that the stricter state's law applies when there is a conflict. So if your Minnesota sales team calls a prospect in California, Minnesota's permissive rule does not matter here. California's Penal Code § 632 does. [4] California requires all parties to consent, and California courts have been aggressive about enforcing that requirement.
Here are the states to train your team on before calling out:
| State | Consent required | Notes |
|---|---|---|
| California | All-party | Pen. Code § 632; statutory damages $5,000/violation |
| Florida | All-party | Fla. Stat. § 934.03 |
| Pennsylvania | All-party | 18 Pa. C.S. § 5703; see pa call recording laws |
| Maryland | All-party | Md. Code, Cts. & Jud. Proc. § 10-402; see maryland call recording laws |
| Washington | All-party | RCW 9.73.030 |
| Illinois | All-party | 720 ILCS 5/14-2 |
| Texas | One-party | Tex. Penal Code § 16.02; see texas call recording laws |
| New York | One-party | NY Penal Law § 250.00 |
| Georgia | One-party | O.C.G.A. § 16-11-62 |
| Arizona | One-party | A.R.S. § 13-3005 |
| Indiana | One-party | I.C. § 35-31.5-2-176 |
| Missouri | One-party | Mo. Rev. Stat. § 542.402 |
Missouri call recording laws are also one-party consent, so a Minnesota business calling Missouri prospects has no recording disclosure obligation under either state's law. But your CRM should still track where each prospect is located so your team automatically applies the right rule.
The safest operational decision for any team calling across state lines is simple: disclose the recording to everyone on every call. A brief "this call may be recorded" at the top costs you nothing and eliminates almost all legal risk no matter which state the prospect is in.
Does Minnesota law require you to tell callers they are being recorded?
No. Under Minnesota's one-party consent statute, disclosure to the other party is not a legal requirement when you are a party to the call. [1]
That said, there are at least three reasons a Minnesota business should disclose anyway.
First, as covered above, your prospect may be in a state that requires it. Second, if you work in a regulated industry (healthcare, financial services, debt collection), sector-specific rules may add their own disclosure requirements on top of state wiretapping law. The FDCPA, for instance, requires debt collectors to identify themselves, and some state AG guidance extends that to recording practices. Third, consent disclosure is a practical trust signal with customers. Plenty of outbound teams find that a straightforward "this call may be recorded for quality and training purposes" actually raises call completion rates because it signals professionalism.
If you do announce recording, do it at the very start of the call before any substantive conversation begins. Announcing it mid-call and then replaying the pre-announcement portion of the recording in litigation is a situation you do not want to explain to a judge.
How does TCPA compliance interact with Minnesota call recording rules?
The TCPA (47 U.S.C. § 227) and state recording laws are parallel frameworks that do not directly overlap, but both apply to outbound sales calls at the same time. [5]
TCPA governs whether you can make the call at all, using what equipment, and to whom. State recording law governs whether you can record the call once it is happening. A call can be perfectly legal under TCPA and still violate Minnesota's or another state's recording statute, or the other way around.
The FCC enforces TCPA violations, and fines run up to $1,500 per call for willful violations. [5] Meanwhile, a single improperly recorded call in California exposes you to $5,000 in statutory damages under California Penal Code § 632.7. These are additive risks.
For outbound teams using auto-dialers or pre-recorded messages, the TCPA consent requirements (written consent for marketing calls to cell phones) are the bigger daily compliance burden. But the recording question surfaces the moment you add call recording software to your stack. See our TCPA law overview for the full federal picture.
One practical note. If you use a third-party call recording service that stores recordings in the cloud, that vendor's terms of service and their data storage state may create extra considerations, though these are usually contractual rather than criminal.
Can employees record calls with their employer in Minnesota?
Yes, under the same one-party consent rule. An employee who is a party to a call with their employer or a manager can legally record that call without telling the employer, as long as the recording is not for a criminal or tortious purpose. [1]
This cuts both ways. Employers cannot assume their internal calls are safe from employee recording in Minnesota. HR teams running investigations or performance reviews by phone should understand that the employee on the other end may be recording.
Employers can address this contractually, through a workplace recording policy in the employee handbook that prohibits recording workplace conversations without consent. That policy creates an employment-law basis to discipline or terminate for violations, even though the recording itself may not be a crime under § 626A.02. Enforcing the policy through employment law is the practical lever, not the criminal statute.
For comparison, Georgia handles this the same way. A Georgia employee can record their own calls under O.C.G.A. § 16-11-62 without notifying the employer. See our piece on the georgia recording consent law group audio call for more on how group calls complicate that analysis.
Are there special rules for recording calls in Minnesota's regulated industries?
Yes. Minnesota's wiretapping statute sets the baseline, but sector regulators layer on more requirements.
Healthcare: providers subject to HIPAA must treat call recordings containing protected health information as PHI. Storage, access controls, and breach notification rules apply to the audio file, on top of the call itself. [6] A Minnesota clinic recording patient intake calls needs a business associate agreement with any third-party recording vendor.
Financial services: FINRA Rule 3110 requires broker-dealers to supervise electronic communications including recorded calls. [7] The Minnesota Department of Commerce can also examine recording practices for licensed financial services firms.
Debt collection: the FDCPA (15 U.S.C. § 1692 et seq.) does not explicitly require recording disclosure, but the CFPB's 2021 Debt Collection Rule tightened communication requirements. Some collectors add a recording disclosure to their mini-Miranda to reduce litigation surface area. [8]
Government contractors: federal contractors handling sensitive information may face NIST or agency-specific requirements about recording and storing communications.
The safest approach in any regulated industry is to treat the most restrictive applicable rule as your baseline, then work outward.
What should a Minnesota outbound sales team's call recording policy look like?
A workable policy has five elements.
1. Default disclosure. Open every recorded outbound call with a brief verbal announcement: "This call may be recorded." Train reps so it becomes automatic, no matter where the prospect is located. This satisfies all-party consent states and documents consent in the recording itself.
2. State-of-the-prospect tracking. Your CRM should store the prospect's state. Flag calls to all-party consent states (California, Florida, Pennsylvania, Maryland, Washington, Illinois, Connecticut, Michigan, New Hampshire, Montana, Oregon) for extra attention. Some teams route those calls through a separate call flow that includes a more explicit consent prompt.
3. Written policy document. Put your recording practices in writing, signed by all sales staff. This becomes evidence of good-faith compliance if litigation arises.
4. Vendor review. Confirm your call recording vendor stores data in a way that meets applicable data protection requirements. Review the BAA if any calls involve health information.
5. Retention schedule. Decide how long you keep recordings and document it. Minnesota has no specific call recording retention law for private businesses, but if recordings are relevant to a contract dispute they may become discoverable. A clear retention and deletion schedule beats an undefined one.
For teams building this from scratch, LeadCompliant's compliance kit includes a call recording policy template and a state consent lookup tool that flags two-party states in real time as you dial. It is a reasonable starting point if you want a documented baseline without building it by hand.
See also the general guide to is it against the law to record phone calls for a 50-state framing of the consent question.
How have courts interpreted Minnesota call recording cases?
Minnesota state courts have not produced a large volume of published call recording cases compared to California or Florida. That reflects the one-party consent rule, which makes most recordings lawful on their face.
The more common litigation angle in Minnesota has been federal Wiretap Act claims layered with state tort claims like invasion of privacy. Courts have generally held that recordings made by a party to the call are protected by the consent exception under both 18 U.S.C. § 2511(2)(d) and Minnesota § 626A.02. [2]
Cases involving third-party recording services have occasionally raised the question of whether the service itself is a "party" to the communication. Federal courts, including in the Eighth Circuit (which covers Minnesota), have generally held that passive recording services that store audio at the direction of a party do not count as independent interception under the Wiretap Act, though this analysis can be fact-specific. [9]
One area where Minnesota courts have been less settled: whether recording voicemails you leave for another person requires consent from that person when they listen to it later. The majority view is that voicemails are stored communications governed by the Stored Communications Act (18 U.S.C. § 2701) rather than the Wiretap Act's interception rules, which changes the analysis. [10] This is an edge case for most sales teams but worth knowing if your outreach involves recording and archiving voicemails left on others' systems.
Nobody has full data on private settlement rates for Minnesota recording claims specifically. The closest public indicator is PACER data showing that federal Wiretap Act cases in the Eighth Circuit resolve at settlement the large majority of the time, which matches national patterns.
How does Minnesota compare to neighboring states on call recording?
All of Minnesota's immediate neighbors use one-party consent, which simplifies cross-border call recording for regional businesses.
| State | Consent rule | Statute |
|---|---|---|
| Minnesota | One-party | Minn. Stat. § 626A.02 |
| Wisconsin | One-party | Wis. Stat. § 968.31 |
| Iowa | One-party | Iowa Code § 808B.2 |
| South Dakota | One-party | SDCL § 23A-35A-20 |
| North Dakota | One-party | N.D.C.C. § 12.1-15-02 |
| Missouri | One-party | Mo. Rev. Stat. § 542.402 |
For a Minnesota company selling regionally across the upper Midwest, the recording consent picture is simple. The complication arises when national outbound campaigns reach California, Florida, or Pennsylvania. That is the risk you need to operationalize.
Missouri call recording laws match Minnesota's approach: one party to the call can record without the other's knowledge, and the statute mirrors the federal Wiretap Act framework. Mo. Rev. Stat. § 542.402 makes unlawful interception a class E felony, the same general structure as Minnesota. [11]
What records should Minnesota businesses keep about their call recording practices?
Minnesota law does not impose a specific record-keeping mandate on private businesses for call recordings, unlike FINRA's three-year retention rule for broker-dealers or HIPAA's six-year requirement for medical records. [7][6]
For litigation preparedness, the practical standard is this: keep recordings long enough to cover your relevant statutes of limitations. The federal Wiretap Act civil claim has a two-year limitations period under 18 U.S.C. § 2520(e). [2] Minnesota does not have a separate shorter period for recording claims; general tort limitations of six years under Minn. Stat. § 541.05 could potentially apply to privacy torts. [12]
A sensible default for outbound sales call recordings: retain for two years minimum, then delete on a documented schedule unless a legal hold is in place. Put the retention policy in writing and train whoever manages your call recording platform on it.
If recordings are subpoenaed or become relevant to a regulatory inquiry, you need to show when recordings were made, who was on the call, and that your disclosure practices met applicable law. A good call logging system that ties recordings to CRM records and timestamps disclosure events is far more useful in that scenario than raw audio files alone.
Frequently asked questions
Does Minnesota require two-party consent to record a phone call?
No. Minnesota is a one-party consent state under Minn. Stat. § 626A.02. If you are a participant in the call, you can record it without informing the other party. Two-party (all-party) consent is required in states like California, Florida, and Pennsylvania, and those rules apply if your prospect is located in one of those states even if you are calling from Minnesota.
Is it a crime to record a phone call in Minnesota without telling the other person?
Not if you are a party to the call. Minnesota § 626A.02 exempts recordings made by a participant. Recording a call you are not part of, such as tapping someone else's line, is a felony punishable by up to five years in prison and a $10,000 fine. The distinction between recording your own call and intercepting someone else's call is the entire legal foundation here.
What happens if I record a call from Minnesota to a California customer?
California's all-party consent law (Penal Code § 632) likely applies because the other party is in California. You need to disclose the recording at the start of the call and get consent. Failure to do so exposes you to California's statutory damages of $5,000 per violation, plus potential federal Wiretap Act claims. Minnesota's permissive rule does not protect you from the stricter state where your prospect is located.
Can my employer record my work calls in Minnesota without telling me?
Yes, if the employer is a party to the call or has designated a party (such as a supervisor on the line). Minnesota's one-party consent rule covers employers recording business calls they are participating in. Employers should disclose recording practices in employee handbooks for trust and HR reasons, but there is no legal requirement to do so under Minnesota's wiretapping statute.
Does the TCPA affect call recording in Minnesota?
The TCPA (47 U.S.C. § 227) governs whether and how you can make the call, not whether you can record it. State wiretapping law governs recording. Both apply at the same time to outbound sales calls, so a call that is TCPA-compliant can still violate recording law if you record without proper consent, and vice versa. TCPA fines run up to $1,500 per willful violation, separate from any recording-law damages.
Is Missouri a one-party or two-party consent state for recording calls?
Missouri is a one-party consent state under Mo. Rev. Stat. § 542.402. A participant in a call can record it without notifying the other party. The statute makes illegal interception (recording calls you are not part of) a class E felony. For Minnesota businesses calling Missouri prospects, neither state requires recording disclosure, though announcing the recording is still best practice for cross-state compliance generally.
Can I use call recordings as evidence in a Minnesota court?
Yes, recordings made lawfully under the one-party consent exception are generally admissible. Courts look at whether the recording was made by a party to the communication and without an unlawful purpose. Recordings made in violation of § 626A.02, meaning without being a party and without consent, are excluded and can form the basis of a civil or criminal claim against the person who made them.
Do I need to disclose call recording in my outbound call script for Minnesota prospects?
Strictly speaking, no, not if you are calling Minnesota residents and you are a party to the call. But most compliance professionals recommend adding a brief disclosure anyway. It protects you if a Minnesota prospect moves to a two-party state, it signals professionalism, and it is documented consent in the recording itself if litigation arises. The disclosure costs about three seconds and eliminates nearly all legal risk.
How long should I keep call recordings in Minnesota?
Minnesota has no private-business retention mandate for call recordings. The federal Wiretap Act civil claim has a two-year limitations period, and Minnesota's general tort statute of limitations is six years. A practical default is two years minimum for sales recordings, six years if the call relates to a contract or dispute. Document your retention policy in writing and apply it consistently.
What is the civil penalty for illegally recording a call in Minnesota?
Under Minn. Stat. § 626A.13, a victim of illegal interception can sue for actual damages, but no less than $100 per day of violation or $10,000 total, whichever is greater. Punitive damages and attorney fees are also available. The federal Wiretap Act (18 U.S.C. § 2520) provides a parallel civil remedy with identical minimums, so plaintiffs can pursue both at once.
Does recording a voicemail I leave someone require consent in Minnesota?
Generally no. Voicemails you leave are communications you are initiating, and leaving a voicemail is not the same as intercepting a wire communication under the Wiretap Act or Minnesota § 626A.02. If you are asking about recording the voicemail the other party leaves you, that is also generally covered by your one-party consent as the intended recipient. The Stored Communications Act (18 U.S.C. § 2701) governs stored voicemails separately.
Can a third-party call recording service legally record my business calls in Minnesota?
Yes, if they are acting at the direction of a party to the call. Courts, including in the Eighth Circuit, have generally held that passive recording services storing audio on behalf of a call participant do not count as independent interception under the Wiretap Act. Make sure your vendor contract reflects this agency relationship and that you have obtained any consents required by the other party's state law before the vendor records.
Are there any Minnesota-specific data privacy rules that affect call recordings?
Minnesota does not yet have a consumer data privacy law equivalent to California's CCPA as of mid-2025, though the Minnesota Consumer Data Privacy Act (MCDPA) was signed into law in 2023 with provisions taking effect in stages. Businesses collecting call recordings that contain personal data should monitor MCDPA requirements around data subject rights and data minimization as implementation continues. [13]
What is the difference between Minnesota's wiretapping law and its eavesdropping law?
Minnesota § 626A.02 covers electronic interception of wire and oral communications, which includes phone calls. Minnesota also has separate criminal prohibitions on in-person eavesdropping under § 609.746, which covers recording private conversations in physical spaces without consent. Call recording for outbound sales is governed by § 626A.02, not § 609.746, though both statutes share the principle that secret interception without being a party is a crime.
Sources
- Minnesota Legislature, Minn. Stat. § 626A.02 (Minnesota Wire and Electronic Communications Interceptions): Minnesota is a one-party consent state; recording by a party to the communication is lawful; violations are a felony punishable by up to five years imprisonment and a $10,000 fine
- U.S. Department of Justice, 18 U.S.C. § 2511 and § 2520 (Federal Wiretap Act): Federal one-party consent exception; civil damages minimum of $10,000 or $100/day per violation; two-year civil statute of limitations
- Minnesota Legislature, Minn. Stat. § 626A.13 (Civil remedy for interception violations): Civil damages of not less than $100 per day of violation or $10,000, whichever is greater, plus punitive damages and attorney fees
- California Legislative Information, Penal Code § 632: California requires all-party consent for confidential communications; statutory damages of $5,000 per violation
- HHS, HIPAA Security Rule guidance: Call recordings containing PHI are subject to HIPAA storage, access control, and breach notification requirements; six-year record retention minimum
- FINRA, Rule 3110 (Supervision): FINRA Rule 3110 requires broker-dealers to supervise electronic communications including recorded calls; three-year retention standard applies
- CFPB, Debt Collection Rule (Regulation F) final rule 2021: CFPB's 2021 Debt Collection Rule tightened communication requirements for debt collectors under FDCPA
- U.S. Courts, Eighth Circuit Court of Appeals opinions database: Eighth Circuit (covering Minnesota) has generally held that passive third-party recording services acting at a party's direction do not constitute independent interception under the Wiretap Act
- Cornell Law School Legal Information Institute, 18 U.S.C. § 2701 (Stored Communications Act): Stored voicemails on third-party systems are governed by the Stored Communications Act, not the Wiretap Act's interception provisions
- Missouri Legislature, Mo. Rev. Stat. § 542.402 (Missouri wiretapping statute): Missouri is a one-party consent state; unlawful interception is a class E felony under Missouri law
- Minnesota Legislature, Minn. Stat. § 541.05 (Limitations of actions): Minnesota's general tort statute of limitations is six years
- Minnesota Legislature, Minnesota Consumer Data Privacy Act (HF 1189, 2023 session): Minnesota Consumer Data Privacy Act signed 2023 with provisions taking effect in stages; covers personal data collected in business contexts including call recordings