Does CCPA Civ. Code § 1798.135(b), (e) apply to my service?

It applies when California CCPA assessed scope Q_CA_CONSUMERS: YES; and at least one of: California CCPA assessed scope Q_CA_REVENUE_THRESHOLD: YES; California CCPA assessed scope Q_CA_VOLUME_100K: YES; California CCPA assessed scope Q_CA_SALE_REVENUE_50: YES; and California CCPA assessed scope Q_CA_SELLS_PI: YES.

From when does this apply?

CCPA Civ. Code § 1798.135(b), (e) applies from 1 January 2023. Its current status is: in force.

CCPA · US-CCPA-OPT-OUT-PREFERENCE-SIGNAL

CCPA Civ. Code § 1798.135(b), (e)

Treat an opt-out preference signal such as Global Privacy Control as a valid opt-out of sale and sharing, and show the consumer that it was honoured

CRITICALRequirementConsentBinding regulationIn forceApplies from 1 January 2023

Where this comes from

Provision: Civ. Code § 1798.135(b), (e); 11 CCR § 7025

Instrument: California Consumer Privacy Act of 2018 (as amended by the CPRA) and CPPA regulations

Citation: Cal. Civ. Code § 1798.135(b), (e); Cal. Code Regs. tit. 11, § 7025

Text version: Civ. Code as published 2026-10-01; 11 CCR as effective 2026-01-01

Checked against the source: 1 October 2026

Read the official text ↗

Who it applies to

A business under the CCPA (Civ. Code § 1798.140(d)(1)) — all of these:

California CCPA assessed scope Q_CA_CONSUMERS: YES

Meets one or more of the business thresholds — any one of these:

California CCPA assessed scope Q_CA_REVENUE_THRESHOLD: YES
California CCPA assessed scope Q_CA_VOLUME_100K: YES
California CCPA assessed scope Q_CA_SALE_REVENUE_50: YES

Duty-specific scope — all of these:

California CCPA assessed scope Q_CA_SELLS_PI: YES

What engineering work it implies

Sample acceptance criteria Landfall generates for this obligation:

Read the Sec-GPC request header and navigator.globalPrivacyControl on every page load
When the signal is present, no sale or cross-context behavioural advertising request fires and the browser is recorded as opted out
A known logged-in consumer sending the signal is opted out on their account, not only in this browser
The page shows that the signal was honoured (for example "Opt-Out Request Honored") and the privacy settings reflect it
No pop-up asks the consumer to confirm or override the signal

Questions people ask

Does CCPA Civ. Code § 1798.135(b), (e) apply to my service?: It applies when California CCPA assessed scope Q_CA_CONSUMERS: YES; and at least one of: California CCPA assessed scope Q_CA_REVENUE_THRESHOLD: YES; California CCPA assessed scope Q_CA_VOLUME_100K: YES; California CCPA assessed scope Q_CA_SALE_REVENUE_50: YES; and California CCPA assessed scope Q_CA_SELLS_PI: YES.
From when does this apply?: CCPA Civ. Code § 1798.135(b), (e) applies from 1 January 2023. Its current status is: in force.

Find out whether this one lands on you

Landfall's pre-scan answers the applicability question above for your product in minutes, then turns every obligation that applies into traceable engineering tickets with a citation chain your auditors can follow.

Run the pre-scan All CCPA obligations

Not legal advice. Landfall maps regulatory obligations to engineering work for planning purposes. Its verdicts are not legal advice and create no attorney-client relationship — verify with qualified counsel before relying on them.

What Landfall Is NOT

Critical Boundaries

Understanding these boundaries is essential before using this product. Misuse of this tool for purposes outside its scope may create legal, regulatory, or commercial risk for your organization.

NOT Legal Advice

This product does not provide legal advice and does not create an attorney-client relationship.

Interpretations are informational analysis, not legal counsel. Always consult qualified legal professionals for compliance decisions.

NOT a Risk Score

We do not quantify, calculate, or certify your compliance risk level.

No numerical risk rating, compliance percentage, or safety score. Risk assessment requires human judgment about your specific context.

NOT Runtime Enforcement

This is a planning and mapping tool, not a runtime enforcement system.

Does not integrate with your production systems. Does not block, filter, or enforce compliance in real-time. Implementation is your responsibility.

NOT Regulatory Approval

Using this tool does not mean you are compliant with any regulation.

No certification, seal of approval, or compliance guarantee. Regulators will evaluate your actual implementation, not your use of this tool.

NOT Authoritative Interpretation

Our interpretations are not binding and may differ from regulatory guidance.

Only regulators and courts provide authoritative interpretation. Our analysis reflects our reading of requirements, which may be incomplete or incorrect.

NOT a Safe Harbor

This tool does not shield you from enforcement actions or liability.

Documentation of your process is valuable, but does not constitute a legal defense. Compliance is ultimately your organization's responsibility.

NOT an AI Compliance Agent

AI features assist analysis but do not make compliance decisions for you.

AI-generated interpretations require human review and approval. Automated suggestions are starting points, not final answers.

NOT Complete Coverage

We do not cover all regulations, all obligations, or all jurisdictions.

Regulatory landscape is vast and evolving. Gaps in our coverage do not mean those requirements don't apply to you.

What This Tool IS:

A structured workflow for mapping regulatory requirements to implementation tasks
A documentation system for compliance decisions (audit trail)
A collaboration platform for compliance, legal, and engineering teams
An informational resource for understanding regulatory obligations