Social media password laws by state (2026): which states bar employers from asking for account access
On this page
- What do social media password laws bar?
- Which states have a social media password law?
- What do these laws still allow?
- Which differences matter most to recruiters?
- What are the penalties?
- What should recruiters and staffing agencies do?
- A policy line and an interview script
- A checklist for hiring teams
- Questions people ask
As of November 2026, 28 states have laws that bar employers from requesting or requiring a job applicant's (and, in all but one, a current employee's) username, password or other access to a personal social media or online account: Arkansas, California, Colorado, Connecticut, Delaware, Hawaii, Illinois, Louisiana, Maine, Maryland, Michigan, Montana, Nebraska, Nevada, New Hampshire, New Jersey, New Mexico, New York, Oklahoma, Oregon, Rhode Island, Tennessee, Utah, Vermont, Virginia, Washington, West Virginia and Wisconsin. Most also bar demanding access in the employer's presence and punishing anyone who refuses; New Mexico protects applicants only, and Oklahoma and Virginia bar "requiring" but not "requesting." None of them bars simply viewing what a candidate has made public, and most say so expressly.
This page is the state-by-state table. What a recruiter may do with public posts, and when a social media check becomes a background check under the Fair Credit Reporting Act, is covered in social media screening of candidates.
Not legal advice. Each row was checked against the state's official code site, or, where the official code is published only through a commercial service (Arkansas, Colorado, New Jersey, New Mexico and Tennessee), against the enacted act on the legislature's own site; California's row was checked against the chaptered bills (AB 1844 of 2012 and AB 383 of 2013) on the legislature's site. Amendments after those acts may exist in those five states. The summaries are short: definitions, exceptions and remedies have conditions that the table cannot carry, so read the statute and ask counsel before relying on an exception. As of November 2026.
What do social media password laws bar?
The statutes differ in wording but share a pattern. Depending on the state, an employer may not:
- request or require a username, password or other login information for a personal account;
- require the person to log in and show the account in the employer's presence;
- require or compel them to add the employer, a manager or a recruiter as a friend, follower or contact;
- require them to change privacy settings so the employer can see more;
- require them to divulge or reproduce content from the account; or
- refuse to hire, discipline or retaliate against someone who says no.
Three states go further on the asking itself: Arkansas, Colorado and Nevada bar an employer from even suggesting that an applicant disclose login information. Hawaii and Vermont also bar demanding an unlocked personal device.
Which states have a social media password law?
"SRO" means a self-regulatory organization, such as a securities industry regulator. "Personal account" means the candidate's own account, not one the employer provides.
| State | Statute | Who it covers | What it bars | Main exceptions |
|---|---|---|---|---|
| Arkansas | Ark. Code 11-2-124 (Act 1480 of 2013, amended by Act 792 of 2017) | Employers, including state and local government; current and prospective employees | Requiring, requesting, suggesting or causing disclosure of username and password, or a privacy-settings change; requiring that the employer be added as a contact; penalizing or refusing to hire | Public information; compliance with law or SRO rules; a formal investigation of a violation of law or written policy; inadvertently received credentials may not be used |
| California | Labor Code 980 | Employers; employees and applicants | Requiring or requesting a username or password, access in the employer's presence, or divulging personal social media; retaliation | Personal social media reasonably believed relevant to an investigation of misconduct or a legal violation, used solely for that investigation; credentials for employer-issued devices |
| Colorado | C.R.S. 8-2-127 (HB 13-1046) | Employers, including state and local government, but not corrections departments or law enforcement; employees and applicants | Suggesting, requesting or requiring login information; compelling a contact add; requiring, requesting, suggesting or causing a settings change; penalizing or refusing to hire | Credentials for the employer's own systems; securities or financial-law compliance investigations; investigations of unauthorized downloads of proprietary data |
| Connecticut | Gen. Stat. 31-40x | Employers, including the state and its subdivisions; employees and applicants | Requesting or requiring credentials or access in the employer's presence; requiring an invitation to a group; retaliation or refusing to hire | Employer-provided or business accounts and employer-paid devices; investigations based on specific information (access may be required, credentials may not); network monitoring; compliance with law or SRO rules |
| Delaware | 19 Del. C. 709A | Employers, including the State, its subdivisions and school districts; employees and applicants | Requiring or requesting credentials, access in the employer's presence, use of a personal account as a condition of employment, divulging content, adding contacts or changing settings; retaliation | Misconduct or legal-violation investigations; employer devices and accounts; network monitoring; screening required by law or SRO rules; law enforcement hiring; public information |
| Hawaii | HRS 487G-3 (Uniform Employee and Student Online Privacy Protection Act, Act 39 of 2021) | Any employer, including government; "employee" includes prospective employees, unpaid interns and independent contractors | Requiring, coercing or requesting login information or content, a settings change, access in the employer's presence or an unlocked personal device; adverse action. A request to connect is allowed only if clearly voluntary | Public information; law, court orders or SRO rules; policies for employer-issued or business devices; specifically identified content (never login information) for compliance, misconduct, data or safety investigations |
| Illinois | 820 ILCS 55/10 (Right to Privacy in the Workplace Act) | Employers and prospective employers; employees and prospective employees | Requesting, requiring or coercing credentials, access, or access in the employer's presence; requiring or coercing a group invitation or a contact add; retaliation or refusing to hire | Policies for and monitoring of employer equipment; public information; compliance with law or SRO rules; specific reported content (no credentials) for investigations; inadvertent credentials must be deleted |
| Louisiana | R.S. 51:1951 to 51:1955 (Personal Online Account Privacy Protection Act) | Employers, including state and local government; employees and applicants | Requesting or requiring credentials for a personal account; penalizing or refusing to hire | Employer devices and accounts; specific-information investigations (content, not credentials); screening duties under law or SRO rules; public information; asking for a personal email address for contact |
| Maine | 26 M.R.S. 615 to 619 | Employers, including the State and its subdivisions; employees and applicants | Requiring, coercing or requesting the password, access in the employer's presence or a settings change; requiring disclosure of account information or a contact add; penalizing or refusing to hire | Public information; screening duties of regulated financial, insurance or securities employers; misconduct investigations; employer devices, software and email |
| Maryland | Lab. & Empl. 3-712 | Employers, including state and local government; employees and applicants | Requesting or requiring a user name, password or other means of access to a personal account; penalizing or refusing to hire | Credentials for the employer's own systems; securities or financial-law compliance investigations; investigations of unauthorized downloads |
| Michigan | MCL 37.271 to 37.278 (Internet Privacy Protection Act) | Employers, including government; employees and applicants | Requesting access to, observation of, or disclosure of access information for a personal account; penalizing or refusing to hire | Employer devices and accounts; specific-information investigations; monitoring; federal or SRO duties; public information |
| Montana | MCA 39-2-307 | Employers and their agents; employees and applicants | Requiring or requesting credentials, access in the employer's presence or divulging content; retaliation, including for lawful speech on personal social media unless it breaks a written policy or contract | Investigations based on specific information about misconduct, criminal defamation or unauthorized data transfer, or a federal or SRO duty; policies for employer devices and accounts |
| Nebraska | Neb. Rev. Stat. 48-3501 to 48-3511 (Workplace Privacy Act) | Public and private employers; employees and applicants | Requiring or requesting credentials or a login in the employer's presence; requiring a contact add; requiring or coercing a settings change; adverse action; waivers | Employer devices and accounts; monitoring; public information; specific-information investigations; screening under law or SRO rules; law enforcement |
| Nevada | NRS 613.135 | Employers in Nevada; employees and prospective employees | Directly or indirectly requiring, requesting, suggesting or causing disclosure of login information; adverse action for refusing | Credentials for non-personal accounts on the employer's internal systems; compliance with law or SRO rules |
| New Hampshire | RSA 275:73 to 275:75 | Employers; employees and prospective employees | Requesting or requiring login information for a personal account; compelling a contact add; requiring lower privacy settings; disciplining employees (the anti-retaliation clause names employees) | Policies and monitoring; employer accounts and devices; inadvertent receipt; public information; investigations (shared content only); compliance with law |
| New Jersey | N.J.S.A. 34:6B-5 to 34:6B-10 (P.L.2013, c.155) | Employers, but not corrections, the State Parole Board or law enforcement; current and prospective employees | Requiring or requesting credentials or any access to a personal account; waivers; retaliation | Compliance with law; employer devices and accounts; specific-information investigations; public information |
| New Mexico | NMSA 50-4-34 (SB 371 of 2013) | Prospective employees only | Requesting or requiring a password, or demanding access in any manner to a social networking account | Workplace policies; monitoring of employer equipment; public information; law enforcement agencies; background checks required by law |
| New York | Labor Law 201-i (effective March 12, 2024) | Private and public employers, but not law enforcement, fire departments or corrections; employees and applicants | Requesting, requiring or coercing credentials, access in the employer's presence, or reproduction of content obtained that way; penalizing or refusing to hire | Non-personal accounts on employer systems; business accounts with prior notice; employer-paid devices where the employee agreed in advance; court orders; federal or SRO duties; public or voluntarily shared information |
| Oklahoma | 40 O.S. 173.2 | Employers that pay one or more individuals; employees and prospective employees | Requiring (not requesting) disclosure of credentials or access in the employer's presence; retaliating or refusing to hire solely for refusing | Employer systems, devices and accounts; inadvertent receipt; specific-information investigations; compliance with law |
| Oregon | ORS 659A.330 | Employers, including public bodies, but not law enforcement units; employees and applicants | Requiring or requesting credentials, or that an account be opened; requiring permission to advertise on the account; compelling a contact add or access in the employer's presence; penalizing or refusing to hire | Employer-provided accounts; investigations (content, not credentials); compliance with law; public information; inadvertent receipt |
| Rhode Island | R.I. Gen. Laws 28-56-1 to 28-56-6 | The state and any employer in the state; employees and applicants | Requiring, coercing or requesting the password or access in the employer's presence; requiring disclosure of account information; compelling a contact add; settings changes; penalizing or refusing to hire | Misconduct investigations; public information; financial, insurance or securities supervision duties |
| Tennessee | Tenn. Code 50-1-1001 to 50-1-1004 (Employee Online Privacy Act of 2014) | Employers with one or more employees, including the state; employees and applicants | Requesting or requiring a password; compelling a contact add or access in the employer's presence; adverse action | Employer devices and accounts; specific-information investigations; monitoring; federal or SRO duties; law enforcement; public information |
| Utah | Utah Code 34-48-101 to 34-48-301 (Internet Employment Privacy Act) | Employers with one or more workers, including the state; employees and applicants | Requesting credentials for a personal account; adverse action or refusing to hire | Employer devices and business accounts; investigations (content); monitoring; federal or SRO duties and law enforcement screening; public information |
| Vermont | 21 V.S.A. 495l | Employers; employees and applicants | Requiring, requesting or coercing credentials, an unlocked personal device, access in the employer's presence, content or a settings change; requiring a contact add; waivers; retaliation | Specifically identified content for compliance, data-leak, harassment or threat investigations; law enforcement screening; compliance with law; employer-issued devices |
| Virginia | Va. Code 40.1-28.7:5 | Employers, including state and local government; current and prospective employees | Requiring (not requesting) disclosure of username and password, or adding an employee, supervisor or administrator as a contact; penalizing or refusing to hire | Inadvertent receipt; public information; compliance with law or SRO rules; requests in a formal investigation |
| Washington | RCW 49.44.200 and 49.44.205 | Employers with one or more employees, including state and local government; employees and applicants | Requesting, requiring or coercing login information or access in the employer's presence; compelling a contact add; settings changes; adverse action | Investigations (content, no login information); employer accounts and devices; compliance with law; peace officer background checks; inadvertent receipt |
| West Virginia | W. Va. Code 21-5H-1 | Employers; employees and potential employees | Requesting, requiring or coercing credentials or access in the employer's presence; compelling a contact add | Public information; compliance with law; employer devices and accounts; data-leak and harassment investigations; inadvertent receipt |
| Wisconsin | Wis. Stat. 995.55 | Employers, including the state; employees and applicants | Requesting or requiring, as a condition of employment, access information, or access to or observation of a personal account; discharging, discriminating or refusing to hire | Employer devices and accounts; investigations on reasonable cause (access, not credentials); legal or SRO duties; public information; a personal email address |
What do these laws still allow?
- Public information. Most of the statutes say expressly that they do not stop an employer from viewing or using information that is publicly available, and none of them regulates simply looking at public posts. Discrimination law still governs how you use what you see.
- The employer's own accounts and devices. Most allow the employer to require credentials for accounts it provides or pays for, and to set policies for its own equipment and networks.
- Investigations of current employees. Most allow an employer with specific information about misconduct, a data leak or a legal violation to ask for the relevant content. Many, including Connecticut, Hawaii, Illinois, Louisiana, Oregon, Washington and Wisconsin, stop short of credentials. These exceptions do not help a recruiter screening applicants.
- Regulated industries. Several states let employers meet screening duties under federal law or the rules of a securities or financial regulator.
Which differences matter most to recruiters?
- "Request" versus "require." Most of the 28 bar a mere request. Oklahoma and Virginia bar only requiring; Arkansas, Colorado and Nevada go further and bar suggesting. A "voluntary" ask is still a violation in most states.
- Applicants are covered almost everywhere. New Mexico covers prospective employees only, and New Hampshire's anti-retaliation clause names employees, but every listed state protects applicants from at least the demand for credentials.
- Showing the account on a call. Many statutes bar requiring or requesting access "in the presence of" the employer. Asking a candidate to log in and share their screen on a video interview is the modern version of that request.
- Friend and follow requests. Several states bar requiring a contact add; Hawaii allows a request only if it is clearly voluntary.
- Who counts as the employer. Montana names the employer's agent, Illinois covers prospective employers, and Hawaii's definition reaches independent contractors and interns.
What are the penalties?
Remedies vary widely, and several statutes state none. Examples from the official texts:
| State | Remedy stated in the statute |
|---|---|
| Colorado | Complaint to the Department of Labor and Employment, which may set by rule fines of up to $1,000 for a first offense and up to $5,000 for each later one |
| Connecticut | Complaint to the Labor Commissioner; civil penalties (for applicants, $25 then $500); attorney's fees to a prevailing complainant |
| Hawaii | Attorney General civil penalty up to $1,000 per violation, capped at $100,000 for all violations caused by the same event; private action for an injunction, damages and fees |
| Illinois | Under amendments effective December 12, 2025, civil penalties of $100 to $1,000 per violation ($1,000 to $5,000 for a repeat within three years), and a private action |
| Michigan | Misdemeanor with a fine up to $1,000; civil action for an injunction and up to $1,000 in damages after a written demand |
| New Jersey | Civil penalty up to $1,000, then $2,500 for each later violation |
| Washington | Private action for an injunction, actual damages, a $500 penalty and fees |
| Wisconsin | Forfeiture up to $1,000; complaint to the Department of Workforce Development |
What should recruiters and staffing agencies do?
The simplest compliant rule works in all 28 states: never ask a candidate for a password, a log-in in front of you, a screen share of a private account, a friend or follow request, or a change of privacy settings, and never hold a refusal against anyone. For a staffing agency the rule has to reach two sets of people: the agency's recruiters and the client's hiring managers who interview the candidates it submits. Put it in the client interview brief, because a client manager's request in an interview can be the one that breaks the law.
If you hire across state lines, apply that rule everywhere rather than tracking which state's law reaches a remote candidate. And if a background screening company reviews social media for you, the FCRA's disclosure, authorization and adverse action steps apply; see the FCRA background check process for recruiters and background checks for staffing agencies.
A policy line and an interview script
Copy-ready text, an example to adapt with counsel:
Policy. "We do not ask applicants or employees for usernames, passwords or other access to their personal social media or online accounts, to log in or share their screen in our presence, to add us or any employee as a contact, or to change their privacy settings. We do not hold a refusal against anyone. We may view information a candidate has made public, and we evaluate it only for job-related reasons."
If a candidate offers to show you a private profile. "Thanks, but please don't. We only look at what's public, and nothing about your personal accounts is part of this process."
Questions about a candidate's personal life raise separate risks; see illegal interview questions.
A checklist for hiring teams
- Remove any password, log-in or "connect with us" field from applications and onboarding forms.
- Brief every interviewer, including client hiring managers, on the no-access rule.
- Keep any social media review to public content, done the same way for every candidate at the same stage.
- If a vendor does the review, follow the FCRA steps.
- Keep investigations of current employees separate from hiring, and check the state's investigation exception with counsel before asking for any content.
Questions people ask
Which states ban employers from asking for social media passwords?
As of November 2026, 28 states have such a law: Arkansas, California, Colorado, Connecticut, Delaware, Hawaii, Illinois, Louisiana, Maine, Maryland, Michigan, Montana, Nebraska, Nevada, New Hampshire, New Jersey, New Mexico, New York, Oklahoma, Oregon, Rhode Island, Tennessee, Utah, Vermont, Virginia, Washington, West Virginia and Wisconsin. New Mexico's law protects job applicants only; the others cover applicants and employees.
Can a recruiter ask a candidate to log in and show their private profile during an interview?
Not in most of these states. Many of the statutes, including California, Connecticut, Illinois, New York, Vermont and Washington, bar requiring or requesting that an applicant access a personal account in the employer's presence, which is what a log-in-and-show request is. Look only at what the candidate has made public.
Can employers still look at a candidate's public social media posts?
Yes. These laws are about passwords and forced access to personal accounts, and most say expressly that they do not stop an employer from viewing information that is publicly available. What you do with public information is still governed by discrimination law and, if a background screening company compiles it, by the Fair Credit Reporting Act.
Can I ask a job applicant to friend or follow our company account?
Be careful. Several states, including Arkansas, Colorado, Illinois, Maine, Nebraska, Oregon, Rhode Island, Tennessee, Vermont, Virginia and Washington, bar requiring or compelling an applicant to add the employer or a manager as a contact. Hawaii allows a request to connect only if the employer makes clear it is voluntary. The safest course is not to ask during hiring.
Is there an exception for workplace investigations?
Most of these laws let an employer investigate specific information about misconduct, data leaks or legal violations, but many limit what it can demand: Connecticut, Hawaii, Illinois, Louisiana, Oregon and Washington, for example, stop short of login credentials. Those exceptions concern current employees under investigation, not applicants being screened.