CCPA/CPRA
Opt-out of sale or sharing, limiting sensitive data and preference signals – CCPA/CPRA

CCPA/CPRA 1798.135(a): Post the opt-out and limit links, or a single alternative link

A business selling or sharing data, or using sensitive data beyond the permitted purposes, must place clear and conspicuous homepage links: an opt-out link carrying the statutory title "Do Not Sell or Share My Personal Information" plus another link carrying the title "Limit the Use of My Sensitive Personal Information", or one combined link (titled Your Privacy Choices or Your California Privacy Choices with the opt-out icon under 11 CCR 7015) that lets the consumer do both. Under 1798.135(b) and section 7025(g) a business that processes opt-out preference signals in a frictionless way and meets the further conditions need not post the links. A separate homepage for California consumers may carry them instead (1798.135(d)).

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 2 controls across 2 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

  • S541-102 Publish a clear privacy notice and disclose sale and targeted advertising with the opt-out route

Virginia CDPA · 1 control

  • 59.1-578 D Disclosure of sale and targeted advertising

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Opt-out of sale or sharing, limiting sensitive data and preference signals – CCPA/CPRA

You are reading one control. How much of CCPA/CPRA have you already done?

CCPA/CPRA 1798.135(a) is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CCPA/CPRA your existing evidence covers. Hold GDPR and 17 of 89 CCPA/CPRA controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the GDPR pair alone.

Query this from an agent

The graph holds this control, the 2 it maps to, and the evidence behind each claim, over MCP and REST.