Pay Secrecy Policies in California: Labor Code 232 Exposure

No. A California employer can’t make silence about pay a condition of the job. Labor Code section 232 says no employer may “Require, as a condition of employment, that an employee refrain from disclosing the amount of his or her wages,” and it bars firing or disciplining an employee who does. A handbook line calling salaries confidential can become a penalty claim, and a firing after a pay conversation can become a wrongful termination suit. The defense usually depends on what the employee disclosed and why the employer acted.

What does Labor Code section 232 prohibit?

It prohibits three things, and the third one is where lawsuits come from. Under section 232, an employer may not require silence about wages as a condition of employment, may not make an employee sign “a waiver or other document that purports to deny the employee the right to disclose the amount of his or her wages,” and may not “Discharge, formally discipline, or otherwise discriminate against an employee who discloses the amount of his or her wages.”

The first two are policy violations. They show up in handbooks, offer letters, bonus plan documents, and confidentiality agreements that sweep compensation into the definition of confidential information. The third is a retaliation rule, and it attaches to individual decisions about individual people.

A companion statute covers more ground. Labor Code section 232.5 applies the same three prohibitions to “information about the employer’s working conditions.” That reaches complaints about staffing levels and the way managers run the floor. Section 232.5(d) gives employers one carve-out: the statute “is not intended to permit an employee to disclose proprietary information, trade secret information, or information that is otherwise subject to a legal privilege without the consent of his or her employer.”

For pay discrimination specifically, California’s equal pay statute adds its own rule. Labor Code section 1197.5(k)(1) says an employer “shall not prohibit an employee from disclosing the employee’s own wages, discussing the wages of others, inquiring about another employee’s wages, or aiding or encouraging any other employee to exercise their rights under this section.” The same subdivision adds that “Nothing in this section creates an obligation to disclose wages.” Employers don’t have to publish a salary list. They just can’t gag the people who know their own numbers.

Is a confidential compensation clause in the handbook enough to get sued?

It can be. Section 232 doesn’t set its own penalty, and that’s exactly why it shows up in PAGA notices. (PAGA is the Private Attorneys General Act, which lets an employee sue for civil penalties on the state’s behalf.) For any Labor Code provision without a specific penalty, Labor Code section 2699(f)(2)(A) sets a default civil penalty of “One hundred dollars ($100) for each aggrieved employee per pay period,” with lower and higher tiers depending on the circumstances.

The math gets ugly because a handbook policy touches everyone. A plaintiff’s lawyer will argue that each employee who received the handbook was aggrieved in every pay period the policy stayed in force. Employers have real arguments in response: whether a policy that was never enforced was ever a “condition of employment” under section 232, whether the language actually reached the employee’s own pay, and how the court should use its power under section 2699(e)(2) to award “a lesser amount than the maximum civil penalty” when the full number would be “unjust, arbitrary and oppressive, or confiscatory.”

The best argument is the one an employer creates before any notice arrives. Section 2699(g)(1) caps PAGA penalties at 15 percent of the penalty sought if, before receiving the PAGA notice or a records request, the employer “has taken all reasonable steps to be in compliance with all provisions identified in the notice.” Rewriting the confidentiality section of the handbook today is cheap. Doing it after the notice comes in doesn’t earn the cap.

Pay-secrecy language hides in more places than the handbook. Check the acknowledgment form, offer letters, bonus and commission plans, the definition of confidential information in nondisclosure agreements, severance agreements, and the scripts managers use at onboarding.

Rewrite, don’t just delete. A clause that protects customer lists and trade secrets is legitimate. A clause that names employee compensation as one of the secrets isn’t, at least as applied to an employee’s own pay.

Can an employee sue for being fired over discussing pay?

Yes, and the usual vehicle is a wrongful termination claim, not section 232 itself. In Grant-Burton v. Covenant Care, Inc. (2002) 99 Cal.App.4th 1361, a marketing director alleged she was fired for discussing bonuses with other marketing directors. The Court of Appeal reversed the judgment against her on her claim for wrongful termination in violation of public policy. The court wrote that “Labor Code section 232 prohibits the discharge of employees for discussing the amount of their wages.”

The employer in Grant-Burton argued that the statute didn’t apply because the conversation was about a bonus the plaintiff hadn’t received. The court rejected that reading, saying it “would render section 232 virtually meaningless,” and explained that the statute’s purpose is “to protect employees who want to discuss some aspect of their compensation, for example, a possible increase in pay, perceived disparities in pay, or the awarding of bonuses.”

A wrongful termination claim brings tort damages, including emotional distress and, with the right proof, punitive damages. Employees also plead Labor Code section 98.6, which bars retaliation against an employee “because of the exercise by the employee or applicant for employment on behalf of themselves or others of any rights afforded them.” Section 98.6 carries reinstatement, lost wages, a civil penalty “not exceeding ten thousand dollars ($10,000) per employee for each violation,” and a rebuttable presumption of retaliation for action taken within 90 days of the protected activity.

Where are the defenses in a pay discussion retaliation case?

The first defense is in the statute’s words. Section 232(c) protects an employee “who discloses the amount of his or her wages.” In Harvey v. Sybase, Inc. (2008) 161 Cal.App.4th 1547, the plaintiff said she was fired partly for talking with coworkers about a threatened demotion and pay cut. The Court of Appeal upheld a nonsuit on the section 232 theory because the undisputed testimony showed she didn’t disclose the amount. The court declined to stretch Grant-Burton, writing, “we see no reason in this case to expand Grant-Burton beyond its holding.”

Harvey also rejected the companion claim under section 232.5, but for a reason that has run out. The court held that the working-conditions policy in section 232.5 wasn’t “well established” when the plaintiff was fired, because the statute had only recently taken effect. Section 232.5 has been on the books since January 1, 2003, so an employer today shouldn’t plan around that argument.

The second defense is the employer’s reason. Most of these cases are really about causation. If the employee who discussed pay was also missing deadlines, violating policy, or lying to a manager, the fight is over which reason drove the decision and what the records show about when the employer knew each fact. The 90-day presumption under section 98.6 makes timing important, and an employer that acts within weeks of a pay conversation should expect to prove its reason with documents created before that conversation.

The third defense is scope. Section 232.5(d) doesn’t protect disclosure of trade secrets or privileged information. An employee who forwarded the company’s full payroll file to an outside party is in a different position from one who told a coworker what she earns. Discipline for misusing confidential data can be lawful even when the data includes pay. The policy and the discipline both need to target the misuse, not the conversation.

Does federal law also protect pay discussions?

Yes, for most non-supervisory employees, whether or not there’s a union. Section 7 of the National Labor Relations Act protects employees’ right “to engage in other concerted activities for the purpose of collective bargaining or other mutual aid or protection.” Grant-Burton drew on that federal right too, explaining that the court interpreted “wages” in section 232 “to permit the same kind of discussion as allowed under the NLRA.” An unfair labor practice charge with the National Labor Relations Board is a separate front, and it can follow the same handbook clause.

How do the pay disclosure claims compare?

What should an employer do once a pay-discussion claim arrives?

Treat it as two problems: the policy and the person. The policy problem is fixed by rewriting documents. The person problem is defended with evidence, and that evidence starts disappearing quickly if nobody preserves it.

1. Put a litigation hold on the employee’s personnel file, the manager’s emails and chat messages, any messages among coworkers about pay that the company holds, and every version of the handbook and confidentiality agreement in force during the employee’s tenure.
2. Calendar the deadline on the PAGA notice, agency complaint, or summons, and check for an arbitration agreement and an employment practices liability (EPLI) policy that requires prompt notice to the carrier.
3. Identify who heard about the pay conversation and who made the decision, and hold off on any further action involving the employee until a lawyer has looked at it.
4. Pull the discipline history, performance reviews, and attendance records, and note the date each one was created.
5. Talk to a lawyer before replying to the employee’s counsel, contacting the employee, or offering money to resolve it.

Employers looking for California employment defense can find an overview of how the firm handles retaliation and PAGA claims on its practice page.

Pay secrecy questions from California employers

Can we ask managers to keep salary information confidential?

Usually, yes. Managers and payroll staff who see other people’s pay because of their job duties can be told to keep that data confidential, because the employee isn’t disclosing their own wages. The section 232.5(d) carve-out for proprietary information supports that position. Write the rule narrowly, tie it to data accessed through the job, and say outright that it doesn’t restrict anyone from discussing their own pay.

Does section 232 protect an employee who asks coworkers what they earn?

Asking is protected under the equal pay statute. Section 1197.5(k)(1) bars employers from prohibiting an employee from “inquiring about another employee’s wages.” Section 232 itself addresses disclosing one’s own wages, and Harvey shows courts read that wording carefully. In practice, an employer should treat both asking and telling as protected and avoid discipline for either.

Is there a penalty for the policy even if nobody was disciplined?

A plaintiff can seek one through PAGA. Section 232 has no penalty of its own, so the default civil penalty in section 2699(f) is what gets pleaded. Whether an unenforced handbook sentence was a “condition of employment” under section 232(a) is a fair fight, and courts can reduce PAGA awards that would be unjust or confiscatory. The cheapest defense is fixing the language before a notice arrives.

Do supervisors have the same protection?

Under California law, the statute speaks of “an employee” and doesn’t exclude supervisors. Federal labor law is different, because the National Labor Relations Act’s definition of “employee” excludes “any individual employed as a supervisor.” A California employer shouldn’t assume that a supervisor who talks about pay can be disciplined for it.

If an employee says they were punished for talking about pay

If your company has received a demand letter or PAGA notice over a confidential-pay policy or a firing after a pay conversation, the policy language and the dates in the personnel file usually decide how much of the claim is real. Rosenberger + Kawabata represents employers defending employment lawsuits and claims through its business litigation practice, including claims involving pay secrecy policies. Contact Rosenberger + Kawabata online for a confidential consultation, or call (310) 894-6921.

Sources

The statutes are Labor Code section 232, Labor Code section 232.5, Labor Code section 1197.5, Labor Code section 98.6, Labor Code section 2699, and 29 U.S.C. section 157. The decisions are Grant-Burton v. Covenant Care, Inc. (2002) 99 Cal.App.4th 1361 and Harvey v. Sybase, Inc. (2008) 161 Cal.App.4th 1547, both published.

This post is general information about California and federal employment law as of November 7, 2026. It is not legal advice, and reading it does not create an attorney-client relationship. Employment statutes, regulations, and court decisions change often, and the outcome of any claim depends on its facts. Past results do not guarantee future outcomes.