Start hereCheck thresholds and map California data
~84 days leftOpen step
Guide library
Regulation North America

CCPA / CPRA

California Consumer Privacy Act, as amended by the CPRA

Determine California scope and operationalize consumer rights, opt-outs and covered assessments.

Who it applies to

For-profit businesses meeting a statutory threshold and doing business in California, with related duties for service providers, contractors and third parties.

What you’ll produce

Documented and testable consumer privacy and governance processes.

Confirm annually adjusted thresholds and any exemptions. Cybersecurity audit, risk assessment and ADMT requirements have distinct applicability and compliance dates.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

Which business and activities are covered?
Confirm California consumers, scope of each entity, thresholds for the relevant year and activity-specific exemptions. Have Finance and Privacy sign off on the calculation inputs.
Where do advertising and vendor choices change obligations?
Have Marketing, Product and Legal review analytics, advertising, vendors and the facts that affect sale or sharing. Fund implementation and testing of preference signals and controls.
Which new rules require a funded project?
Assign separate owners for rule applicability, cybersecurity audits, risk assessments and automated decisionmaking technology where applicable. Confirm milestones from the operative rule for each activity.

How to spend the first week

  1. Get Finance’s threshold inputs, a California audience estimate, data flows and the current vendor and tag inventory.
  2. Use a clean browser with a supported opt-out preference signal enabled and check whether applicable data transfers actually stop. Repeat with a logged-in account.
  3. Run a request through Support and Privacy, then review new rule applicability and secure owners and testing time.

What to review each week

Report requests due this week, failed opt-out tests, uncovered vendor changes and each applicable audit or risk-assessment deadline.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

CCPA / CPRA kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Check thresholds and map California data · Privacy counsel + business owners [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Get Finance’s threshold inputs, a California audience estimate, data flows and the current vendor and tag inventory.
2. Use a clean browser with a supported opt-out preference signal enabled and check whether applicable data transfers actually stop. Repeat with a logged-in account.
3. Run a request through Support and Privacy, then review new rule applicability and secure owners and testing time.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • Does the organization meet the California business and threshold tests?
  • Do advertising, sale, risk assessment or audit rules apply to a specific activity?

Worked scenario

An online shop receives an opt-out signal in the browser. Its privacy operations team checks the tag manager and the server-side audience feed, then keeps both results with the relevant opt-out controls.

What to read next

FROM THE SOURCE

Cases and numbers

Stipulated enforcement order · March 2025

$632,500Administrative fine in the stipulated order

Honda’s privacy request forms became an enforcement issue

The California Privacy Protection Agency alleged that Honda required excessive verification for certain opt-out and limit requests and gave unequal prominence to privacy choices. The final order required changes to the request process, training and a review by a user experience designer.

What to check Test opt-out and limit flows from a fresh browser. Compare the steps, prominence and personal information requested on each path. Test what happens when an authorized agent submits the request.

CalPrivacy stipulated final order ENF23-V-HO-2 (opens in a new tab)
DATES AND TRIGGERS

Official milestones

See the deadline calendar
  • 1 Jan 2026

    Updated regulations effective

    Covered cybersecurity audits, risk assessments and ADMT have separate phase-ins and applicability tests.

    Official reference (opens in a new tab)
  • 1 Jan 2027

    Covered ADMT compliance begins

    Businesses using ADMT for a significant decision before that date must comply by this date. Apply the rules whenever starting covered use from this date.

    Official reference (opens in a new tab)
  • 31 Dec 2027

    Assess covered legacy processing

    Complete risk assessments for covered processing that began before the effective date and continues after it.

    Official reference (opens in a new tab)
  • 1 Apr 2028

    Submit 2026–2027 risk assessment information

    Section 7157 specifies the information and certification to submit.

    Official reference (opens in a new tab)
  • 1 Apr 2028

    First cybersecurity audit report for the 2028 cohort

    Section 7121(a)(1) uses annual gross revenue above $100 million for 2026. Check § 7120 coverage and § 7124 filing duties.

    Official reference (opens in a new tab)
  • 1 Apr 2029

    First cybersecurity audit report for the 2029 cohort

    Section 7121(a)(2) uses the $50 million to $100 million gross revenue bracket for 2027. Check all coverage and filing criteria.

    Official reference (opens in a new tab)
  • 1 Apr 2030

    First cybersecurity audit report for the 2030 cohort

    Section 7121(a)(3) uses gross revenue below $50 million for 2028. Check all coverage and filing criteria.

    Official reference (opens in a new tab)
The whole journeyabout 84 days across 4 steps
  1. 01Check thresholds and map California dataPrivacy counsel + business owners · ~14 days
  2. 02Implement notices, choices and contractsLegal + marketing + product · ~28 days
  3. 03Run consumer rights and verificationPrivacy operations · ~21 days
  4. 04Screen new rules and schedule obligationsPrivacy + security leadership · ~21 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 11 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Check thresholds and map California dataPrivacy counsel + business ownersAt initiation and annuallySet a start dateCoverage memo; Data and vendor inventoryOpen
Implement notices, choices and contractsLegal + marketing + productBefore covered collection or disclosureSet a start dateNotices; Preference signal tests; Contract addendaOpen
Run consumer rights and verificationPrivacy operationsOn receipt, with timing based on the requestSet a start dateRights request playbook; Request log; Response templatesOpen
Screen new rules and schedule obligationsPrivacy + security leadershipBy applicable phase-in and ongoingSet a start dateApplicability matrix; Audit calendar; Assessment registerOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Check thresholds and map California data

    Who Privacy counsel + business owners When At initiation and annually

    Assess doing-business and threshold tests. Include relevant employee and business-contact data. Map sales, sharing, sensitive information and recipients.

    How to do this step

    Before you start

    Revenue data, California audience and activity counts, legal entity map, collection points and contracts.

    1. Document the threshold source, year, assumptions and calculations for each business. List who verified the inputs and what might change the conclusion.
    2. Map consumers, workforce and business contact data where applicable. Identify the activities relying on a specific exemption and preserve the basis.
    3. Follow data from collection to analytics, advertising, hosting and support. Record the recipient’s role and any uses beyond the business’s instructions.

    What a reviewer should see

    Finance can reproduce the coverage calculation, and Privacy can trace the sample advertising activity to tags, recipients, purpose and contract.

    When to escalate

    Escalate an uncertain count, a new group entity or a vendor whose actual use contradicts the planned classification.

    What to produce

    Coverage memoMemo

    Gather first

    • Service inventory and architecture
    • Customer commitments and contracts
    • Applicable criteria or legal text

    How to prepare it

    1. Write the exact decision this memo supports. Name the legal entity, service, environments and dates. Attach a boundary diagram and state which people, vendors and processes can affect the scope.
    2. List the exclusions next to the inclusion list. Give a reason for each one and describe any shared service that crosses the boundary.
    3. Review the draft with service owners and the person making the decision. Freeze the approved version and add a review date or trigger for changes.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Decision
    Cover the hosted billing service for the April to June review.
    In scope
    Production billing API, hosting, releases and production access.
    Excluded and why
    Internal HR tool. It has no access to billing systems or data.
    Dependencies
    Cloud hosting and corporate identity provider.
    Approval
    Service owner approves after checking the architecture and contract.

    Check before handing it over

    A reviewer can use the memo to classify a named system and see how shared dependencies are handled.

    Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.

    Data and vendor inventorySpreadsheet

    Gather first

    • Asset exports or system discovery
    • Service owner interviews
    • Approved scope and architecture

    How to prepare it

    1. Export a dated baseline from the source system. Give each asset, service or record class a stable ID and remove duplicates without losing links to the source.
    2. Add ownership, purpose, sensitivity and any vendor or system it depends on. Mark unknowns explicitly and assign them to someone to resolve.
    3. Reconcile the register against an independent source such as cloud billing or the production deployment list. Set a refresh cadence and an owner.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    ID
    SYS-014
    Item
    Production billing database
    Owner
    Platform operations
    Location and purpose
    Production EU region, stores invoice and account data
    Impact and dependencies
    High. Identity provider and managed backups.
    Verified on
    2026-11-10, cloud inventory export

    Check before handing it over

    Each item has one accountable owner. The source and as-of date let a reviewer trace it back.

    Share the reviewed inventory with the people building the control, privacy or testing scope.

  2. 02

    Implement notices, choices and contracts

    Who Legal + marketing + product When Before covered collection or disclosure

    Update notices at collection and privacy policy. Implement applicable sale/share opt-out and sensitive information restrictions. Test Global Privacy Control and review recipient terms.

    How to do this step

    Before you start

    Coverage decision, live collection screens, tag manager, preference settings and vendor terms.

    1. Map notices at collection and privacy policy disclosures to the actual personal information categories, purposes and points of collection.
    2. Have Engineering test opt-out preference signals and opt-out links on applicable flows, including the signal before sign-in and any required account behavior after sign-in.
    3. Check that downstream tags and data exports honor recorded choices. Compare service provider and contractor terms with actual vendor uses and fix inconsistencies.

    What a reviewer should see

    The test includes browser network evidence before and after the preference signal and a record of the resulting behavior in the relevant backend or vendor.

    When to escalate

    Raise an advertising or analytics release that sends covered data after an applicable opt-out or to a vendor with unclear terms.

    What to produce

    NoticesMemo

    Gather first

    • Approved data map and purposes
    • Applicable disclosures and languages
    • Actual rights, consent and contact channels

    How to prepare it

    1. Write the information a person needs at the point of collection or disclosure. Use the applicable legal checklist to cover who, why, what, recipients, retention and choices.
    2. Match every promise to the real product and supplier configuration. Draft any short collection notice alongside the longer policy and use language appropriate to the audience.
    3. Have privacy and product owners check the draft against the live journey. Publish the approved version, record where it appears and test all contact and choice links.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Audience and moment
    Customer account contact, on the invoice email form
    Plain wording
    We use your billing email to send receipts and help with billing questions.
    Choices and contact
    Link to the applicable privacy request channel.
    Supporting record
    Processing activity P-014 and retention schedule FS-04
    Publish and verify
    Legal approval, web form URL, version and date

    Check before handing it over

    A reader can understand the intended use and reach the correct rights channel. The notice matches what the service actually does.

    Send approved text to the publishing owner and give support teams the version and effective date.

    Preference signal testsMemo

    Gather first

    • Approved test scope and criteria
    • Population and sample records
    • Test approach, results and reviewer requirements

    How to prepare it

    1. State objective, dates, scope and the method before describing results. Record the tester, any independence requirements, and how samples were selected.
    2. For each item, compare what should have happened with what the evidence shows. Describe impact and link the evidence or recorded exception.
    3. Add limitations, obtain review and give each finding an owner and a date. Retain the underlying samples and calculations with the signed version.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Test objective
    Check that production role removals happen within the internal deadline.
    Method and population
    All September departures. Test each privileged account.
    Expected result
    Remove access within one business day.
    Observed result
    11 on time. One late by two days, ticket IAM-114.
    Finding and follow-up
    F-008. Retest the next departure and verify alerting.

    Check before handing it over

    Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.

    Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.

    Contract addendaMemo

    Gather first

    • Current agreement and service description
    • Applicable flow-down terms or engagement requirements
    • Contract owner and legal review

    How to prepare it

    1. Make a clause-by-clause worksheet. Quote only what you need to identify the current clause, and record each required subject and unresolved question.
    2. Mark where scope, instructions, evidence, security, subprocessors, incident notice, audit rights or termination affect the work. Route proposed wording to authorized reviewers.
    3. Record the signed or agreed version, responsible parties and the dates you need to revisit it. Save the source agreement in its restricted store.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Party and service
    Northstar hosting provider, production backup
    Clause or requirement
    Incident notification and contacts
    Current position
    General notice terms. No operational escalation contacts listed.
    Change to review
    Add named response channel and request confirmation of the timing.
    Owner, status and record
    Vendor lead, legal review pending, contract register V-018

    Check before handing it over

    The executed version covers the agreed roles and evidence paths. Review any jurisdiction-specific clauses with counsel.

    Give named obligations to operations and procurement. Use this worksheet to track review and keep the executed agreement as the authority.

  3. 03

    Run consumer rights and verification

    Who Privacy operations When On receipt, with timing based on the request

    Configure request channels, verification, exceptions and applicable response clocks. Train agents and test fulfillment across vendors.

    How to do this step

    Before you start

    Request intake channels, verification procedure, vendor contacts, applicable rights and current response deadlines.

    1. Log the request type, receipt, identity or authorized-agent checks where appropriate and applicable deadline. Keep the queue accessible to a backup owner.
    2. Assign each search, correction or deletion to the owner of the system and relevant recipient. Record statutory exceptions and what information can be released.
    3. Verify response and downstream completion, including how any systems remaining in scope handle the action. Keep a record of the response and approvals.

    What a reviewer should see

    A practice deletion request shows the systems searched, downstream tasks, an exception decision where applicable and the approved response date.

    When to escalate

    Raise a near-deadline case with incomplete searches, a mismatch in identity verification or a system that cannot execute the right.

    What to produce

    Rights request playbookMemo

    Gather first

    • Covered rights and scope exceptions
    • Intake channels and identity verification rules
    • Systems, vendors and escalation contacts

    How to prepare it

    1. Start from each intake channel. Write who logs the request, verifies the requester and calculates the due date under the applicable rule.
    2. Map tasks to system owners. Include gathering records, searching vendors, deciding exemptions, securing replies and obtaining approval for extensions or denials.
    3. Run a test request end to end. Track timestamps, handoffs and output. Fix gaps and repeat the test before putting the procedure into use.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Trigger
    A verified customer requests access through the support form.
    Triage
    Open a case and record receipt time, jurisdiction and deadline.
    Handoffs
    Billing and customer operations return records using restricted links.
    Quality check
    Reviewer checks redactions, exemptions and controller instructions where applicable.
    Close
    Send the response securely and save delivery evidence and date.

    Check before handing it over

    A new case worker can follow the procedure and deliver a test response without inventing missing steps or timings.

    Train intake, operational and backup staff. Make the intake instructions and current contact list easy to find.

    Request logSpreadsheet

    Gather first

    • Case, change or communication records
    • Required fields and timing
    • Named case owner and authorized recipients

    How to prepare it

    1. Give each event a record ID. Record the action or request, receipt or send time, owner and the deadline or next date.
    2. Write the decision and link the response or supporting record. Track delivery, escalation or verification separately so a sent message is distinguishable from an accepted one.
    3. Review open rows on a regular cadence. Restrict personal details to the case system and keep the register to IDs and necessary dates.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Record ID
    REQ-022
    Event and date
    Verified access request received 2026-11-07 UTC
    Owner and target
    Privacy operations, internal review by 2026-11-23
    Decision and status
    Approved response, sent securely
    Completion evidence
    Case delivery record, 2026-11-24
    Follow-up
    None, approved by the reviewer

    Check before handing it over

    Every open item has a next action and closed items have a verifiable record of closure or delivery.

    Use the log at case reviews and provide a restricted copy only where the engagement requires it.

    Response templatesMemo

    Gather first

    • Incident case facts and awareness timestamps
    • Current authority forms and applicable notification criteria
    • Approved recipients and counsel or incident lead

    How to prepare it

    1. Identify the recipient and required fields. Prepare a concise account of what happened, data and people affected, likely consequences, protective steps and an official contact.
    2. Mark unknown facts and state how they will be updated. Confirm recipients and secure delivery or required portal before sending.
    3. Obtain the prescribed approval. Keep the sent version, delivery receipt and any follow-up or supplement with the case.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Recipient and reference
    Approved authority or affected person, incident INC-041
    What happened
    An account viewed a link beyond its permissions. Investigation continues.
    Likely effect and protection
    Access was revoked. Review your recent account activity and contact support for help.
    Contact and update
    Approved incident contact, updated facts after log review
    Approval and record
    Privacy lead approved, receipt recorded in case file

    Check before handing it over

    Use the applicable authority’s language and official portal where required. Every material factual statement can be traced to the case.

    Have the authorized notifier submit through the official channel and add the receipt and follow-up date to the incident log.

  4. 04

    Screen new rules and schedule obligations

    Who Privacy + security leadership When By applicable phase-in and ongoing

    Evaluate cybersecurity audit thresholds, processing risk assessments and ADMT obligations. Record phase-in dates and assign reporting and audit responsibility.

    How to do this step

    Before you start

    Applicable CPPA regulation text, processing and automation inventory, financial inputs and vendor data.

    1. Make separate determinations for audit, risk-assessment and ADMT requirements. Record the rule section, threshold or use case, effective dates and supporting facts.
    2. Give each applicable obligation a decision owner and arrange evidence access, review, assessor independence where required, and submission or certification responsibilities.
    3. Open a fresh screen when an impacted activity, automated use, revenue band or vendor changes. Record who approved the outcome and when you must revisit it.

    What a reviewer should see

    The rollout calendar links each due date to the relevant rule and facts, with owner, internal review milestone and filing location when required.

    When to escalate

    Escalate a launch whose risk assessment or required ADMT safeguards are incomplete, or an audit for which evidence cannot be produced in time.

    What to produce

    Applicability matrixSpreadsheet

    Gather first

    • Official rules or contract and version
    • Product, organization or processing facts
    • Jurisdiction and exception criteria

    How to prepare it

    1. Start with one row per rule, decision or authority. Record the citation, scope test and facts that determine whether it applies.
    2. Distinguish a confirmed decision from an open question. Record the obligation, any exception or approved route, owner and timing.
    3. Have technical and legal or program owners review the decision against the source. Revisit on a new market, product change or rule update.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement or decision
    REG-05, determine whether the new processing activity requires an assessment.
    Source and trigger
    Current regulator guidance, high-risk processing indicators
    Facts and evidence
    New dataset includes sensitive attributes. Data map P-024.
    Outcome and rationale
    Assessment required before release. Privacy lead to confirm scope.
    Owner and review
    Product privacy owner, reassess before launch and on new purposes.

    Check before handing it over

    A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.

    Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.

    Audit calendarSpreadsheet

    Gather first

    • Current obligations, expiry dates or audit window
    • Delivery dependencies and owner availability
    • Official rules or engagement confirmation

    How to prepare it

    1. Separate official due dates, trigger-based clocks and team target dates. Write down the event or rule that starts each clock.
    2. Work backward from each milestone. Include lead time for review and submission, and name the owner and backup.
    3. Cross-check the dates with the source or reviewer and make reminders actionable. Record the next verification point for changing rules.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Milestone
    Quarterly access review approved
    Date and kind
    2026-12-18, internal target
    Trigger or source
    Internal access control schedule v3
    Prerequisite
    Access export by 2026-12-09
    Owner and reminder
    IAM lead, remind one week before
    Status
    Scheduled

    Check before handing it over

    Every external deadline links to a real source. Planning targets are visibly marked.

    Add approved dates to the team calendar and share them with the people scheduled to deliver or review.

    Assessment registerSpreadsheet

    Gather first

    • Processing or service design and affected people
    • Threats, consequences and assessment triggers
    • Risk methodology and current safeguards

    How to prepare it

    1. Screen the activity against the applicable assessment trigger. Describe the real scenario and who or what could be harmed. Record likelihood and consequence using your criteria.
    2. Describe existing safeguards. Decide what reduces the risk and what risk remains after those measures. For a required impact assessment, document necessity, alternatives and consultation where applicable.
    3. Send the result to the person who can approve, change or stop the activity. Set a review trigger and keep evidence of the decision.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Activity and risk
    Account recovery could expose invoices to an impersonator.
    Affected people or assets
    Customer account contacts and invoices
    Current controls
    Recovery uses verified channel. Sampled evidence linked.
    Proposed treatment
    Require a second check for requests to change the billing address.
    Remaining risk and decision
    Moderate under company method. Approval required before launch.
    Owner and review trigger
    Product risk owner, repeat when recovery flow changes

    Check before handing it over

    The assessment explains the potential harm, why each measure helps and who accepts the remaining risk.

    Give the signed review to the owner of the launch or processing decision. Use the regulator’s assessment form where one applies.

Common questions

Does every covered CCPA business need a cybersecurity audit?

The cybersecurity audit rule has its own criteria for processing that presents significant risk to consumers’ security. Check section 7120 for coverage, section 7121 for the first report date and section 7124 for the certification of completion.

CPPA · Final regulations text, §§ 7120–7124, 7155–7157 and 7200 (opens in a new tab)

How should we test Global Privacy Control?

Send a real preference signal from a supported browser and check how your site responds, including downstream tags and partners affected by the opt-out. Record the domain, test date, request and observed behavior, and repeat after changes.

CPPA · Statute and current regulations (opens in a new tab)
PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes