GDPRvsCCPA/CPRA
See exactly how GDPR controls map to CCPA/CPRA. Pre-computed mappings, identified gaps, and coverage analysis.
A reviewed coverage crosswalk for this pair is available. See which CCPA/CPRA controls you already evidence.
According to the TheArtOfService Compliance Knowledge Graph:
GDPR maps to CCPA/CPRA with 62% coverage across 25 directly mapped controls. Analysis of 40 GDPR controls identifies 15 compliance gaps, primarily concentrated in Chapter IV - Controller and Processor.
Source: TheArtOfService Knowledge Graph | 40 controls analysed | 686 frameworks | 310K+ cross-framework mappings
Control Mappings
Showing 20 of 46 mapped controls across 3 domains. Sign up to explore all 310K+ mappings across 686 frameworks.
Chapter II - Principles(7 mappings)
Chapter III - Rights of the Data Subject(13 mappings)
+26 more mappings
Plus AI-powered gap analysis, compliance advisory, PDF exports, and cross-mapping for all 686 frameworks.
Create Free Account →Free forever, no credit card required
The GDPR to CCPA/CPRA crosswalk
The table above lists candidate mappings. A crosswalk answers the narrower question you are probably here for: which CCPA/CPRA controls your existing GDPR work already satisfies, which are real gaps, and the reasoning behind every claim so you can check it. One pair, $299, one time.
Coverage does not run both ways. GDPR into CCPA/CPRA lands at 56.7%, while CCPA/CPRA into GDPR lands at 32.5%, on the same two control sets. That is not a rounding difference. It is the whole reason these are two separate reports: one asks what your GDPR evidence buys you for CCPA/CPRA, the other asks the reverse.
17 of 30 CCPA/CPRA controls are evidenced by work you have already done for GDPR. 13 are genuine gaps.
A sample of what the report says
Adds the categories of personal data concerned, the element the collection notice needs.
Grounded in GDPR-Art.14 Information where personal data have not been obtained from the data subject. Confidence high, survived the refutation pass.
A business's collection, use, retention and sharing of a consumer's personal information must be reasonably necessary and proportionate to achieve the purposes for which it was collected or processed, or for another disclosed purpose...
Every one of the 17 evidenced controls and 13 gaps in the report carries this much reasoning, so you can check the claim rather than take it on trust.
13 of 40 GDPR controls are evidenced by work you have already done for CCPA/CPRA. 27 are genuine gaps.
A sample of what the report says
Requires categories, purposes, retention and a policy link presented before collection.
Grounded in CCR §7012 Notice at Collection Drafting Requirements. Confidence high, survived the refutation pass.
Process personal data relating to criminal convictions and offences, or related security measures, only under the control of official authority or where Union or Member State law authorises the processing and provides appropriate...
Every one of the 13 evidenced controls and 27 gaps in the report carries this much reasoning, so you can check the claim rather than take it on trust.
- Every evidenced control, with the reasoning behind it
- Every gap, with what it requires
- Its level of review stated plainly, not a bare number
Why this page shows two different percentages. The 62% in the header counts how many GDPR controls carry at least one candidate mapping in the graph, before any review. The crosswalk percentage counts something stricter: how many CCPA/CPRA controls are actually evidenced, after a pass that argued against each mapping and kept only what survived. They answer different questions and they are not meant to agree.
A crosswalk narrows the work. It does not replace an audit, and your assessor may take a different view on individual controls. Mappings between frameworks are judgements, not text printed in either standard, which is why every claim in the report shows its reasoning. Questions go to support@theartofservice.com.
Related Comparisons
Other GDPR comparisons
Other CCPA/CPRA comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 686 frameworks, at a fraction of consulting costs.
Free
- ✓ 686 framework browser
- ✓ Cross-framework mappings (310K+)
- ✓ 824 compliance assessments
- ✓ 3 AI queries & searches per day
Professional
- ✓ Unlimited AI Compliance Advisory
- ✓ Unlimited full-text search
- ✓ Framework self-assessment
- ✓ PDF, Excel & CSV exports
What are the key differences between GDPR and CCPA/CPRA?
GDPR has 40 controls across its framework, while CCPA/CPRA covers 30 controls. Direct mapping analysis identifies 25 overlapping controls (62% coverage). The frameworks diverge most significantly in Chapter IV - Controller and Processor, where 7 GDPR controls have no direct CCPA/CPRA equivalent.
How many controls map between GDPR and CCPA/CPRA?
Of 40 total GDPR controls, 25 map directly to CCPA/CPRA controls, representing 62% coverage. The remaining 15 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.
What are the compliance gaps when mapping GDPR to CCPA/CPRA?
15 GDPR controls have no direct equivalent in CCPA/CPRA. The highest concentration of gaps is in Chapter IV - Controller and Processor with 7 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.
Which control domains have the most gaps between GDPR and CCPA/CPRA?
The domain with the highest gap count is Chapter IV - Controller and Processor (7 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.
Related Resources
This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.