US CPRA CCPA vs CPRA

CCPA: define the exact products, services, processing, claims, entities, assets, or activities that bring this side into scope; record out-of-scope facts separately.

CPRA: test its own scope boundary, exclusions, and covered activity; do not copy the CCPA conclusion without a separate source-linked finding.

Write two scope findings first: where CCPA applies, where CPRA applies, and which facts are outside one side even if evidence can be reused.

CCPA: identify whether the duty belongs to a business, service provider, contractor, third party, consumer-facing team, or vendor owner.

CPRA: assign the comparator duty to the California privacy actor named in the source, and separate business, service-provider, contractor, and third-party obligations.

Name each role separately because one entity can hold different obligations in different workflows.

CCPA: state the California privacy fact that starts the obligation, such as covered-business thresholds, collection, sale, sharing, a consumer request, or an opt-out signal.

CPRA: test the amended CCPA facts separately, including sensitive personal information, correction rights, sharing for cross-context behavioral advertising, contractor terms, and new CPPA rulemaking areas.

Start with the trigger so teams do not apply the wrong regime to the wrong facts.

CCPA requires businesses meeting the size thresholds to disclose the categories of personal information collected and sold, provide a "Do Not Sell My Personal Information" opt-out link, honor consumer requests to know and delete within 45 days, and avoid retaliatory pricing or service differences for consumers who exercise rights.

CPRA adds to CCPA by creating a right to correct, expanding opt-out rights to cover sharing for cross-context behavioral advertising, introducing sensitive personal information restrictions and a separate opt-out right for SPI use, establishing the California Privacy Protection Agency as the independent enforcement body, and imposing data minimization and retention limit obligations.

Translate obligations into tickets, notices, records, controls, or contract terms.

CCPA: keep the evidence that proves this side of the decision, including cited text, registers, policies, test records, contracts, notices, reports, approvals, or audit artifacts.

CPRA: keep comparator evidence in a distinct record set and link only the artifacts that genuinely satisfy both source-linked requirements.

Keep source links, factual analysis, owner approval, and implementation evidence together.

CCPA: capture the application date, commencement date, transition period, reporting clock, review cadence, remediation window, or certification renewal that controls this side.

CPRA: track the comparator schedule separately so a later deadline, recurring audit, or incident timer is not hidden by the other workstream.

Use current source dates; do not reuse old project plans after amendments or guidance updates.

CCPA: identify the competent authority, regulator, assessor, customer audit, certification body, contractual remedy, penalty, or supervisory process tied to this side.

CPRA: identify the comparator enforcement or assurance route and record where supervision, penalties, market access, certification, or contract leverage differs.

Escalate when enforcement routes differ because a regulator, market-surveillance authority, certification body, customer, or contract counterparty may require different proof.

CCPA: reuse controls only where the source-linked duty, evidence standard, owner, and timing align with the comparator; otherwise keep a bridge note.

CPRA can reuse evidence from the other side only when the same fact pattern, system boundary, control, owner, and source-linked requirement are genuinely aligned.

Document overlap explicitly instead of merging both tests into one vague compliance label.

CCPA: treat this as the controlling workstream when its scope trigger, deadline, regulator, or required artifact is the immediate blocker.

CPRA: run a parallel or follow-on workstream when this side adds separate actors, evidence, timing, penalties, customer assurances, or implementation constraints.

Choose one practical next step: proceed under CCPA, proceed under CPRA, run both in parallel, or document why neither side controls the present fact pattern.