Use the preceding calendar year's facts to decide whether an entity is a business covered by the CCPA as amended by the CPRA.
Test California nexus and each threshold first, then analyze related entities and exemptions by data set. An exemption for particular information does not automatically exempt the entity.
The CPRA amended the CCPA rather than creating a separate law. This test asks whether an entity is a covered : generally a for-profit entity doing business in California that determines why and how consumers' personal information is processed and meets at least one current revenue, volume, or sale-or-sharing-revenue threshold. It then checks related-entity rules and data-specific exemptions instead of treating an exempt data set as an exemption for the whole organization.
1
Section 1
What should the US CPRA Applicability Test decide?
Start with the entity, not the product. The entity must generally be organized or operated for profit, do in California, determine the purposes and means of processing consumers' personal information, and meet at least one threshold based on the preceding calendar year. The revenue threshold is $26.625 million, effective January 1, 2025; the alternatives are buying, selling, or sharing the personal information of 100,000 or more California consumers or households, or deriving 50 percent or more of annual revenue from selling or sharing consumers' personal information. Record which threshold applies and the measurement period rather than carrying forward an old scope result.
Then test statutory extensions. An entity that controls or is controlled by a covered and shares common branding with it may itself be covered; control includes ownership or voting power over more than 50 percent, control over selection of a majority of directors or similar managers, or power to exercise a controlling influence over management. A joint venture or partnership in which each business holds at least a 40 percent interest is treated as a business for the joint venture's processing, while each participant remains a separate business for its own processing. The statute also permits an entity to certify voluntarily to the Agency that it is bound by the CCPA.
Finally, analyze exemptions at the information and activity level. The statute contains rules for information governed by laws such as the CMIA, HIPAA, and GLBA, and for specified credit-reporting activity. Government agencies and nonprofit entities generally fall outside the definition of . The former employee and business-contact exemptions expired on January 1, 2023, so those contexts cannot be excluded on that historical basis.
Record the legal entity, ownership structure, common branding, California activities, and who determines processing purposes and means.
Calculate each threshold from the preceding calendar year and retain the revenue source, measurement period, California consumer-or-household count method, deduplication rule, and sale-or-sharing revenue calculation.
Map each claimed exemption to the exact data, actor, and processing activity it covers; do not write 'HIPAA exempt' or 'GLBA exempt' as an entity-wide conclusion unless the statutory test supports it.
State the result as covered, not covered, or unresolved, with the facts that would change the answer and a review trigger for acquisitions, reorganizations, new California activity, or threshold changes.
Who owns the applicability decision, and what evidence should be retained?
Privacy or legal should own the legal conclusion, while finance supplies revenue evidence, data governance supplies consumer and household counts, and corporate teams confirm ownership and branding. The decision record should make those inputs traceable instead of relying on a checkbox.
Keep a dated scope memorandum with the entity chart, California nexus, preceding-year calculations, data-set exemptions, assumptions, cited statutory provisions, approver, and next review trigger. If the conclusion is that the law does not apply, preserve enough evidence to reproduce that conclusion.
Finance: retain the preceding calendar year's gross-revenue calculation and identify the entity whose revenue was measured.
Data governance: retain the deduplicated consumer-or-household counting method and the data flows classified as buying, selling, or sharing.
Corporate or legal: retain common-control, common-branding, joint-venture, and California-nexus evidence.
Privacy: record each exemption by data set and purpose, the final conclusion, open legal questions, and the event that requires reassessment.
Revenue alone is not the only threshold. A below $26.625 million can still be covered by the 100,000-consumer-or-household test or the 50-percent sale-or-sharing-revenue test. Conversely, a large entity still must satisfy the business definition and California nexus.
Count California consumers and households under the statutory definitions and document how duplicates, multiple devices, and records belonging to one household are handled. Determine whether an advertising or disclosure flow is a sale or sharing before excluding it from the count. Publicly available information and deidentified or aggregate consumer information have specific definitions; labels in a data catalog do not settle those tests.
Reassess after a merger, acquisition, new common brand, California launch, new monetization model, material data-flow change, or annual threshold adjustment.
Do not use the expired employee or -contact exemptions for processing after 2022.
Do not assume regulated organizations are wholly exempt when the statute exempts only specified information or activities.
Check whether a recipient relationship causes a disclosure to count as sale or sharing, including whether the required service-provider or contractor contract exists.
Keep unsettled California-nexus, common-branding, household-counting, and exemption questions visible rather than forcing a yes-or-no result.
If the entity is covered, move from the scope memorandum to a data inventory and control plan for notices, consumer requests, sale and sharing opt-outs, opt-out preference signals, sensitive personal information, retention, reasonable security, and recipient contracts. Screen the 2026 risk-assessment, cybersecurity-audit, and ADMT regulations separately because each has its own trigger.
If the entity is not covered, retain the negative determination and schedule a review after the next calendar-year close or earlier if a trigger event occurs. A not-covered conclusion does not displace sector-specific privacy, security, breach, data-broker, or contract duties.
Covered: assign the requirements inventory and implementation plan to named owners.
Not covered: retain the calculation, exemption analysis, approver, and next review date.
Partly exempt: mark the exact data and processing covered by each exemption and apply CCPA controls to the remainder.
Unresolved: identify the missing fact or legal interpretation and stop the affected decision until it is resolved.