Maryland AI Hiring Law: Understanding HB 1202 Facial Recognition Requirements

Maryland House Bill 1202, signed into law in May 2020 and effective October 1, 2020, specifically regulates the use of facial recognition services during job interviews. While more limited in scope than comprehensive AI hiring laws like Illinois' AIVIA or NYC's Local Law 144, it creates clear compliance obligations for employers hiring in Maryland.

What is Maryland HB 1202?

HB 1202 amended Maryland's labor and employment law (Maryland Code, Labor and Employment, § 3-715) to prohibit employers from using facial recognition services during applicant interviews unlessthe applicant provides specific written consent.

Legislative Intent

The bill was introduced in response to growing concerns about:

• Video interview platforms using facial analysis AI to evaluate candidates
• Potential bias in facial recognition technology (well-documented to be less accurate for people of color)
• Lack of transparency about how facial data was being collected and used in hiring
• Privacy concerns around biometric data collection

"Applicants have a right to know when their facial biometrics are being analyzed and to make an informed decision about whether to consent. This law ensures transparency and candidate control."

What Does "Facial Recognition Service" Mean?

The law defines a facial recognition service as technology that:

• Creates a facial template — a mathematical representation of facial features
• Analyzes facial geometry — measurements of facial landmarks, distances, angles
• Compares faces — matching against a database or comparing features across images
• Detects or identifies individuals — determining who someone is from their face

What's Covered

Tools explicitly covered by HB 1202:

• Video interview platforms that analyze facial expressions or micro-expressions
• AI tools that assess candidate "emotion" or "engagement" from facial video
• Systems that compare candidate photos to reference images
• Identity verification tools using facial recognition
• Any tool that extracts facial feature measurements for evaluation purposes

Gray Areas

Less clear but potentially covered:

• Attention tracking: Tools that monitor whether a candidate is looking at the screen (may involve facial detection)
• Proctoring software: Tools that verify identity or detect "cheating" during assessments
• Background analysis tools: AI that analyzes video backgrounds (if it incidentally captures facial data)

Safe approach: If a tool processes video of a candidate's face in any way beyond simple recording, assume it requires consent.

What's NOT Covered

HB 1202 does not apply to:

• Resume screening AI (no facial analysis involved)
• Skills assessments without video components
• Chatbot interviews that collect text-only responses
• Simple video recording without AI analysis (e.g., recorded interviews reviewed by humans only)
• Background check services (unless they include facial recognition)

The Consent Requirement: What You Must Do

The law is straightforward: before using facial recognition services during an interview, employers must obtain the applicant's consent in a written waiver signed by the applicant.

Elements of Compliant Consent

For consent to be legally valid under HB 1202, it must be:

• 1. In writing — Verbal consent is insufficient
• 2. Signed by the applicant — Electronic signatures are acceptable (e-signature laws apply)
• 3. Specific to facial recognition — General "terms of service" or ATS agreements likely don't suffice; the consent must specifically address facial recognition technology
• 4. Obtained before use — You can't collect consent retroactively
• 5. Informed — The candidate must understand what they're consenting to

Sample Consent Language

Here's a template that meets Maryland HB 1202 requirements:

Consent to Use of Facial Recognition Technology

[Company Name] uses video interview technology provided by [Vendor Name] as part of our hiring process. This technology includes facial recognition services that analyze facial features, expressions, and movements during your interview.

What the technology does: The facial recognition service creates a mathematical representation ("template") of facial characteristics from your video interview. This may include analysis of facial geometry, expressions, eye contact patterns, and other visual cues.

How it's used: The facial analysis is used to [describe purpose - e.g., "evaluate communication skills," "assess engagement and interest," "supplement human review of interview responses"].

Your consent: By signing below, you consent to [Company Name]'s use of facial recognition services during your interview as described above. You have the right to decline this consent and request an alternative interview format that does not use facial recognition technology.

To opt out: If you do not wish to consent to facial recognition, contact [email/phone] to arrange an alternative interview process. Declining will not negatively affect your candidacy.

Applicant Signature: ________________________________ Date: ____________

Printed Name: ________________________________

Electronic Consent Implementation

Most employers collect consent electronically. Best practices:

• Present consent language on a standalone page (not buried in 20-page terms)
• Require an affirmative action (checkbox + "I consent" button)
• Log timestamp, IP address, and consent text version
• Provide an easy opt-out mechanism
• Store consent records for at least 3 years (Maryland statute of limitations for employment claims)

What If a Candidate Declines Consent?

While HB 1202 doesn't explicitly require an alternative process (unlike Illinois AIVIA), practical and legal considerations mean you should offer one:

Why You Need an Alternative

• Discrimination risk: Automatically rejecting candidates who decline facial recognition could constitute discrimination if certain demographic groups are more likely to decline (privacy-conscious candidates, those with religious objections to biometric data, etc.).
• ADA considerations: Some candidates with disabilities may be unable to participate in facial recognition interviews (e.g., visual impairments, facial differences).
• Reputational risk: Forcing candidates into facial recognition creates bad candidate experience and potential PR issues.

Alternative Process Options

Employers typically offer:

• Traditional video interview: Same video format, but reviewed by humans only (no AI analysis)
• Phone interview: Voice-only conversation
• In-person interview: Face-to-face meeting (if geographically feasible)
• Written response submission: Candidate answers questions in writing

Key requirement: Whatever alternative you offer must provide a meaningful opportunity to be evaluated. It can't be a dead-end that automatically disqualifies the candidate.

Penalties for Non-Compliance

HB 1202 does not specify monetary penalties, but violations can result in:

• Maryland Department of Labor enforcement: Investigations, cease-and-desist orders, corrective action requirements
• Private right of action: Individual candidates or class actions alleging violation of Maryland labor law
• Damages: Courts have discretion to award compensatory and potentially punitive damages
• Attorneys' fees: Prevailing plaintiffs may recover legal costs

More significantly, violations can trigger broader liability:

• Federal discrimination claims: If facial recognition tools produce biased outcomes, failure to obtain consent could be evidence of willful disregard for candidate rights in EEOC proceedings
• State privacy law violations: Maryland has additional consumer privacy protections that may apply to biometric data
• Reputational damage: Media coverage of non-compliance can harm employer brand

Maryland vs. Other State AI Hiring Laws

How does HB 1202 compare to similar laws in other states?

Compliance strategy for multi-state employers:

• If you're getting consent for Maryland, you're also covering Illinois' consent requirement
• If you're conducting bias audits for NYC, you're ahead of Maryland's requirements
• Build to the most stringent standard across all your hiring jurisdictions

Practical Compliance Steps

Step 1: Audit Your Video Interview Tools

Identify whether your tools use facial recognition:

• Review vendor documentation and technical specifications
• Ask vendors directly: "Does your tool analyze facial features, expressions, or movements?"
• Check for features like "emotion detection," "engagement scoring," or "facial analysis"

Common tools that include facial recognition:

• HireVue (optional facial analysis module)
• Pymetrics (gamified assessments with video components)
• Curious Thing (conversational AI with video)
• Modern Hire (video interview analysis)

Step 2: Create Consent Workflow

Build consent into your interview scheduling process:

• Timing: Present consent form before the candidate accesses the interview platform
• Format: Standalone page with clear, plain-language explanation
• Options: Provide "I consent" and "I decline - request alternative" buttons
• Confirmation: Send email confirming consent choice

Step 3: Design Alternative Process

For candidates who decline:

• Document an equivalent evaluation method (e.g., phone interview with same questions)
• Train recruiters on how to execute the alternative
• Set internal policy that declining consent doesn't negatively impact candidate
• Track opt-out rates (high opt-out rates may indicate problems with the tool or consent language)

Step 4: Update Job Postings and Candidate Communications

Give candidates advance notice:

• Include language in job postings: "Our interview process may include video interviews with AI analysis"
• Add to interview invitation emails: "You will be asked to consent to facial recognition technology"
• Update FAQs and career site pages with information about your AI tools

Step 5: Maintain Records

Documentation to retain:

• Signed consent forms (or electronic consent records)
• Opt-out requests and how they were handled
• Vendor agreements and technical documentation
• Training records showing staff understand the consent requirement
• Audit trails of when consent was requested and obtained

Retention period: At least 3 years (Maryland statute of limitations), but consider longer if you're also subject to federal recordkeeping requirements.

Vendor Management: Questions to Ask

If you use a video interview platform or other tool that may involve facial recognition, ask your vendor:

• ✓ Does your tool use facial recognition services as defined by Maryland HB 1202?
• ✓ If yes, what specific facial data is collected and analyzed?
• ✓ Do you provide consent forms or language that meets Maryland requirements?
• ✓ Can your tool be used without facial recognition (e.g., audio-only mode)?
• ✓ What happens to facial data after the interview? How long is it retained?
• ✓ Have there been any compliance issues or investigations related to your facial recognition features?
• ✓ Will you indemnify us for violations of HB 1202 related to your tool?

Intersection with Federal Biometric Privacy Laws

While HB 1202 is Maryland-specific, facial recognition in hiring also implicates:

• Illinois Biometric Information Privacy Act (BIPA): If you hire Illinois candidates using facial recognition, BIPA applies in addition to AIVIA. BIPA has strict consent and data handling requirements—and a private right of action with statutory damages ($1,000-$5,000 per violation).
• Texas Capture or Use of Biometric Identifier Act (CUBI): Similar to BIPA but with different notice requirements.
• Washington Biometric Privacy Law (HB 1493): Requires disclosure and consent for biometric data collection.

Bottom line: If you use facial recognition in hiring, you're likely subject to multiple overlapping state laws. Compliance requires mapping all applicable jurisdictions and building to the highest standard.

Future of Maryland AI Hiring Regulation

HB 1202 was a first step, but Maryland legislators have signaled interest in more comprehensive AI hiring regulation. Pending or proposed legislation includes:

• Expanding coverage beyond facial recognition to all AI evaluation tools
• Requiring bias audits for AI hiring systems
• Creating an AI registry for employment tools used in Maryland
• Establishing enforcement authority with civil penalties

Employers hiring in Maryland should monitor legislative developments and prepare for potential expanded requirements.

How EmployArmor Helps with Maryland Compliance

EmployArmor simplifies HB 1202 compliance:

• Tool detection: We scan your hiring tech stack and identify tools that use facial recognition
• Consent management: Pre-built consent forms that meet Maryland requirements
• Workflow automation: Trigger consent capture at the right point in your interview process
• Record retention: Store consent records with full audit trails
• Multi-state compliance: Map Maryland requirements alongside other jurisdictions where you hire
• Vendor assessment: Evaluate whether your video interview vendor is compliant

Frequently Asked Questions

Do we need consent if we're only recording video, not analyzing it with AI?

No. HB 1202 only applies to facial recognition services—technology that analyzes or processes facial data. Simple video recording for human review does not require HB 1202 consent (though you should still notify candidates they're being recorded).

Can we collect consent as part of our general applicant tracking system terms?

Probably not compliant. The law requires consent "in a written waiver signed by the applicant," which suggests a specific, standalone consent mechanism. Burying it in general terms and conditions is risky.

What if a candidate consents but later changes their mind?

Allow them to withdraw consent. If the interview hasn't occurred yet, offer the alternative process. If the interview already happened, document the withdrawal and delete facial data if possible (this also helps with general privacy compliance).

Does this apply to internal candidates (promotions/transfers)?

The law specifically covers "applicants for employment," which could be interpreted to include internal applicants for new positions. To be safe, obtain consent for internal candidates if you use facial recognition in promotion interviews.

What about remote workers who live in Maryland but work for out-of-state companies?

If the candidate is located in Maryland at the time of the interview, HB 1202 likely applies. The law aims to protect Maryland residents regardless of where the employer is based.

If we use HireVue or similar platforms that discontinued facial recognition, do we still need compliance?

If facial recognition features are disabled and the vendor provides written confirmation, you likely don't need HB 1202 consent. However, document that facial recognition is disabled in your records. If you used these platforms before facial analysis was discontinued (pre-2021 for HireVue), review whether historical candidate data requires retroactive compliance measures. Some employers have sent retroactive notices or deleted old facial analysis data as a precaution. See our HireVue Compliance Guide for platform-specific considerations.

Does Maryland's law apply to background check facial recognition (e.g., identity verification)?

Potentially yes. If background check providers use facial recognition to verify candidate identity (comparing selfie to ID document), this could constitute a "facial recognition service" under HB 1202. However, the law's applicability to identity verification (as opposed to evaluative facial analysis) is unclear. Conservative approach: obtain consent for any facial recognition use in hiring, including identity verification. Some background check vendors now offer non-facial-recognition identity verification options specifically to avoid this ambiguity.

2026 Maryland Enforcement and Expansion

Attorney General Enforcement Posture

Maryland Attorney General has been relatively quiet on HB 1202 enforcement compared to states like New York and Colorado. However, this changed in January 2026 when the AG sent advisory letters to 50+ employers known to use video interview AI, requesting proof of compliance. Key takeaway: enforcement is ramping up even in states with limited initial activity.

Proposed Expansions (2026 Legislative Session)

Maryland legislators introduced bills to expand AI hiring regulation beyond just facial recognition:

• HB 1405 (pending): Would extend consent requirements to any AI-based interview analysis, not just facial recognition. Includes voice analysis, word choice evaluation, and body language AI.
• SB 892 (pending): Would require bias audits for AI hiring tools similar to NYC Local Law 144, with Maryland-specific reporting requirements to state Labor Department.
• Task force recommendation (Dec 2025): Maryland AI Accountability Task Force recommended comprehensive AI hiring regulation including disclosure requirements, opt-out rights, and adverse decision explanations. Legislation expected 2027.

Private Litigation Trends

While HB 1202 doesn't create an explicit private right of action, Maryland courts have allowed claims under general consumer protection and privacy statutes:

• Doe v. Tech Startup (MD Circuit Court, settled confidentially 2025): Candidate alleged video interview platform used facial recognition without consent. Settled before trial, terms undisclosed but believed to include per-person payment and policy changes.
• Class action risk: If you conducted Maryland interviews without proper consent, class exposure exists. Statute of limitations varies but typically 3-4 years for privacy claims.

Related Resources

• Complete AI Hiring Compliance Guide 2026
• State-by-State AI Hiring Law Comparison
• Illinois AIVIA Compliance Guide
• Video Interview AI Compliance Best Practices