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

1798.136 Browsers must offer an opt-out preference signal setting (from 1 January 2027)

From 1 January 2027, any business that builds or maintains a web browser must include a setting, easy for a reasonable person to find and configure, that lets the consumer switch on an opt-out preference signal which the browser then transmits to the sites the consumer visits, and must explain in its public disclosures how the signal works and what it is meant to do. The browser maker is not liable for how recipients treat the signal.

Source: CCPA/CPRA, 1798.136. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CCPA/CPRA in the compliance library.

Applies only to a business that meets one of the thresholds in Cal. Civ. Code 1798.140(d).

3
artefacts
0
held by a system
2
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

  • Product specification and release notes for the opt-out preference signal setting · Source control / CI pipeline
  • Usability test showing users can locate and enable the setting · Document repository

governing documentDocuments that govern the control

  • Public help page describing how the signal works and its intended effect · Document repository

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

1798.135(c) Run opt-out and limit requests without friction or reuse · CCR 7002 Purposes must match reasonable expectations, or consent is needed