Last updated 2026-07-10

TL;DR
Maryland is an all-party consent state under Md. Code Ann. § 10-402. Everyone on a call must consent before you record. Criminal penalties reach 5 years in prison and a $10,000 fine. Civil damages run up to $10,000 per violation. If you record sales or compliance calls, you need disclosed consent from every participant before you hit record.
What is Maryland's phone call recording law?
Maryland's wiretapping and surveillance statute lives at Md. Code Ann., Courts and Judicial Proceedings § 10-402 [1]. It makes it a crime to willfully intercept, record, or disclose the contents of any wire, oral, or electronic communication without the consent of all parties. That word "all" is the one that catches people.
Most states use a one-party consent rule. If you're on the call, you can record it without telling anyone else. Maryland is not one of those states. It sits in the stricter category alongside Oregon, California, Illinois, and Pennsylvania. Oregon requires all-party consent under ORS 165.540 [6], so if your sales team records across state lines into Oregon, you carry the same exposure you do with Maryland. Michigan requires all-party consent under MCLA 750.539c [7], but Michigan courts have read the statute a bit more narrowly than Maryland courts read theirs.
The Maryland statute defines "intercept" broadly. It covers acquiring contents through electronic, mechanical, or other devices. A call recorder attached to your VoIP stack counts. So does a cloud dialer that captures audio, or a smartphone app recording in the background. All of them are devices under the statute.
Here's the single most important practical point. Consent must come before the recording starts. A disclosure that rolls out after you've already begun capturing audio does not satisfy the statute.
Is Maryland a one-party or two-party consent state?
Maryland is an all-party consent state, which functions the same as two-party consent when exactly two people are on a call [1]. The "two-party" label gets misleading on conference calls, though. With three or more participants, every single person must consent, more than a second party.
Here is how the categories break down across the states most relevant to outbound sales teams:
| State | Consent standard | Key statute |
|---|---|---|
| Maryland | All-party | Md. Code Ann. § 10-402 |
| Oregon | All-party | ORS 165.540 |
| Pennsylvania | All-party | 18 Pa. C.S. § 5703 |
| California | All-party | Cal. Penal Code § 632 |
| Michigan | All-party (two-party) | MCLA 750.539c |
| Texas | One-party | Tex. Penal Code § 16.02 |
| New York | One-party | NY Penal Law § 250.00 |
| Georgia | One-party | O.C.G.A. § 16-11-62 |
| Federal (baseline) | One-party | 18 U.S.C. § 2511 |
Federal law under 18 U.S.C. § 2511(2)(d) allows one-party consent, but states can and do set stricter standards [2]. When a stricter state law applies, you follow that state law. For a Maryland resident receiving your recorded call, Maryland law applies even if your business sits in a one-party state.
Oregon mirrors Maryland's severity closely. Michigan uses similar language, but Michigan courts have applied it in ways that sometimes look more lenient than Maryland's approach. Betting your compliance program on that distinction is a bad idea.
For a broader comparison of how states diverge, see the telephone call recording laws overview on LeadCompliant.
What are the penalties for illegal call recording in Maryland?
The criminal penalties under Md. Code Ann. § 10-402 are not trivial. A violation is a felony punishable by up to five years in prison and a fine of up to $10,000 [1]. That is per violation, not a total cap on an investigation.
On the civil side, Md. Code Ann. § 10-410 lets any person whose communication was intercepted sue [3]. They can recover the greater of actual damages or $100 per day for each day of violation, with a statutory floor of $1,000, plus punitive damages if the conduct was willful or intentional, plus attorney's fees and court costs. The attorney's fee provision is what makes these cases attractive to plaintiffs' lawyers even when actual damages are tiny.
Maryland's civil remedy does not require the plaintiff to prove economic harm. You recorded their call without consent. That is the violation. The suit follows from that fact alone.
The statute of limitations for civil wiretapping claims is generally three years under Maryland's general civil statute, though courts have sometimes analyzed the issue differently for privacy tort claims. If you're on the receiving end of a demand letter, check with Maryland-licensed counsel before assuming you know the deadline.
Federal wiretapping claims under 18 U.S.C. § 2520 can pile on top of state claims [10]. A single recorded call can generate parallel state and federal exposure. That stacking dynamic is why compliance teams should treat Maryland the way they treat California in their call recording policies.
How does consent actually work for recorded sales calls in Maryland?
Consent under § 10-402 must be knowing and voluntary [1]. The statute does not prescribe an exact format, but prosecutors and courts look for evidence that the other party understood the call might be recorded and continued anyway.
The most defensible method for outbound sales calls is a verbal disclosure at the very start of the call, before any recording begins. Something like: "This call may be recorded for quality and compliance purposes. By continuing this call, you consent to the recording." If the person stays on the line after that, Maryland courts generally treat continued participation as implied consent. That consent is legally stronger when you pause and give them a realistic chance to hang up.
Written consent works too. If your outbound leads submitted a form or signed an agreement that included a call recording disclosure, that written consent travels with the contact record and covers later recorded calls. The disclosure has to be clear and conspicuous, though. Burying it in a terms-of-service block under six layers of scroll is not the unambiguous consent Maryland's statute contemplates.
Things that do not count as consent: calling someone and recording with no disclosure, relying on a disclosure given to a different company that later sold you the lead, and assuming that because a lead gave TCPA consent to be called they also consented to be recorded. TCPA consent and state recording consent are legally separate [4].
For a deeper look at what consent requires across call types, the consent and opt-in fundamentals article covers how courts have drawn that line.
Does Maryland law apply when one party is outside the state?
This is one of the harder questions in call recording compliance, and courts have not produced a perfectly uniform answer. The general rule: if a Maryland resident is a party to the call, Maryland's all-party consent statute applies regardless of where the recording party sits [1]. Several Maryland courts and prosecutors have taken this position, and it matches how California courts have applied their own all-party statute in interstate situations.
The safe approach, and what any compliance-focused team should adopt, is to apply the stricter of the two applicable state laws whenever there's any ambiguity about where the other party is located. If you don't know whether someone is in Maryland or Virginia (a one-party state), treat the call as Maryland. If you're calling into both states from the same dialer, apply the all-party disclosure to everyone.
This adds friction on calls. The alternative is picking the wrong law on a Maryland call and generating felony-level exposure. The math favors the disclosure.
Oregon creates the same interstate puzzle. ORS 165.540 applies when an Oregon resident is a party, and Oregon has a specific exemption structure for certain calls that Maryland does not replicate [6]. If your team calls into both Oregon and Maryland regularly, those differences matter for scripting.
For teams working Texas leads alongside Maryland leads, you're managing a split. See texas call recording laws for how that one-party framework differs.
What exceptions exist under Maryland's recording statute?
Maryland's § 10-402 carves out several specific exceptions [1]. Law enforcement acting under a court order is the obvious one, and it doesn't help commercial callers. The exceptions that actually matter for sales and compliance teams are these:
First, the consent exception, which is what every legitimate business relies on. If all parties consent, there is no violation.
Second, a limited exception for communications service providers who intercept in the ordinary course of business for things like network maintenance or billing records. This is narrow. It does not cover a third-party SaaS call recorder sitting on top of your VoIP system.
Third, providers of electronic communication services may intercept where necessary to protect the rights or property of the service provider. Again, very narrow.
There is no Maryland exception for one-party consent. There is no "business purpose" exception that lets commercial entities record without consent. There is no exception for calls made entirely within a corporate enterprise. If two employees at a Maryland company call each other and one records without the other's knowledge, that is still a potential § 10-402 violation. The statute is that broad.
The "readily accessible to the general public" exception applies to unencrypted radio communications, not telephone calls. Some people think this creates an opening for VoIP calls. It does not.
How should outbound sales teams set up call recording compliance for Maryland calls?
The operational answer is simpler than the legal background makes it sound. You need four things working together.
First, identify Maryland numbers. Area codes 301, 240, and 410 are Maryland's primary codes. 443 is also Maryland. Numbers with those area codes get flagged in your dialer as all-party consent required. Remember that number portability means area code is a hint, not a guarantee, so if you have state data on the contact record, use it.
Second, pre-call disclosure. Your call script starts with a clear recording disclosure before any real conversation begins. Record the disclosure itself as part of the audio so you have proof it was given. Some dialers play a recorded disclosure at the start of the call automatically, which kills the human-error risk of a rep skipping it.
Third, a consent log. Your CRM or compliance system should record that the disclosure was made, when it was made, and that the call continued afterward. If you use written consent at lead capture, store that documentation tied to the contact record.
Fourth, call recording policies in writing. Have a document that names which states require all-party consent, states your disclosure script, and spells out what reps do if a prospect refuses recording. If someone withholds consent, your options are to proceed without recording or end the call. You cannot record anyway and hope nobody notices.
LeadCompliant's free TCPA compliance kit includes a multi-state consent disclosure script and a call recording policy template covering Maryland and the other all-party states. It saves a few hours of drafting if your team is building this from scratch.
For how these state rules interact with TCPA at the federal level, the tcpa law primer covers the federal floor your state policies sit on top of.
Does Maryland's recording law apply to text messages or only phone calls?
Maryland's § 10-402 applies to "wire, oral, or electronic communications," and that electronic communications category is broad [1]. Courts interpreting similar federal language under 18 U.S.C. § 2510 have included electronic messages in the definition of covered communications [2].
For outbound SMS marketing specifically, Maryland's recording law is less directly relevant. You're not recording a conversation. You're storing message content you're a party to. The framework that actually governs text marketing is TCPA plus Maryland's consumer protection law. But if you're screenshotting or logging incoming consumer text replies for documentation without any disclosure, that sits in a gray area worth reviewing with counsel.
Real-time interception of text messages by a third party would almost certainly fall under § 10-402's electronic communications prong, though there's less Maryland case law on that specific scenario than there is on phone call recording.
For text message compliance more broadly, the text message marketing facts article is the right next read, because Maryland phone recording law and SMS compliance pull from different regulatory frameworks even though both cover outbound contact.
How does Maryland's law compare to federal wiretapping law?
Federal wiretapping law under 18 U.S.C. § 2511 allows one-party consent for phone call recording [2]. Maryland requires all-party consent. When a state law is more protective of privacy than the federal baseline, the state law governs conduct within that state. There is no federal preemption argument that rescues you from Maryland's all-party requirement.
Section 2511(2)(d) says it is not unlawful for a person to intercept a communication where one party has given prior consent. But it also says that if the communication was intercepted for the purpose of committing a criminal or tortious act under state law, that exception does not apply. So if recording without all-party consent in Maryland is a crime under state law, the federal one-party exception does not shield you.
The FCC has separately addressed call recording in the TCPA context. FCC guidance clarifies that its TCPA regulations under 47 U.S.C. § 227 govern the initiation of calls and consent to automated or prerecorded messages, but the FCC has not preempted state call recording consent laws [4]. TCPA consent and Maryland recording consent stay independent requirements.
For a general overview of how the federal and state layers interact across recording scenarios, is it against the law to record phone calls walks through both frameworks.
What Maryland court cases have shaped how this law is applied?
Maryland courts have consistently applied § 10-402 strictly. In Fearnow v. C&P Telephone Co., the Maryland Court of Appeals confirmed that the statute requires consent of all parties and that interception without such consent is actionable regardless of the purpose behind the recording [5]. The court declined to read a broad business-purpose exception into the statute.
Maryland treats its wiretapping statute as a privacy protection, not a technical formality. That framing shows up across the case law, and it explains why courts reject the workarounds businesses keep trying.
Maryland courts have also grappled with whether intercepted recordings are admissible as evidence. The answer under § 10-405 is generally no. Evidence obtained in violation of the wiretapping statute is suppressed [9]. That matters for employers who record calls with employees without consent and then try to use those recordings in disciplinary proceedings.
The suppression remedy compounds the civil and criminal exposure. If you record without consent, you cannot use the recording defensively either. You've created a liability and lost the evidentiary benefit you were trying to capture.
What should you do if you receive a demand letter for illegal recording in Maryland?
Take it seriously immediately. A Maryland wiretapping demand letter usually arrives from a plaintiff's attorney who has identified that a call was recorded without proper consent. They'll cite § 10-402 and § 10-410, calculate statutory damages at $100 per day or the $1,000 minimum, add attorney's fees, and often attach a settlement demand.
Do not respond yourself. Retain Maryland-licensed counsel who handles privacy and telecommunications claims. Your first task is to verify whether the recording actually happened and whether consent was properly obtained. Pull the call records, the consent logs, and the disclosure scripts your team was using at the time of the alleged recording.
If you find a genuine gap, meaning calls were recorded without proper disclosure, settlement is often faster and cheaper than litigation. The attorney's fee provision in § 10-410 means even a small underlying violation can generate large legal bills once it goes to court [3].
If you believe consent was properly obtained, document your consent evidence carefully. A pre-call disclosure in the audio record plus a CRM log entry showing the call continued after disclosure is strong evidence. Written consent from a lead form is stronger still.
Fix your process immediately regardless of how the demand letter resolves. If one person caught a consent gap, others probably got the same treatment. Your exposure is proportional to how many calls got recorded without compliant disclosure.
Frequently asked questions
Is Maryland a two-party consent state for phone recordings?
Yes. Maryland requires all-party consent under Md. Code Ann. § 10-402, which in a standard two-person call means both parties must consent before recording. On calls with three or more participants, every person on the line must consent. Recording any Maryland resident's call without their knowledge is a felony, regardless of where the recording party is located.
What is the penalty for recording a phone call without consent in Maryland?
Criminal penalties run up to 5 years in prison and a $10,000 fine per violation. Civil damages under § 10-410 include the greater of actual damages or $100 per day of violation, with a minimum of $1,000, plus punitive damages for willful conduct and mandatory attorney's fees. The fee-shifting provision is what makes these cases economically viable for plaintiffs' lawyers.
Can I record a call in Maryland if I'm the one initiating it?
No. Being the party who placed the call gives you no special recording right under Maryland law. The all-party consent requirement applies to everyone on the call, including the person who dialed. You must disclose before recording and give the other party a realistic opportunity to decline.
How do I get valid consent to record a call under Maryland law?
Deliver a clear verbal disclosure at the very start of the call, before any recording begins, stating the call may be recorded. Give the other party a moment to object or disconnect. If they continue the call, that continuation constitutes implied consent. Written consent captured at a lead form or contract stage also works and is actually stronger evidence.
Does Maryland recording law apply if my business is in another state?
Yes, when a Maryland resident is a party to the call. Courts and prosecutors apply Maryland's all-party consent requirement based on where the participants are, not where the recording equipment sits. If you're calling Maryland-based consumers and recording without consent, you're exposed under Maryland law even if your office is in Texas or Florida.
How does Maryland's recording law compare to Oregon phone call recording laws?
Both Maryland and Oregon are all-party consent states, so the baseline requirement is the same: everyone on the call must consent before you record. Oregon's statute is ORS 165.540, Maryland's is Md. Code Ann. § 10-402. Oregon has specific exemptions for certain call types that Maryland does not mirror, so the operational details differ even though the consent standard matches.
How does Maryland law compare to Michigan law on recording phone calls?
Michigan also requires all-party consent under MCLA 750.539c. In practice Maryland courts have applied their statute broadly with few exceptions, while some Michigan case law has been applied more narrowly. That said, relying on a perceived flexibility difference in Michigan is risky. Both states are all-party consent states and both carry criminal exposure for non-compliant recording.
Can my employer record my work calls in Maryland without telling me?
No. Maryland's all-party consent requirement applies to employer-employee calls too. An employer recording employee calls without their knowledge or consent violates § 10-402 even within the same company. Many employers handle this by including call recording consent in employment agreements or onboarding documents, which constitutes advance written consent.
Are text messages covered by Maryland's recording law?
Maryland's statute covers wire, oral, and electronic communications, which is broad enough to include electronic messages in principle. For outbound SMS marketing, TCPA and consumer protection law are the more directly applicable frameworks. Real-time interception of text messages by third parties would almost certainly fall under the electronic communications prong of § 10-402.
Does TCPA consent cover call recording consent in Maryland?
No. These are separate legal requirements. TCPA consent under 47 U.S.C. § 227 governs whether you can call someone using an autodialer or send prerecorded messages. Maryland's § 10-402 governs whether you can record the conversation. A lead who consented to be called under TCPA has not automatically consented to being recorded. You need both.
Can illegally recorded calls be used as evidence in Maryland?
No. Section 10-405 of Maryland's Courts and Judicial Proceedings code suppresses evidence obtained in violation of the wiretapping statute. If you recorded a call without consent, you cannot use that recording defensively in litigation or disciplinary proceedings. You've created liability and lost the evidentiary benefit at the same time.
What area codes indicate a Maryland phone number?
Maryland's primary area codes are 301, 240, 410, and 443. A 667 area code also serves Maryland. Area code alone is not definitive proof of location due to number portability, but it's a reasonable first-pass signal for flagging calls that need all-party consent disclosure in your dialer.
Is there a Maryland-specific notice required for business call recording?
Maryland does not prescribe a word-for-word script. The requirement is that all parties consent before recording begins. A clear statement that the call may be recorded and the opportunity to object or disconnect satisfies the consent standard. Many compliance teams use a standardized opening disclosure and document it in their call recording policy.
How long does someone have to sue for illegal call recording in Maryland?
Maryland's general civil statute of limitations is three years for civil claims. For wiretapping claims specifically, courts analyze the limitations period under the nature of the privacy tort, and results can vary. If you receive a demand related to a recording that occurred more than three years ago, that's a potential defense worth raising with counsel, but do not assume the claim is time-barred without confirming the applicable period.
Sources
- Maryland General Assembly, Courts and Judicial Proceedings § 10-402: Maryland requires all-party consent to record telephone calls; violations are a felony punishable by up to 5 years imprisonment and a $10,000 fine
- U.S. Department of Justice, 18 U.S.C. § 2511 Federal Wiretap Act: Federal law allows one-party consent for call recording under 18 U.S.C. § 2511(2)(d), but states may impose stricter requirements
- Maryland General Assembly, Courts and Judicial Proceedings § 10-410: Civil damages for illegal recording in Maryland include the greater of actual damages or $100 per day, minimum $1,000, plus attorney's fees
- Fearnow v. C&P Telephone Co., Maryland Court of Appeals: Maryland courts have consistently applied § 10-402 strictly, requiring consent of all parties and rejecting broad business-purpose exceptions
- Oregon Legislative Assembly, ORS 165.540: Oregon requires all-party consent to record telephone calls under ORS 165.540, similar to Maryland's standard
- Michigan Legislature, MCLA 750.539c: Michigan law on recording phone calls requires all-party consent under MCLA 750.539c
- Electronic Privacy Information Center (EPIC), Wiretapping Laws by State: Comparison of state call recording consent laws showing which states require all-party versus one-party consent
- Maryland General Assembly, Courts and Judicial Proceedings § 10-405: Evidence obtained in violation of Maryland's wiretapping statute is suppressed and inadmissible
- U.S. Department of Justice, 18 U.S.C. § 2520 Civil Action for Wiretapping: Federal civil action for wiretapping under 18 U.S.C. § 2520 can be filed alongside state claims, creating parallel exposure