Use this hub to decide whether the CCPA applies, which consumer right or processing rule is triggered, what deadline controls, and which detailed FAQ to open next.
Apply the cited California statute and regulations to the actual entity, data flow, system, and recipient role; escalate unresolved legal interpretation.
The CPRA amended California's CCPA; it is not a separate parallel privacy statute. This FAQ hub orients businesses to coverage, consumer rights, sale and sharing choices, sensitive personal information, vendor roles, retention, and the newer cybersecurity, risk-assessment, and regulations.
Browse sub-FAQs
Choose the question set you need
These focused FAQ modules break this artifact into narrower answer sets so teams can move straight to the right source-backed guidance.
How should teams use the California CPRA FAQ hub for privacy compliance decisions?
Start with entity coverage. A for-profit entity doing business in California is a if it determines the purposes and means of processing and meets at least one statutory test: the current adjusted gross-revenue threshold, buying, selling, or sharing the personal information of at least 100,000 consumers or households in a year, or deriving at least 50% of annual revenue from selling or sharing consumers' personal information. Parent, subsidiary, joint-control, nonprofit, sectoral, and data-specific rules can change the result, so document the legal entity and data flow before applying a control.
Next identify the action: notice at collection; a request to know, delete, or correct; an opt-out of sale or sharing; a signal; a request to limit sensitive personal information; a vendor-role contract; retention; or a newer cybersecurity audit, risk assessment, or duty. For ADMT used to make a significant decision, identify the separate pre-use notice, opt-out, access, and any human-appeal path. The CPRA is an amendment to the CCPA, while the Delete Act's data-broker registry and DROP duties come from a separate California title.
Name the exact trigger, consumer or data category, responsible business process, deadline, owner, downstream recipients, evidence, and escalation point. Use the detailed FAQ for the selected issue rather than applying one answer across unrelated rights.
Record the applicable legal entity and which coverage test it meets before assessing a right or processing duty.
Record which role, product, system, customer group, or data flow is in scope.
Attach the cited rule, the owner, and the evidence field before approving the control.
Escalate uncertainty when the facts depend on adjusted thresholds, statutory exemptions, household counts, recipient roles, or a case-specific interpretation.
Current regulations governing disclosures, consumer requests, opt-out preference signals, sensitive-information limits, recipient contracts, risk assessments, cybersecurity audits, and ADMT.
2
Question 2
Who should maintain the California CPRA FAQ evidence and source-review process?
Assign operational ownership to the team that can change the relevant system: privacy operations for request intake, product and engineering for interfaces and preference signals, procurement and legal for recipient contracts, data owners for retention, and security leadership for audits. Privacy counsel should review coverage, exemptions, denials, and other legal interpretations.
Consumer requests to delete, correct, know, access , or appeal ADMT generally require confirmation within 10 business days and a response within 45 calendar days, with one explained extension of up to 45 additional days when allowed. The response period starts when the business receives the request, regardless of verification time. Sale-or-sharing opt-outs, ADMT opt-outs, and sensitive-information limitation requests follow different rules, including a 15-business-day outer limit for stopping the covered processing and sending required downstream instructions. Keep each clock tied to the correct request type.
Evidence should show the coverage analysis, collection notices, request handling, GPC processing, sensitive-information purpose mapping, recipient contracts, retention controls, and any risk-assessment, cybersecurity-audit, or readiness work that the actual processing triggers.
Name one accountable owner and one reviewer for the FAQ workflow.
Keep source screenshots or source links, decision notes, implementation tickets, and approval records together.
Use dated evidence for deadlines, notices, risk assessments, contracts, user journeys, and regulator-facing records.
Review the evidence after product changes, new markets, new vendors, enforcement updates, or material changes in the source text.
Official CPPA registry source for California data-broker registration context referenced by this FAQ hub.
The previous data broker registries can be accessed at the Office of the Attorney General's Data Broker webpage.
3
Question 3
Which edge cases should teams check before relying on California CPRA FAQ guidance?
Do not treat a sectoral or data-specific exemption as an entity-wide exclusion unless the statute says it is one. Publicly available information, deidentified information, employee records, business contacts, regulated financial or health data, and data handled by government bodies each require the exact statutory definition and facts. The temporary employee and business-contact exemptions expired after 2022, so current employment and business-contact processing cannot be excluded on that historical basis.
Reassess before a material change to the data, purpose, interface, vendor, recipient role, system logic, or law. In particular, distinguish selling from sharing for cross-context behavioral advertising, a service provider from a third party, and a sensitive-data use that is limitable from one allowed by section 7027(m). A signal applies at least to the browser or device that sends it and must also reach a known account when the business can associate the signal with that consumer.
Check whether the rule changes for minors, consumers, business users, public-sector bodies, regulated sectors, high-risk services, or cross-border transfers.
Separate binding law, regulator guidance, consultation material, standards, and enforcement commentary in the evidence record.
Do not rely on a previous answer if the data categories, user interface, vendor role, or contractual flow changed.
Track unresolved assumptions in an open-questions section and route legal interpretation points for review.
Official CPPA registry source for California data-broker registration context referenced by this FAQ hub.
The previous data broker registries can be accessed at the Office of the Attorney General's Data Broker webpage.
4
Question 4
How should teams turn California CPRA FAQ guidance into owned controls?
Use one intake that captures entity coverage, data categories and purposes, consumer right, opt-out signal, recipient role, retention logic, cybersecurity-audit, risk-assessment and triggers, owner, deadline, and review date.
The result should be a specific record: a coverage memo, notice update, consumer-request workflow, opt-out and GPC test record, sensitive-information purpose map, vendor clause map, retention schedule, risk assessment, rights package, or cybersecurity-audit evidence pack.
Create a short intake question that identifies the FAQ scenario.
Map the answer to a required action, evidence field, owner, reviewer, and review date.
Review the flow for scope, deadlines, controls, penalties, and templates before moving to the next implementation step.
Update the workflow when official source material changes or when non-public evidence shows recurring exceptions.
Official California statutory source for opt-out preference signals, sale or sharing opt-outs, and cross-context behavioral advertising rulemaking authority.
"Global opt out from sale and sharing of personal information"