EMPLOYEE PRIVACY | 2026-11-20
Social Security Number Confidentiality at Work: California 2026
California law restricts how an employer may post, print, transmit, and store an employee Social Security number.
By Anatolii Trembach, Esq. (California State Bar No. 349304; LL.M., USC Gould School of Law; admitted to the U.S. Court of International Trade), Trembach Law Firm, APC · Published
Your employer needs your Social Security number for tax and verification purposes, but collecting it does not let the company post it, print it on your pay stub, email it unencrypted, or leave it exposed in your file. California law sharply restricts how any employer may handle a Social Security num
Why Your Social Security Number Is Legally Protected at Work
A Social Security number is the master key to a worker's financial identity, and California treats it accordingly. Employers collect the number at hire for tax and verification purposes, but collecting it does not give the employer free rein to post it, print it, email it, or scatter it across records and mailings. A dedicated California statute restricts what any person or entity, including an employer, may do with an individual's Social Security number, and the restrictions apply even when the employer means no harm.
The core protections appear in Civ. Code § 1798.85, which prohibits several specific uses of a Social Security number. These rules supplement the broader right to privacy guaranteed by Cal. Const. art. I § 1, which this state has long read to protect informational privacy against both government and private intrusion. For employees, the combination creates enforceable limits on how an employer handles one of the most sensitive data points it holds.
These protections exist because the consequences of exposure are severe and permanent. Unlike a compromised password, a Social Security number cannot be reset. Once it is loose, a worker can face years of fraudulent credit applications, tax-refund theft, and identity misuse. The Legislature responded by imposing categorical limits that do not depend on proof of actual harm, so a violation is complete the moment the prohibited handling occurs.
The Five Prohibitions of Civil Code Section 1798.85
Civ. Code § 1798.85 bars a person or entity from doing five things with an individual's Social Security number. First, it may not publicly post or publicly display the number, meaning it may not be intentionally communicated or otherwise made available to the general public. Second, it may not print the number on a card required to access products or services. Third, it may not require an individual to transmit the number over the internet unless the connection is secure or the number is encrypted. Fourth, it may not require the number to log on to a website without a password or other authentication. Fifth, it may not print the number on materials mailed to the individual unless state or federal law requires it, with narrow exceptions.
These are categorical limits. An employer that posts a schedule, roster, or benefits document bearing full Social Security numbers in a break room has publicly displayed them. An employer that emails an unencrypted spreadsheet of employee numbers has required transmission over the internet without the required safeguards.
The statute also constrains how an employer may redesign its systems. An employer cannot avoid the prohibitions by using the number as a login credential, because the fourth prohibition specifically bars requiring the number to access an internet website without a separate password or authentication device. The cumulative message is that the Social Security number is not a convenient identifier to be reused across business systems; it is sensitive data to be quarantined.
Only the Last Four Digits Belong on a Wage Statement
The wage statement is the most common place a Social Security number surfaces, and California law is explicit. Labor Code § 226(a)(7) requires that an itemized wage statement show only the last four digits of the employee's Social Security number or an employee identification number other than the Social Security number. A pay stub that prints the full nine-digit number violates the statute, and the violation is independent of any actual identity theft that results.
This requirement reflects a legislative judgment that routine payroll documents, which pass through many hands and are easily lost, should never carry the full number. Employers that inherited legacy payroll templates printing full numbers remain liable until they fix the format, and workers who spot a full number on a pay stub have identified a concrete statutory violation.
The wage-statement rule is especially consequential because pay stubs are generated every pay period for every employee, so a single defective template can create a recurring violation across the workforce. California treats each noncompliant statement as a discrete event, which is why pay-stub violations frequently drive representative and class claims with substantial aggregate exposure.
The Duty to Use Reasonable Security
Beyond the specific prohibitions, California imposes a general duty of care over sensitive data. Civ. Code § 1798.81.5 requires a business that owns, licenses, or maintains personal information about a California resident to implement and maintain reasonable security procedures and practices appropriate to the nature of the information, to protect it from unauthorized access, destruction, use, modification, or disclosure. A Social Security number is squarely within the definition of protected personal information.
Reasonable security is contextual. Storing numbers in an unlocked drawer, in a shared folder without access controls, or on an unencrypted laptop can breach the duty. When a breach exposes numbers, separate notification obligations attach, and a pattern of careless handling can support a negligence theory in addition to the statutory claims.
The reasonableness standard scales with sensitivity, so the law expects more protection for a Social Security number than for an ordinary business record. An employer that encrypts customer payment data but leaves employee Social Security numbers in plain text has misallocated its security, and that inconsistency can itself be evidence that the employer failed to adopt practices appropriate to the nature of the information.
Restrictions on Agencies and Communications
California layers additional limits through Civ. Code § 1798.89, which restricts printing an individual's Social Security number on documents and in communications in specified circumstances and constrains its use by certain entities. Read together with § 1798.85, these provisions reflect a consistent policy: the number should be collected only when necessary, used only for the narrow purpose that justified collection, and never broadcast. Employers that treat the number as a convenient universal identifier for files, lockers, timekeeping, or logins run directly into these rules.
The safe practice is to substitute an internal employee identification number for every operational use and to quarantine the actual Social Security number in a restricted system accessible only to payroll and tax functions.
Data-minimization is the organizing principle behind all of these provisions. The fewer places the number appears, the smaller the attack surface and the lower the risk of an inadvertent violation. A workplace that collects the number once, stores it in a single encrypted system, and never reproduces it elsewhere has largely immunized itself against these claims.
The Constitutional Privacy Backdrop
Cal. Const. art. I § 1 names privacy as an inalienable right, and California courts recognize a private cause of action for invasion of informational privacy. To prevail, a plaintiff generally must show a legally protected privacy interest, a reasonable expectation of privacy under the circumstances, and a serious invasion of that interest. A Social Security number carries an obvious and strong expectation of privacy, so an employer's careless exposure can support a constitutional claim alongside the statutory ones.
This constitutional dimension matters because it is not limited to the specific scenarios the statutes enumerate. An employer practice that falls through a statutory gap may still be an actionable invasion of privacy if it seriously compromises the number's confidentiality.
The constitutional claim also reaches conduct that predates or sidesteps the specific statutory prohibitions, giving workers a flexible remedy where the facts do not fit neatly within an enumerated category. Because the constitutional right binds private employers in California, a worker is not limited to the statutory causes of action when an employer's handling of the number is genuinely egregious.
How Violations Happen in Real Workplaces
Violations rarely look dramatic. A manager tapes a sign-up sheet to the wall that includes numbers for verification. A benefits administrator emails enrollment forms in plain text. A timekeeping terminal uses the full number as the login. A terminated employee's file is left in a copier. An onboarding portal asks new hires to type the number into an unencrypted web form. Each of these ordinary administrative choices can breach Civ. Code § 1798.85 or the reasonable-security duty, and each is avoidable with a different design.
Because the harm from exposure can be severe and long-lasting, California does not require a worker to wait for identity theft to materialize before the statutory violation is complete.
Many violations also originate with third-party vendors, such as payroll processors, benefits administrators, and background-check firms, that handle the number on the employer's behalf. An employer remains responsible for the data it owns or licenses, so pushing the number to a careless vendor does not transfer the legal exposure. Vendor contracts should require encryption, access controls, and breach notification, and the employer should verify that those protections are real rather than merely promised.
Remedies and Enforcement Options
A worker harmed by misuse of a Social Security number may have several overlapping avenues. The wage-statement violation under Labor Code § 226(a)(7) can be pursued where the statute provides penalties and attorney fees for knowing and intentional violations, and it can anchor a representative action. The data-security and confidentiality provisions can support claims for damages and injunctive relief, and the constitutional privacy right offers an independent path. Workers whose paychecks or final pay are mishandled alongside privacy breaches may also review our guide on overpayment recoupment and Labor Code § 221 for related final-pay protections.
Injunctive relief is often the most valuable remedy, because it forces the employer to change the practice and protect the broader workforce. Documentation is key: keep copies of any document that exposed the number and note where and how it was displayed or transmitted.
Where the exposure is systemic, affecting many employees through a single practice such as a defective pay-stub template or an unencrypted portal, representative enforcement can address the problem at scale and secure relief for workers who would never have brought an individual claim. The prospect of aggregate liability is often what finally moves an employer to redesign a noncompliant system.
Compliance Steps for California Employers
Employers should map every place the Social Security number appears, eliminate it from wage statements except for the last four digits, replace it with an internal identifier for all operational uses, encrypt it in transit and at rest, restrict access to a need-to-know basis, and never post or mail the full number. Onboarding portals should use secure, encrypted transmission, and physical documents bearing the number should be locked and shredded on a schedule. Training line managers not to improvise with the number on sign-in sheets prevents the most common inadvertent violations. For related developments, follow our California employment law news coverage.
A short internal audit against the five prohibitions of § 1798.85 and the reasonable-security standard of § 1798.81.5 catches the overwhelming majority of problems before they become claims.
Employers should also build a document-retention and destruction schedule so that old files bearing the number are securely destroyed rather than accumulating in storage, where they become a standing liability. Periodic re-auditing matters too, because new systems, vendors, and forms introduced over time can quietly reintroduce the number into places it was removed from, undoing earlier compliance work.
Background Checks and Third-Party Screeners
The Social Security number does not stop being protected when an employer hands it to a vendor. Background-check companies, payroll processors, and benefits administrators routinely receive the number, and the employer that owns or licenses the data remains responsible for its protection under Civ. Code § 1798.81.5. A worker whose number is exposed through a careless screener may have claims against both the vendor and the employer that selected and fed the vendor the data without ensuring reasonable security. Employers should require encryption, access limits, and breach notification in every vendor contract that touches the number, and should confirm those protections operate in practice.
Background-check practices intersect with other California protections as well, including limits on how consumer reports are obtained and used in hiring. While those rules are distinct from the Social Security number statutes, they share the same orientation: sensitive personal information must be collected narrowly, handled carefully, and disclosed only as the law allows. An employer that treats the number as a routine input to a sprawling screening process, shared freely among vendors, multiplies the points at which a violation of Civ. Code § 1798.85 can occur.
What Workers Can Do Right Now to Protect Their Number
A worker who suspects mishandling should start by examining recent pay stubs to confirm that only the last four digits appear, as Labor Code § 226(a)(7) requires. The worker should note any posting, email, portal, or mailing that displayed the full number and preserve a copy, because that document is the evidence of a violation. If the number has been exposed, the worker may place fraud alerts or a credit freeze, monitor credit reports, and report suspected identity theft, steps that both mitigate harm and document the consequences of the exposure.
Raising the issue internally is often the fastest route to a fix, and an employer that corrects a defective pay-stub template or an insecure portal promptly can prevent further violations. If the employer refuses to correct the practice, or if the exposure has already caused harm, the worker can pursue the statutory and constitutional remedies described above, including injunctive relief to force a systemic change. Keeping a clear timeline of what was exposed, when, and how the employer responded strengthens any later claim.
Penalties, Injunctions, and Systemic Fixes
Because a single defective practice can affect an entire workforce, the most powerful remedy is often an order compelling the employer to redesign its systems. A pay-stub template that prints the full number, or an onboarding portal that transmits it without encryption, injures every worker who passes through it, and an injunction stops the harm prospectively. Where the employer acted knowingly and intentionally in violating the wage-statement rule, the worker may also recover penalties and attorney fees, which creates a financial incentive for employers to comply before a claim is filed.
The layered structure of California law, combining the specific prohibitions of Civ. Code § 1798.85, the reasonable-security duty of Civ. Code § 1798.81.5, the wage-statement limit of Labor Code § 226(a)(7), and the constitutional right of Cal. Const. art. I § 1, means that most careless handling of a Social Security number violates more than one provision at once. That overlap gives workers multiple paths to relief and gives employers multiple reasons to adopt the simple data-minimization practices that prevent violations in the first place. It also means a plaintiff is rarely limited to a single theory, which improves the odds that at least one claim will reach a remedy.
It is also worth separating the handling of the number from the lawful reasons an employer collects it. An employer genuinely needs the Social Security number to report wages to taxing authorities and to verify work authorization, and collecting it for those purposes is proper. What the law forbids is the drift from that narrow, legitimate use into convenience uses, such as putting the number on a schedule, a login, a locker tag, or a full pay stub. The compliance question is never simply whether the employer may possess the number, which it usually may, but whether each particular display, transmission, or storage of the number satisfies the prohibitions of Civ. Code § 1798.85 and the security duty of Civ. Code § 1798.81.5.
Workers should also remember that the obligation to protect the number continues after employment ends. An employer retains personnel and payroll records bearing the number for years, and those records must stay secure and be destroyed on a reasonable schedule rather than abandoned in storage. A former employee whose number surfaces in a post-termination breach, an improperly discarded file, or a mailing that prints the full number has the same claims as a current worker, because Civ. Code § 1798.85 and the reasonable-security duty of Civ. Code § 1798.81.5 do not expire on the last day of work. Preserving separation paperwork and any later correspondence helps a former worker document the source of an exposure.
Talk to a California employee-privacy lawyer. If an employer exposed your Social Security number on a pay stub, a posting, an unencrypted email, or an insecure portal, you may have statutory and constitutional claims. The attorneys at Trembach Law Firm help California workers protect their most sensitive data. Call (213) 645-2246 for a confidential consultation.
Frequently Asked Questions
Can an employer print a full Social Security number on a pay stub in California?
No. Labor Code § 226(a)(7) allows only the last four digits of the Social Security number or a separate employee identification number on an itemized wage statement. Printing the full number is a statutory violation independent of any resulting identity theft.
What does Civil Code section 1798.85 prohibit?
It prohibits publicly posting or displaying a Social Security number, printing it on an access card, requiring its unencrypted transmission over the internet, requiring it as an unauthenticated website login, and printing it on mailed materials except as the law allows.
Does an employee have to prove identity theft to bring a claim?
No. The statutory violations are complete when the prohibited handling occurs. Actual identity theft can increase damages, but it is not required to establish that the employer violated the Social Security number protections.
Is an employer required to secure stored Social Security numbers?
Yes. Civ. Code § 1798.81.5 requires reasonable security procedures appropriate to the sensitivity of the information, which for Social Security numbers generally means encryption, access controls, and restricted storage.
Does the California Constitution protect a worker's Social Security number?
It can. Cal. Const. art. I § 1 recognizes a right to informational privacy that binds private employers, and careless exposure of a Social Security number can support a privacy claim in addition to the specific statutory protections.
This article is provided for general informational purposes only and is not legal advice. Reading it does not create an attorney-client relationship. Every case depends on its own facts, and no particular outcome is guaranteed.
Contact Trembach Law Firm at (818) 514-7680 for a confidential consultation.
Trembach Law Firm | 27001 Agoura Road, Suite 350, Calabasas, CA 91301