Data Broker Crossover 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 explains, in plain terms, when a CCPA-covered business also counts as a data broker: a business that knowingly collects and sells to third parties the personal information of a consumer with whom it does not have a direct relationship. It maps US CCPA obligations for Data Broker Crossover to trigger conditions, accountable owners, required deadlines, evidence records, and review paths that product, legal, privacy, security, and compliance teams can apply.
Start by deciding whether the issue affects business-threshold status, notice at collection, privacy policy disclosures, consumer rights, do-not-sell/share controls, GPC, service-provider restrictions, or enforcement exposure. The useful answer should name the exact trigger, affected product or process, required action, owner, evidence, and escalation point.
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, consumer-request decision, opt-out/GPC record, vendor clause map, dark-pattern review, or enforcement evidence pack.
This US CCPA guide turns Data Broker Crossover into owners, evidence requests, review checkpoints, and reusable operating records inside Sorena.
Turn Data Broker Crossover 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.
"Collect, use, retain, sell, share, or disclose consumers' personal information that is deidentified"
"refrain from selling or sharing the consumer's personal information"
"The definitions in Section 1798.140 shall apply unless otherwise specified"
"The regulations became effective on March 29, 2023."
"To fulfill its duties, the Agency is authorized to adopt and amend regulations through the Administrative Procedures Act"