Thresholds 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.
Structured answer sets in this page tree.
Cited legal and guidance references.
This page maps US CCPA obligations for Thresholds to trigger conditions, accountable owners, required deadlines, evidence records, and review paths that product, legal, privacy, security, and compliance teams can apply.
Start by checking whether the business meets the CCPA applicability thresholds: it does business in California and has annual gross revenues in excess of $25 million, buys, sells, or shares the personal information of 100,000 or more consumers or households, or derives 50 percent or more of annual revenues from selling or sharing consumers' personal information. If the business meets one of those thresholds, it should then map the obligations that apply, including notices, rights handling, opt-out controls, and contract requirements.
Keep the California source, threshold calculation, notice text, consumer-right workflow, opt-out/GPC evidence, and service-provider contract record together so the CCPA decision can be reviewed later.
Ownership should sit with the team that can change notices, request intake, ad-tech settings, vendor contracts, data retention, or consumer-facing controls, with privacy/legal review for ambiguous cases.
Evidence should show threshold calculations, notice-at-collection placement, privacy-policy disclosures, rights request logs, opt-out/GPC handling, vendor restrictions, and enforcement-response readiness.
Most CCPA mistakes happen at the boundary between a business, service provider, contractor and third party, or between selling, sharing, financial incentives, minors, GPC, and data-broker obligations.
Apply this section before launching a collection point, ad-tech flow, rights workflow, vendor onboarding, financial incentive, minor-focused journey, or data-broker process.
Use a CCPA workflow that captures threshold status, data category, collection point, consumer right, opt-out or GPC trigger, vendor role, evidence, owner, and review date.
The output should be a threshold note, notice update, DSAR decision, opt-out/GPC record, vendor clause map, dark-pattern review, or enforcement evidence pack.
This US CCPA guide turns Thresholds into owners, evidence requests, review checkpoints, and reusable operating records inside Sorena.
Turn Thresholds into scoped questions, evidence fields, and review tasks.
Use Research Copilot to answer follow-up questions with cited source material.
Review scope, evidence, owners, and the next compliance actions with Sorena.
"does business in the State of California, and that satisfies one or more of the following thresholds"
"On March 29, 2023, the Office of Administrative Law approved the California Privacy Protection Agency's regulations"
"A business shall process any opt-out preference signal that meets the following requirements"
"The contract required by the CCPA for service providers and contractors shall"
"Every odd-numbered year, Civil Code § 1798.199.95(d) adjusts the following monetary thresholds"