CCR §7025 Opt-Out Preference Signal Configuration
Opt-out preference signals must be processed by businesses that sell or share PI. The signal must be in a format commonly used and recognized, sent with the consumer's consent, and clearly communicate the consumer's inte
4
artefacts
1
held by a system
2
at each review
moderate
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Tag manager or CMP configuration · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Test results across major browsers · Source control / CI pipeline
- No-additional-info attestation · Vendor register / contract repository
governing documentDocuments that govern the control
- GPC implementation documentation · Document repository
First move
Start with the 1 of 4 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Signal honored only after pop-up confirmation
- Implementation requires additional consumer action
- Not extended to logged-in cross-device sessions
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 sheetCCR §7012 Notice at Collection Drafting Requirements · CCR §7026 Requests to Opt-Out of Sale/Sharing Handling