What evidence do auditors commonly ask for on CCR 7026 Handle requests to opt out of sale or sharing?

Opt-out request log with receipt and effective dates; Evidence that sale and sharing stopped within 15 business days, or immediately where real-time bidding allows; Notifications sent to third parties that received data between request and implementation, with onward-forwarding instructions; Confirmation display or account toggle showing opt-out status.

What is the most common gap auditors find on CCR 7026?

Weekly or batched data feeds that went out after the request with no follow-up notice to recipients

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

`CCR 7026` Handle requests to opt out of sale or sharing

The business must offer two or more easy methods to opt out, at least one matching its main channel; an online business must accept opt-out preference signals plus a form, link or policy route, and a cookie banner alone does not count. No verification or account may be required, and only suspected fraud documented in good faith justifies refusal. It must stop selling and sharing as soon as feasible and no later than 15 business days after receipt. It must notify every third party to which it sold or shared the consumer's data between receipt of the request and the moment the request took effect, telling them to honour it and to pass it to anyone they in turn made the data available to in that window. Consumers must be able to confirm the request was processed, agents with signed permission may act for them, and the business must wait 12 months before asking the consumer to opt back in.

Source: CCPA/CPRA, CCR 7026. 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).

artefacts

held by a system

at each review

moderate

to go live

SIEM / log platform

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

Opt-out request log with receipt and effective dates · SIEM / log platform

periodic reviewEvidence produced at each review

Evidence that sale and sharing stopped within 15 business days, or immediately where real-time bidding allows · Document repository

governing documentDocuments that govern the control

Notifications sent to third parties that received data between request and implementation, with onward-forwarding instructions · Vendor register / contract repository
Confirmation display or account toggle showing opt-out status · Policy repository / GRC workspace

First move

Start with the 1 of 4 artefacts that already live in a system (SIEM / log platform); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Weekly or batched data feeds that went out after the request with no follow-up notice to recipients
Opt-out offered only through a cookie preference centre
Requests denied for lack of verification

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

CCR 7025 Process opt-out preference signals · CCR 7027 Handle requests to limit use of sensitive personal information