- California statutory source for operationalizing do-not-sell-or-share links and opt-out preference signal handling.
"Do Not Sell or Share My Personal Information"
Do not sell or share decisions under the US CCPA should be written in operational language: who is in scope, what must happen, what evidence proves it, and when escalation is needed.
This guide converts official requirements into scope, evidence, ownership, and review decisions for practical implementation, supporting implementation planning and should be validated against jurisdiction-specific legal, contractual, and policy requirements before implementation.
Structured answer sets in this page tree.
Cited legal and guidance references.
Under the CCPA, California consumers can tell a business to stop selling or sharing their personal information, and the business has to honor that choice. This page first explains what that right actually means, then maps the obligation to trigger conditions, accountable owners, required deadlines, evidence records, and review paths that product, legal, privacy, security, and compliance teams can apply.
This US CCPA guide turns Do not sell or share into owners, evidence requests, review checkpoints, and reusable operating records inside Sorena.
Turn Do not sell or share into scoped questions, evidence fields, and review tasks.
Use Research Copilot to answer follow-up questions with cited source material.
Review scope, evidence, owners, and the next compliance actions with Sorena.
"Do Not Sell or Share My Personal Information"
"for monetary or other valuable consideration"
"You cannot sue businesses for most CCPA violations"
"Applying Data Minimization to Consumer Requests"
"Privacy User Signal Mechanism ("USP API") (CCPA Compliance Mechanism) produced by IAB Technology Laboratory (IAB Tech Lab)"