Consumer Rights Workflow decisions under the US CCPA should be written in operational language: who is in scope, what must happen, what evidence proves it, and when escalation is needed.
This guide converts official requirements into scope, evidence, ownership, and review decisions for practical implementation, supporting implementation planning and should be validated against jurisdiction-specific legal, contractual, and policy requirements before implementation.
This page maps US CCPA obligations for Consumer Rights Workflow to trigger conditions, accountable owners, required deadlines, evidence records, and review paths that product, legal, privacy, security, and compliance teams can apply.
1
Section 1
How should a Consumer Rights Workflow run under the US CCPA?
Run the workflow as California privacy operations: intake the request or signal, identify the right involved, verify identity only when required, route the request to the right owner, meet the response deadline, and document the outcome for review. For delete, correct, know, and ADMT access requests, businesses must confirm receipt within 10 business days and generally respond within 45 calendar days, with one 45-day extension if they notify the consumer. For opt-out of sale/sharing and limit requests, the business should comply as soon as feasibly possible, and no later than 15 business days. If the request cannot be verified or another CCPA exception applies, the business may deny the request and should explain why.
Capture the request type, channel, consumer or browser context, deadline, owner, and whether verification is required.
Check whether the request is for delete, correct, know, opt-out of sale/sharing, limit, or ADMT access and apply the matching rule.
If the business cannot comply, record the specific denial reason and the facts that support it.
Keep the response, evidence location, and escalation path in plain language so support, product, legal, security, and compliance teams can follow it.
What fields should the Consumer Rights Workflow template capture?
A useful template captures the source, who or what the request applies to, the right involved, the decision, the deadline, and the evidence trail needed to show the business acted correctly.
Source URL and the exact source quote that supports the decision.
Entity, product, service, system, data category, and user group with enough detail to show what is in scope.
Decision result, control action, owner, reviewer, due date, and any escalation reason.
Evidence attachment, approval note, exception note, and review cadence for follow-up.
How should teams review and improve the Consumer Rights Workflow?
Review the workflow after CPPA updates, ad-tech changes, new collection points, vendor changes, consumer complaints, enforcement advisories, or material product changes.
Track recurring exception categories and update intake questions.
Remove fields that never affect the decision.
Add fields when reviews show missing source evidence or unclear ownership.
Confirm generated markdown and page content include the same visible source-linked guidance.
"No later than 10 business days after receiving a request to delete, request to correct, request to know, request to access ADMT, or request to appeal ADMT, a business shall confirm receipt of the request."