This page maps California CPRA requirements into scope triggers, accountable owners, controls, evidence records, deadlines, and escalation points.
This guide maps official CPRA requirements into scope, evidence, owners, and review outputs. Validate decisions against current legal and policy requirements before implementation.
Structured answer sets in this page tree.
Cited legal and guidance references.
This page explains California CPRA obligations to the specific trigger, responsible role, deadline, evidence record, and review path that product, legal, privacy, security, and compliance teams can apply.
Start by deciding whether the issue affects threshold status, sensitive personal information, sharing or cross-context advertising, GPC, correction rights, data-broker duties, ADMT, risk assessments, cybersecurity audits, or service-provider contracts. The right answer should identify the trigger, the affected product or process, the required action, the owner, the evidence, and the escalation point.
Keep the statutory/regulatory source, threshold calculation, data category, consumer-right workflow, opt-out signal handling, and contract evidence together so California privacy decisions are reviewable.
Ownership should sit with the team that can change notices, rights intake, consent/opt-out interfaces, data sharing, retention, vendor terms, or security evidence, with privacy counsel reviewing edge cases.
Evidence should show threshold calculations, privacy notice language, consumer request handling, GPC processing, sensitive-personal-information controls, service-provider/contractor terms, and risk/cyber/ADMT readiness where applicable.
Most CPRA mistakes happen at the boundary between CCPA and CPRA terminology, sale versus sharing, sensitive personal information, data-broker duties, and draft or phased regulatory Requirements.
Review this section before launching a data flow, ad-tech integration, consumer interface, vendor contract, retention rule, risk assessment, or cyber audit control.
Use a CPRA workflow that captures threshold status, data categories, consumer rights, opt-out signals, vendor role, retention logic, risk/cyber/ADMT trigger, owner, and review date.
The output should be a threshold memo, notice update, DSAR workflow, opt-out/GPC implementation record, vendor clause map, risk-assessment intake, or audit evidence pack.
This US CPRA guide turns turn Requirements into owners, evidence requests, review checkpoints, and reusable operating records for your team.
Turn Requirements 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.
"On March 29, 2023, the Office of Administrative Law approved the California Privacy Protection Agency's regulations and filed"
"(ii) Does not make use of any dark patterns"
"The CPRA amended the CCPA by adding additional consumer privacy rights and obligations for businesses"
"Cybersecurity Audits, Risk Assessments, Automated Decisionmaking Technology (ADMT), and Insurance Regulations"
"Instructions on how to register in 2026 Data brokers must register and pay the annual fee between January"