In brief GDPR compliance is not CCPA compliance: the European model asks permission up front, the Californian one requires a way to object afterwards.
What the CCPA is
The CCPA took effect on 1 January 2020. In November 2020 California voters approved Proposition 24, the California Privacy Rights Act (CPRA), which extends the law and created a dedicated regulator, the California Privacy Protection Agency.
When people say CCPA today they usually mean the extended version. Both names describe the same body of rules at two stages.
Who it applies to
It applies to for-profit businesses doing business in California that meet at least one of three thresholds:
- gross annual revenue over 25 million US dollars
- buying, selling or sharing the personal information of 100,000 or more California residents or households
- deriving 50 percent or more of annual revenue from selling California residents' personal information
A Californian establishment is not required. What counts is doing business there and processing residents' data — which is why it reaches European providers with US customers.
What rights it grants
Four rights sit at the core: to know what data is collected and how it is used and shared; to have it deleted (with exceptions); to opt out of sale or sharing, including through the Global Privacy Control signal; and to non-discrimination for exercising those rights.
The CPRA added a right to correction and a right to limit the use of sensitive personal information.
How it differs from the GDPR
This is where European companies most often get it wrong. The GDPR works on permission first: no legal basis, no processing. The CCPA works on objection afterwards: processing is permitted, and the person must be able to stop it.
That has a practical consequence. A GDPR banner asking for consent up front does not automatically satisfy the Californian requirement — that needs a reachable opt-out and respect for the GPC signal. Conversely, an opt-out alone does not meet European requirements.
What it means for a website
If a business falls under the CCPA, three things are visible: a route to opt out of sale and sharing, a privacy notice naming categories and purposes, and honouring the GPC signal that some browsers and extensions send automatically.
The GPC signal is the part most often missed technically: it arrives as a header or a JavaScript property and has to be evaluated server-side or in the consent platform. A banner on its own does not see it.
Manuel Riveiro Rodriguez CEO & Digital Strategist
A technical audit covers this and everything else in one pass.
Request an audit Frequently asked
Does the CCPA affect us if we are based in Europe?
It may. What matters is not where the company sits but whether it does business in California, processes residents' data and meets one of the three thresholds. A European shop with US customers can fall under it.
Can we reuse our GDPR banner for the CCPA?
Not as it stands. The European banner collects consent up front; California requires an opt-out route and attention to the GPC signal. Many consent platforms support both models, but it has to be switched on.
What counts as «selling» data?
The definition is broad and does not require money. Disclosing data to a third party for valuable consideration can be enough, which is why many common advertising integrations fall under sale or sharing.
What is the GPC signal?
Global Privacy Control is a signal a browser or extension sends automatically to express an opt-out. In California it must be treated as a valid request, without the person clicking anything on the site.
Who enforces it?
The California Privacy Protection Agency, created by the CPRA, together with the state Attorney General. This text explains the framework; assessing a specific case requires legal advice.
Sources
- California Attorney General — California Consumer Privacy Act (CCPA)
- California Privacy Protection Agency — Regulations
- Global Privacy Control — signal specification