Governance DocsGovernance Docs
Browse Toolkits

CART

No products in the cart.

Skip to content

CCPA vs GDPR: 8 Clear Differences and the 2026 Deadlines Compared

CCPA vs GDPR explained

CCPA vs GDPR is the comparison every company with Californian customers and European ones has to make, and the mistake in it runs both ways: treating GDPR compliance as automatically covering California, or building a Californian programme and assuming it satisfies Europe. The General Data Protection Regulation is a comprehensive law that applies to any organisation processing EU residents’ data, requires a lawful basis before processing starts, and fines up to €20 million or 4% of global turnover.

The California Consumer Privacy Act, as amended by the CPRA and now surrounded by the Privacy Protection Agency’s 2026 regulations, applies to for-profit businesses over defined thresholds, lets processing proceed by default subject to opt-out rights, and fines per violation — $2,663, or $7,988 for intentional violations and those involving children under 16, since the 2025 inflation adjustment. This guide sets out the eight differences that decide what a programme built for one has to add for the other, where the two have converged since 2023, and how to run a single privacy programme across both.

CCPA vs GDPR: eight differences and where they converge
Who is covered · legal basis vs opt-out · the rights · sensitive data · risk assessments vs DPIAs · processors · enforcement and fines · private action — and the 2026 California regulations that closed part of the gap.

Free gap assessment

Could you demonstrate GDPR compliance today?

Score yourself against what a supervisory authority actually asks for, free — the records, not the policy.

Run the free GDPR gap assessment →  or  View premium report sample

CCPA vs GDPR at a glance

Dimension GDPR (Regulation (EU) 2016/679) CCPA as amended by the CPRA, with the 2026 regulations
Who is covered Any controller or processor established in the EU, or offering goods or services to or monitoring people in the EU, whatever its size or sector For-profit businesses doing business in California that exceed $26,625,000 in annual revenue, or buy, sell or share the personal information of 100,000 or more consumers or households, or derive 50% or more of revenue from selling or sharing; plus their service providers, contractors and third parties
Whose data Data subjects in the EU California residents as consumers — including employees, contractors, job applicants and B2B contacts since 1 January 2023
Basis for processing A lawful basis under Article 6 before processing — consent, contract, legal obligation, vital interests, public task or legitimate interests No prior basis; processing is lawful by default subject to notice at collection, purpose limitation, data minimisation and the consumer’s rights to opt out and limit
Consumer rights Access, rectification, erasure, restriction, portability, objection, and rights about automated decisions (Articles 15–22) Know, delete, correct, opt out of sale or sharing, limit use of sensitive personal information, non-discrimination, and — from 1 January 2027 — notice, opt-out and access rights for automated decision-making technology
Sensitive data Special categories under Article 9, prohibited unless an exception applies Sensitive personal information: a right to limit use to what is necessary, plus a risk assessment before processing
Risk assessment A data protection impact assessment under Article 35 for high-risk processing, with prior consultation where residual risk is high A risk assessment under Article 10 of the regulations before selling or sharing, processing sensitive data, using ADMT for significant decisions or training it — with a summary filed with the Agency each year
Fines Up to €10 million or 2% of worldwide turnover, or €20 million or 4% for the more serious infringements (Article 83) Administrative fines up to $2,663 per violation, or $7,988 for intentional violations and violations involving consumers known to be under 16; no cure period since 2023
Private action Article 82: compensation for material or non-material damage for any infringement Section 1798.150 only: $107 to $799 per consumer per incident, or actual damages, for data breaches caused by a failure to maintain reasonable security

Difference 1: who is covered

The GDPR has no size threshold; a two-person consultancy processing EU customer data is a controller. The CCPA has three, and meeting any one is enough — revenue above $26,625,000 (adjusted every two years), personal information of 100,000 or more consumers or households, or half of revenue from selling or sharing. The third catches data brokers and ad-tech regardless of size; the first two exclude most small businesses entirely. The CCPA vs GDPR scope question therefore has opposite answers for a small company: probably in scope of the GDPR, probably out of scope of the CCPA.

CCPA vs GDPR difference 2: lawful basis against opt-out

This is the structural difference the rest follow from. Under the GDPR nothing may be processed without one of the Article 6 bases, and consent must be freely given, specific, informed and unambiguous.

Under the CCPA a business may collect and use personal information once it has given notice at collection, provided the use is compatible with the disclosed purposes and reasonably necessary and proportionate; the consumer’s protection is the right to opt out of sale and sharing and to limit the use of sensitive personal information, which the business must honour — including through opt-out preference signals such as Global Privacy Control. Consent appears in the CCPA only at the edges: children under 16, financial incentives, and re-entering a consumer into sale after an opt-out.

Difference 3: the rights, and who holds them

The lists overlap heavily — access, deletion, correction, portability in both — but California’s are held by a wider population. Since 1 January 2023 employees, job applicants, contractors and business-contact individuals are consumers with full rights, and the Agency’s first seven-figure enforcement decision, against Tractor Supply in September 2025, turned partly on the privacy rights of job applicants. The GDPR has always covered employees; the CCPA’s late arrival there is why HR data is the most common gap in a US programme extended from marketing.

Difference 4: risk assessments against DPIAs

The CCPA vs GDPR gap on assessments narrowed in 2026 but did not close. The GDPR’s DPIA under Article 35 is required for processing likely to result in a high risk, with the supervisory authority consulted if residual risk stays high. California’s risk assessment is required for a fixed list of activities regardless of a high-risk judgement, must contain nine specified elements including named contributors and an executive approver, must be updated within 45 days of a material change, and is reported to the Agency in summary each year under penalty of perjury.

Free privacy risk assessment

Which privacy risks would hurt the people whose data you hold?

List your personal data and processing, pick from 38 privacy risk scenarios, rate them for the people concerned and for you, and plan treatment with ISO 27701 controls. You get a heat map, a process score and the findings an auditor would raise, free.

Run the free privacy risk assessment →  or  View premium report sample

Section 7156 of the regulations lets a DPIA count only if it contains everything the California rule requires; in practice a DPIA needs the minimum-data statement, the vendor list with purposes and the decision record added. Our guide to the CCPA risk assessment covers the nine elements.

Difference 5: processors against service providers

The GDPR’s controller–processor model rests on Article 28: a written contract with prescribed terms, sub-processor authorisation, assistance duties, and a processor that is itself directly liable for some obligations. The CCPA’s service provider and contractor roles rest on the contract too — prohibitions on selling or sharing, on use outside the business purpose, on combining data, and a right to audit — but the consequence of a missing term is different: the vendor becomes a third party and the transfer becomes a sale or share, which triggers opt-out rights and a risk assessment. Our guide to CCPA service providers vs contractors covers the terms.

Difference 6: security audits

The GDPR requires appropriate technical and organisational measures under Article 32 and leaves the method to the controller. California’s 2026 regulations require businesses above defined processing thresholds to complete an annual cybersecurity audit by an independent auditor against 18 named components, with the first reports due from 1 April 2028 and a certification filed with the Agency each year. Nothing in the GDPR mandates an audit of that shape. Our guide to the CCPA cybersecurity audit covers it.

Difference 7: enforcement and fines

The GDPR is enforced by national supervisory authorities with turnover-based fines and a one-stop-shop for cross-border cases. The CCPA is enforced by the California Privacy Protection Agency through administrative decisions and by the Attorney General through civil actions, with per-violation amounts that scale with the number of consumers affected: Honda paid $632,500 in March 2025, Todd Snyder $345,178 in May 2025 and Tractor Supply $1.35 million in September 2025, while data brokers have been fined for registration failures under the Delete Act through 2026. The headline numbers are smaller than Europe’s; the per-consumer arithmetic on a large breach or a broken opt-out is not. Our guide to CCPA penalties covers the amounts.

2026 raised the ceiling on the California side. In May the Attorney General, four county district attorneys and CalPrivacy announced a $12.75 million settlement with General Motors over the sale of drivers’ location and driving data to data brokers — subject to court approval, the largest CCPA penalty to date and the first case brought on the data-minimisation principle. On the GDPR side the record remains the €1.2 billion fine the Irish Data Protection Commission imposed on Meta in May 2023 over transfers of EU users’ data to the US.

Difference 8: the private right of action

Article 82 of the GDPR gives any data subject a right to compensation for any infringement, and European courts have awarded damages for non-material harm. The CCPA’s private right of action is confined to section 1798.150: a data breach of unencrypted, unredacted personal information caused by a failure to implement reasonable security, with statutory damages of $107 to $799 per consumer per incident. Every other CCPA violation is for the regulators alone — but the breach action, multiplied across a large consumer base, is the largest single exposure in the statute.

CCPA vs GDPR deadlines: requests, opt-outs and breaches

The clocks are where a programme built for one regime most often fails the other. The GDPR counts in months and hours; California counts in business days and calendar days, and since 1 January 2026 it has a fixed deadline for breach notices to consumers that it never had before.

Obligation GDPR CCPA and California law
Acknowledge a rights request No separate acknowledgement step; the one-month clock runs from receipt Confirm receipt within 10 business days (§ 7021 of the regulations)
Answer a request to access, delete or correct Within one month of receipt, extendable by two further months for complex or numerous requests, with the person told within the first month (Article 12(3)) Within 45 calendar days, extendable once by a further 45 days with notice and an explanation (§ 7021)
Act on an opt-out An objection to direct marketing must be honoured with no balancing test (Article 21(3)); the response falls under the one-month rule Stop selling and sharing as soon as feasibly possible and no later than 15 business days after receipt (§ 7026)
Notify the regulator of a breach The supervisory authority within 72 hours of becoming aware, unless the breach is unlikely to result in a risk to people (Article 33) A sample of the consumer notice to the Attorney General when more than 500 Californians are notified, now with a 15-calendar-day deadline (Civil Code § 1798.82 as amended by SB 446)
Notify affected people of a breach Without undue delay where the breach is likely to result in a high risk (Article 34) Within 30 calendar days of discovering or being notified of the breach, subject to law-enforcement and scoping exceptions (SB 446, from 1 January 2026)
Deletion requests through a central platform None; every erasure request goes to the individual controller (Article 17) Registered data brokers must access the Delete Request and Opt-out Platform (DROP) at least every 45 days and process the deletion requests in it, from 1 August 2026 (Delete Act)

Two practical consequences follow. A single global intake process should run to the shorter clock in each pair: acknowledge within 10 business days and answer within one month, which satisfies both the GDPR’s one month and the CCPA’s 45 days. And the incident response plan needs two tracks — a 72-hour regulator notice for Europe and a 30-day consumer notice for California — because a European notification made on time does not discharge the California consumer notice, and the reverse is also true.

Children, transfers, DPOs and records

Four further obligations sit on only one side of the CCPA vs GDPR line, or look very different on each.

Topic GDPR CCPA
Children Parental consent for information society services offered directly to a child under 16; member states may lower the age to 13 (Article 8) Opt-in consent before selling or sharing the personal information of a consumer aged 13 to 15, and a parent’s consent under 13; violations involving consumers known to be under 16 carry the higher $7,988 fine
International transfers Chapter V: an adequacy decision (including the EU–US Data Privacy Framework for certified US recipients), standard contractual clauses or binding corporate rules No transfer restriction; data may leave California or the US subject only to the notice and contract rules
DPO and representative A data protection officer is mandatory for public authorities and for organisations whose core activities involve large-scale monitoring or large-scale special-category data (Article 37); a non-EU controller in scope must appoint an EU representative (Article 27) No DPO or in-state representative requirement; accountability sits with the business, and the risk-assessment and cybersecurity-audit filings are signed by a member of executive management
Records A record of processing activities under Article 30 Records of consumer requests and how they were answered, kept for at least 24 months (§ 7101), plus the inventory that notice at collection and risk assessments depend on

The transfer row surprises US companies most. A GDPR programme needs a lawful transfer mechanism for every EU-to-US data flow — including to its own US parent company and its US SaaS vendors — and nothing in a California programme prompts that analysis.

Where CCPA vs GDPR has converged

  • Data minimisation and purpose limitation are now express CCPA requirements, not only GDPR principles.
  • Risk assessments and automated decision-making rights arrived in California with the 2026 regulations, closing the largest structural gap with Articles 22 and 35.
  • Sensitive data has a distinct regime in both.
  • Contracts with processors and service providers are prescriptive in both.
  • Regulators cooperate: the CPPA signed declarations of cooperation with the UK ICO (now the Information Commission) and France’s CNIL in 2024–25.

What changed in 2026 on each side

Date Regime Change
1 Jan 2026 CCPA The CCPA updates regulations took effect: risk assessments for listed processing activities, annual cybersecurity audits and automated decision-making technology (ADMT) rules
1 Jan 2026 California breach law SB 446: a 30-calendar-day deadline for consumer breach notices and a 15-day deadline for the Attorney General sample notice
1 Jan 2026 GDPR Regulation (EU) 2025/2518 on procedural rules for cross-border enforcement entered into force; it applies from 2 April 2027
8 May 2026 CCPA The Attorney General, four county district attorneys and CalPrivacy announced a $12.75 million settlement with General Motors, subject to court approval — the largest CCPA penalty to date and the first data-minimisation case
1 Aug 2026 Delete Act Registered data brokers must process deletion requests from the DROP platform at least every 45 days
Oct 2026 GDPR EU governments agreed the Council’s negotiating position on the Digital Omnibus amendments to the GDPR; the European Parliament has not adopted its position, so the GDPR applies unchanged
1 Jan 2027 CCPA Compliance date for the ADMT requirements where ADMT is used for significant decisions
1 Apr 2028 CCPA First risk-assessment submissions to CalPrivacy and the first cybersecurity audit certifications for the largest businesses; audits phase in by revenue through 2030

The GDPR’s substantive text has not changed in 2026; the movement in Europe is procedural and prospective. California’s rules changed more in one year than in the previous three, which is why a CCPA vs GDPR gap analysis written in 2024 is now out of date on the California side.

One programme for both

  1. Build the inventory to the higher standard — GDPR’s record of processing plus the CCPA’s categories, sources, purposes and recipients — once.
  2. Run the GDPR lawful-basis analysis for everyone; it costs little in California and prevents the “we never thought about why” finding.
  3. Honour opt-outs and preference signals globally where the engineering allows; it is simpler than geo-fencing.
  4. Write one assessment template that satisfies Article 35 and Article 10 — the nine California elements plus the DPIA’s necessity and proportionality analysis.
  5. Keep two contract schedules — Article 28 terms and CCPA service-provider terms — because the consequences of omission differ.
  6. Cover the workforce under both.

Frequently asked questions

What is the main difference between CCPA vs GDPR?
The GDPR requires a lawful basis before any processing and applies to organisations of any size handling EU residents’ data, with fines up to 4% of turnover; the CCPA applies to for-profit businesses over revenue or volume thresholds, allows processing by default subject to notice and opt-out rights, and fines per violation — $2,663 or $7,988 since 2025 — with a private right of action limited to data breaches.

Does GDPR compliance cover the CCPA?
Mostly, but not entirely: California adds opt-out preference signals, the workforce as consumers, service-provider contract terms with different consequences, a nine-element risk assessment reported to the Agency, and from 2028 an independent cybersecurity audit.

Does CCPA compliance cover the GDPR?
No. A California programme lacks the lawful-basis requirement, consent standards, restriction and objection rights, the DPIA consultation route, international transfer rules and a general right to compensation.

Which has bigger fines?
The GDPR’s ceiling — €20 million or 4% of worldwide turnover — is far larger; the CCPA’s per-violation amounts multiply by affected consumers, and the largest CCPA penalty to date is the $12.75 million General Motors settlement announced in May 2026.

Are employees covered by the CCPA?
Yes, since 1 January 2023: employees, applicants, contractors and business contacts hold full consumer rights.

How fast must you answer a request under CCPA vs GDPR?
The GDPR allows one month from receipt, extendable by two further months for complex or numerous requests. The CCPA requires confirmation of receipt within 10 business days and an answer within 45 calendar days, extendable once by 45 more; opt-outs must be actioned within 15 business days. A one-month global target satisfies both.

Is the GDPR being amended?
The Commission proposed GDPR amendments in its Digital Omnibus package in November 2025. As of November 2026 the Council has agreed a negotiating position but the European Parliament has not, so nothing has changed yet. Separately, Regulation (EU) 2025/2518 changes how cross-border complaints are handled from 2 April 2027, without changing what controllers must do.

Do I need a data protection officer for the CCPA?
No. The CCPA has no DPO or representative requirement. The GDPR requires a DPO only for public authorities and for large-scale monitoring or large-scale special-category processing, and an EU representative for non-EU controllers in scope.

Where this leaves you

Treat CCPA vs GDPR as two regimes with one inventory: the GDPR’s lawful basis and consent standard as the floor for everyone, California’s opt-out mechanics, workforce coverage, risk-assessment reporting and cybersecurity audit as the additions, and one assessment template that satisfies both. The convergence since 2023 is real; the differences that remain are exactly the ones a programme built for the other side will miss.

References

More on the CCPA

The Privacy Program Framework, the Data Processing Inventory and Record of Processing Activities, the Cross-Border Data Transfer Policy, the Consumer Rights Policy and the Right to Opt-Out of Sale/Sharing Procedure are in the CCPA-CPRA Compliance Toolkit, or start with the free templates.

When a standard changes, know first

One email a month: edition changes, new deadlines, and what they mean for documentation you already have. No sales sequence.

We don’t spam! Read our privacy policy for more info.