Video Surveillance Laws in Maryland for Security Teams

Video surveillance laws in Maryland create meaningful legal and operational risk for organizations that deploy camera networks. For teams that manage camera programs in the state, a disciplined review process can reduce exposure before routine deployment creates gaps that are harder to unwind.

Key Takeaways

• Maryland separates visual monitoring from recorded communications, so teams should treat camera configuration and recording settings as distinct compliance controls.
• Cameras are lowest risk when they observe shared business areas for documented protective purposes.
• Spaces associated with changing, restrooms, residences, and other private activities require heightened placement review.
• Programs that use analytics or identity-related templates need privacy controls and secure vendor terms with defined retention practices.

How Maryland Regulates Video Surveillance

Maryland separates silent video and audio interception from data handling obligations, so each area needs its own compliance review. The Maryland Wiretapping and Electronic Surveillance Act, Courts and Judicial Proceedings § 10-402, regulates audio interception. Criminal placement rules and data handling obligations require separate review before deployment.

Compliance reviews should determine whether the person observed is in a setting or activity where privacy would reasonably be expected.

Because these rules vary significantly from state to state, teams managing multi-state camera portfolios can compare requirements across jurisdictions in our state-by-state guide to video surveillance laws.

Silent Video vs. Audio Recording

The Maryland Wiretapping and Electronic Surveillance Act addresses wire, oral, and electronic communications. Camera placement requires a separate review. Silent video compliance therefore turns on camera location and intent.

§ 10-402 makes it unlawful to willfully intercept any wire, oral, or electronic communication, and the consent exception applies only when every party to the communication has agreed in advance. The requirement covers private conversations. A private oral conversation is one where a participant holds a reasonable expectation of privacy; telephone calls are treated separately as wire communications.

A camera with audio capture that records conversations without all-party consent creates felony exposure under § 10-402.

Where Cameras Are Permitted and Prohibited

Maryland's placement rules make retail dressing rooms and restrooms the highest-risk locations for camera review. Security teams should keep cameras out of those spaces unless counsel has confirmed a consent basis, and property ownership should not be treated as a defense.

Section 3-902 prohibits prurient-intent surveillance in private places. Those are rooms where a person can reasonably be expected to disrobe: dressing rooms, tanning rooms, bedrooms, restrooms, hotel rooms, and locker rooms. An amendment effective October 1, 2025 (HB 437) added residences to that list. Section 3-902 does not prohibit surveillance conducted without prurient intent to protect property, safeguard public safety, or prevent crime, or by a licensed security professional acting within the scope of that occupation. Security teams should not treat that exemption as a substitute for reviewing other visual surveillance offenses.

Security teams should also document residential fields of view as part of the same placement analysis. Common areas of multiunit dwellings and portions of a residence used for business purposes require their own field-of-view documentation.

Workplace Surveillance and Employee Monitoring

Employer video-only surveillance reviews generally derive from the criminal statutes above, the Wiretap Act, and federal labor law. For placement reviews, shared work areas generally present lower risk than private spaces because employees have less practical privacy in areas used by coworkers, visitors, or customers. Silent video for a documented protective purpose is lower risk in open work areas, including lobbies and parking lots. The prohibited-location rules still hold: no camera may cover employee restrooms, locker rooms, or changing areas, whatever the business justification.

Security teams should distinguish broad observation of shared work areas from targeted monitoring that moves toward a private or protected setting. A camera positioned to cover an entrance, loading dock, reception desk, or parking area presents a different risk profile from a camera that also captures the doorway of a locker room or the interior of a residence. Placement reviews should therefore look at the actual field of view, not just the device name or the area label in a video management system (VMS).

The National Labor Relations Act (NLRA) bars employers from using surveillance to monitor or chill protected activity such as wage discussions or organizing. Recording restrictions must be narrowly tied to specific confidentiality or privacy interests.

Notice, Signage, and Consent

For video-only surveillance in non-private areas, posted signage and advance notice are primarily risk controls under the statutes addressed here. Employer notice of potential surveillance can undermine an employee's claim to a reasonable expectation of privacy.

For audio, notice can establish implied consent. The Maryland Department of Information Technology's recording policy treats continued participation after notification of recording as implied consent. Implied consent must reach every party; recording is unlawful if even one participant has not consented. No signage cures surveillance the statutes prohibit outright.

In practice, signage helps control risk under limited conditions. It can help set expectations in entrance and parking areas and other non-private spaces, but it does not convert a prohibited camera angle into a lawful one and does not replace all-party consent for audio. Security teams should align posted notices and employee policies with camera configurations so that notices do not promise one thing while microphones or fields of view do another.

Data Privacy and Biometric Obligations

Biometric analytics raise separate data-handling obligations when footage is processed into a template capable of authenticating identity. Raw footage that is not processed into an identifier presents a different privacy profile. Organizations using identity-related templates should document necessity and retention limits, and complete privacy review before deployment. Consumer privacy reviews for camera analytics should be separated from employee-facing programs, which also require review under the criminal statutes and the NLRA.

Camera analytics reviews should determine whether the system merely records or reviews footage, or whether it creates or uses a biometric template capable of authenticating identity. The legal exposure changes when video is processed into sensitive personal information. Security and privacy teams should use the same definitions with procurement during reviews of camera analytics and access-control integrations, including vendor contracts and retention practices.

The Personal Information Protection Act (PIPA) separately covers biometric data capable of authenticating identity. It requires reasonable security practices and protective vendor contract terms. It also requires breach notification within 45 days of discovery.

Penalties and Legal Exposure

Unlawful audio interception under § 10-402 is a felony punishable by up to 5 years' imprisonment, a $10,000 fine, or both. Illegally intercepted communications are also inadmissible as evidence.

The visual surveillance offenses are misdemeanors with jail and fine exposure. Each creates a private civil action for damages and attorney's fees. The statutory penalties should be reviewed when policies are updated.

Federal Rules That Apply in Maryland

Maryland's all-party consent requirement should guide camera-audio settings, even for teams operating under more permissive baselines in other jurisdictions. The National Labor Relations Board (NLRB) General Counsel has said she would urge the Board to adopt a framework under which surveillance practices that, viewed as a whole, would tend to interfere with protected activity presumptively violate the Act, and that employers should disclose the monitoring technologies they use and why.

Practical Compliance Steps for Security Teams

• Disable audio capture on cameras, or document prior consent from every party before any audio records.
• Audit camera placement against §§ 3-901 through 3-903 and document that no angle captures restrooms, changing areas, residential interiors, or other protected views after renovations, office moves, access-control changes, or tenant changes.
• Maintain a camera inventory that identifies each device, location, field of view, audio status, retention setting, and business purpose.
• Define retention periods and access controls for footage, including review cadence. National Institute of Standards and Technology (NIST) SP 800-53 control PE-6(3) covers designated-area video surveillance, including review cadence and retention.
• Separate video-only policies from audio-recording policies, limit footage access to personnel with an operational need, align vendor access with contract terms that protect biometric data where applicable, and train global security operations center (GSOC) and site teams to escalate questions about prohibited locations, residential views, employee protected activity, and audio consent before footage is captured or shared.

Building a Defensible Camera Program in Maryland

Maryland compliance turns on keeping the two regimes separate. Lawmakers amended the statutes in 2025 and continue to revisit the wiretap framework, so any program last reviewed against pre-amendment text is due for a fresh audit. Codifying those rules into written policy positions a security team to absorb the next round of amendments.

Frequently Asked Questions

What changes did Maryland's HB 437 amendment effective October 1, 2025 make to video surveillance laws regarding residences?

HB 437 expanded Section 3-902's protected private places to explicitly include residences, bringing them under the same prurient-intent surveillance prohibition that already covered dressing rooms, restrooms, locker rooms, and similar spaces where individuals expect privacy.

How does Maryland's all-party consent requirement for audio recording differ from other states, and what are the penalties for violating it?

Maryland requires every participant to consent before audio recording, unlike one-party consent states where only one participant needs awareness. Violating this all-party rule is a felony carrying up to five years imprisonment and ten thousand dollars in fines.

What specific steps should security teams take to ensure camera analytics and biometric data comply with Maryland's Personal Information Protection Act (PIPA)?

Security teams should implement reasonable security practices, establish protective vendor contract terms with defined data handling obligations, document necessity and retention limits before deployment, and ensure breach notification protocols trigger within forty-five days of discovery when biometric templates are compromised.