Law · Privacy · California
CCPA CPRA compliance: rights, the 2026 regulations and audits
CCPA CPRA compliance means meeting the California Consumer Privacy Act as amended by the California Privacy Rights Act, enforced by the CPPA and the Attorney General. New CPPA regulations took effect on 1 January 2026, adding privacy risk assessments, rules for automated decision-making and annual cybersecurity audits from 2028.
What you need to know about CCPA / CPRA
Who must comply with the CCPA?
For-profit businesses doing business in California that meet one of the thresholds.
QULDEX helps here first: the readiness check shows where you stand before you commit budget.
What does the CCPA require?
The CCPA requires covered businesses to give notice at collection, honour rights to know, delete, correct, opt out and limit, keep contracts with service providers, maintain reasonable security and, under the 2026 regulations, assess risk, audit cybersecurity and govern ADMT.
Notice at collection
What, why and how long.
In QULDEX: Notice versionsConsumer rights
Know, delete, correct, opt out, limit.
In QULDEX: Request log with deadlinesSale and sharing opt-outs
Including Global Privacy Control.
In QULDEX: Signal testsRisk assessments and ADMT
Significant-risk processing.
In QULDEX: Assessment workflowCybersecurity audits
From 2028 by revenue.
In QULDEX: Audit workspaceReasonable security
Breach lawsuits if not.
In QULDEX: Security evidenceWhich CCPA sections and rules matter most?
These 15 sections and regulations carry the obligations most businesses work on. Select any one to see what it requires, typical evidence and the matching GDPR or security reference.
Showing up to 6 per group. Search, filter, or open a group to see all 15.
Scope 2
1798.140(d)Who is a businessFor-profit entities doing business in California that meet a revenue threshold (adjusted for inflation), buy, sell or share data of 100,000+ consumers or households, or earn half their revenue from selling or sharing personal information.
In QULDEXThresholds are recorded with the figures used.
- Typical evidence
- Applicability assessment
1798.140(v)Personal and sensitive personal informationPersonal information is broad; sensitive personal information includes government IDs, precise geolocation, health, biometrics and account log-ins.
In QULDEXSensitive data is tagged in the data map.
- Typical evidence
- Data map
Consumer rights 6
1798.100Right to know and notice at collectionTell consumers at or before collection what you collect, why and for how long.
In QULDEXQULDEX gives this obligation an owner, evidence requests and a review date, and maps it to GDPR and ISO 27701.
- Typical evidence
- Notice at collection
- Maps to
- GDPR Art. 13
1798.105Right to deleteDelete personal information on request, with listed exceptions, and tell service providers to delete too.
In QULDEXRequests are logged with 45-day deadlines.
- Typical evidence
- Request log
- Maps to
- GDPR Art. 17
1798.106Right to correctCorrect inaccurate personal information on request.
In QULDEXQULDEX gives this obligation an owner, evidence requests and a review date, and maps it to GDPR and ISO 27701.
- Maps to
- GDPR Art. 16
1798.120Right to opt out of sale or sharingOffer "Do Not Sell or Share My Personal Information" and honour opt-out preference signals such as Global Privacy Control.
In QULDEXOpt-out signals are tested as a control.
- Typical evidence
- Opt-out evidence
1798.121Right to limit sensitive data useLet consumers limit the use of sensitive personal information.
In QULDEXQULDEX gives this obligation an owner, evidence requests and a review date, and maps it to GDPR and ISO 27701.
- Typical evidence
- Limit link evidence
1798.125No discriminationDo not discriminate against consumers for exercising their rights.
In QULDEXQULDEX gives this obligation an owner, evidence requests and a review date, and maps it to GDPR and ISO 27701.
2026 regulations 3
Cyber auditAnnual cybersecurity auditsNew in 2026 regulationsBusinesses whose processing presents significant risk complete independent cybersecurity audits; first certifications are due from 1 April 2028 to 2030, by revenue.
In QULDEXAudit scope and evidence sit in the audit workspace.
- Typical evidence
- Cybersecurity audit report
- Maps to
- ISO 27001SOC 2
Risk assessmentPrivacy risk assessmentsNew in 2026 regulationsAssess processing that presents significant risk, such as selling or sharing data or processing sensitive data; compliance from 1 January 2026, submissions from April 2028.
In QULDEXRisk assessments run with sign-off and submission records.
- Typical evidence
- Risk assessments
- Maps to
- GDPR Art. 35
ADMTAutomated decision-making technologyNew in 2026 regulationsNotice, opt-out and access rights where ADMT is used for significant decisions, from 2027.
In QULDEXQULDEX gives this obligation an owner, evidence requests and a review date, and maps it to GDPR and ISO 27701.
- Typical evidence
- ADMT notices
- Maps to
- EU AI Act
Obligations and enforcement 4
1798.100(d)Contracts with service providers and contractorsContracts must limit use of personal information and require compliance.
In QULDEXEach service provider is linked to its contract terms.
- Typical evidence
- Contracts
- Maps to
- GDPR Art. 28
1798.100(e)Reasonable securityImplement reasonable security procedures and practices appropriate to the data.
In QULDEXSecurity controls are reused from ISO 27001 or SOC 2.
- Typical evidence
- Security evidence
- Maps to
- ISO 27001
1798.150Private right of action for breachesConsumers can sue for data breaches caused by a failure to maintain reasonable security.
In QULDEXQULDEX gives this obligation an owner, evidence requests and a review date, and maps it to GDPR and ISO 27701.
1798.155Administrative finesFines per violation, higher for intentional violations or those involving minors, adjusted for inflation; enforced by the CPPA and the Attorney General.
In QULDEXQULDEX gives this obligation an owner, evidence requests and a review date, and maps it to GDPR and ISO 27701.
Nothing matches that search.
Section numbers follow the California Civil Code; regulation summaries follow the CPPA regulations approved in September 2025. Summaries are QULDEX paraphrases, not legal advice.
How do you comply with the CCPA and the 2026 regulations?
Confirm you are covered, map personal and sensitive data, fix notices and rights handling, then add risk assessments now and prepare for audits and ADMT rules. Most businesses need 3 to 6 months for the core and plan the audit work into 2027.
Confirm the thresholds
Revenue, data volume and selling or sharing share.
Map personal and sensitive data
Sources, purposes, retention, sharing and service providers.
Notices, rights and opt-outs
Notice at collection, request handling and Global Privacy Control.
Risk assessments
Assess significant-risk processing from 1 January 2026.
Prepare the cybersecurity audit
Scope, evidence and an independent auditor before your due date.
Keep it current
2027ADMT rules applyApr 2028First audit certifications and risk assessment submissionsYearlyAudits continue
Dates follow the CPPA regulations approved in September 2025. Durations are QULDEX planning ranges.
Which records does CCPA compliance need?
The CPPA and auditors will ask for these.
| Record | Section | Where it lives in QULDEX |
|---|---|---|
| Applicability assessment | 1798.140(d) | Risk register |
| Data map with sensitive data | 1798.140(v) | Risk register |
| Notice at collection and privacy policy | 1798.100 | Policy library |
| Consumer request log | 1798.105–1798.121 | Evidence vault |
| Opt-out signal test evidence | 1798.120 | Evidence vault |
| Service provider contracts | 1798.100(d) | Vendor register |
| Privacy risk assessments | 2026 regulations | Audit workspace |
| Cybersecurity audit report and certification | 2026 regulations | Audit workspace |
Record names are QULDEX recommendations.
How long does CCPA compliance take and what drives the effort?
The core programme typically takes 3 to 6 months; the cybersecurity audit adds 3 to 6 months of preparation before its due date. Data selling or sharing, sensitive data and ad-tech drive the effort.
Where the time goes
Bars show the upper end of each range on one scale (6 months = full width).
What changes the effort
- Selling or sharing: adds opt-outs and risk assessments
- Ad-tech and cookies: opt-out signals must reach every tag
- Sensitive data: limit rights and assessments
- Revenue band: sets the audit due date
- Existing SOC 2 or ISO 27001: supports the cybersecurity audit
How ready are you for the CCPA?
Check these eight things first. Nothing you enter leaves this page.
How the CCPA maps to GDPR, ISO 27701 and SOC 2
The CCPA is opt-out based where GDPR is consent based, but rights handling, risk assessments and security evidence overlap heavily.
CCPA vs GDPR at a glance
| CCPA / CPRA | GDPR | |
|---|---|---|
| Model | Notice and opt-out (opt-in for minors) | Lawful basis, often consent |
| Scope | Businesses meeting thresholds | Any controller or processor in scope |
| Assessments | Risk assessments under 2026 regulations | DPIAs for high risk |
| Security audits | Independent cybersecurity audits from 2028 | No audit mandate |
| Enforcement | CPPA, Attorney General, private action for breaches | Supervisory authorities |
| In QULDEX | QULDEX maps each process to both laws, so one privacy programme serves California and the EU. | |
Privacy crosswalk
| CCPA / CPRA | GDPR | ISO 27701:2025 | SOC 2 | Shared evidence |
|---|---|---|---|---|
| 1798.100 Notice | Art. 13–14 | Notices | P1 | Notices |
| 1798.105 Delete | Art. 17 | Erasure | P4 | Request log |
| 1798.120 Opt-out | Art. 21 | Objection | P2 | Opt-out evidence |
| 1798.100(d) Contracts | Art. 28 | Processor contracts | CC9.2 | Contracts |
| Reasonable security | Art. 32 | Security for PII | CC6–CC8 | Security evidence |
| Risk assessments | Art. 35 | Impact assessment | CC3.2 | Assessments |
| Cybersecurity audit | — | — | SOC 2 report | Audit report |
Indicative mapping for planning, not legal advice.
How QULDEX runs CCPA compliance from data map to cybersecurity audit
QULDEX is CCPA compliance and audit management software built from EGV Group's audit delivery, used by businesses, their privacy teams and the independent cybersecurity auditors the 2026 regulations require. Pick your role to see who does what.
For businesses meeting the CCPA thresholds.
- ScopeConfirm thresholdsApplicability record
- MapMap dataData map with sensitive data
- RightsAnswer requestsRequest log with deadlines
- AssessRun risk assessmentsAssessment workflow
- SecurityProve reasonable securityControls mapped to ISO 27001 and SOC 2
- CertifyCertify the auditCertification pack
For privacy consultants and internal audit.
- ScopeRun the gap assessmentA reusable CCPA gap template
- MapReviewComments per system
- RightsOverseeDashboards
- AssessReviewSign-off
- SecurityReview evidenceReview states
- CertifyPrepareReadiness check
For independent auditors under the 2026 regulations.
- ScopePlanScope in a standard format
- MapReviewView-only access
- RightsSampleRequest history
- AssessReviewAssessment records
- SecurityAuditView-only evidence with download control and an access log
- CertifyReportFindings into CAPA
Pre-mapped control library
Requirements with owners, test steps and the crosswalk to 50+ frameworks.
Explore →EvidenceSecure evidence vault
Evidence linked to controls and findings, with upload, review and approval history.
Explore →RiskRisk register
Risk assessment and treatment, with decisions traced to the controls they drive.
Explore →FindingsCAPA remediation
Findings from internal and external audits tracked to closure with due dates.
Explore →CCPA / CPRA questions people ask
Who must comply with the CCPA?
For-profit businesses doing business in California that exceed the inflation-adjusted revenue threshold, buy, sell or share personal information of 100,000 or more consumers or households, or earn at least half their revenue from selling or sharing personal information.
What did the 2025 CCPA regulations add?
Regulations approved in September 2025 and effective 1 January 2026 add privacy risk assessments, rules for automated decision-making technology (from 2027) and annual cybersecurity audits (certifications from 2028).
When are CCPA cybersecurity audits due?
Certifications are due by 1 April 2028 for businesses with over $100 million in revenue, 1 April 2029 for $50–100 million, and 1 April 2030 for those under $50 million.
What are the CCPA penalties?
Administrative fines per violation, higher for intentional violations or those involving minors, adjusted for inflation each year, plus statutory damages in consumer lawsuits after certain data breaches.
What rights do California consumers have?
To know, delete and correct their personal information, to opt out of its sale or sharing, to limit the use of sensitive personal information, and not to be discriminated against for using these rights.
Go deeper on CCPA / CPRA
Data privacy topic hub
GDPR, ISO 27701 and privacy-law comparisons.
blog.quldex.comAudit evidence naming convention
A file-naming scheme auditors can follow.
blog.quldex.comAudit sampling size for compliance
How many samples auditors look at.
blog.quldex.comSOC 2 bridge letter
Security reports that support a cybersecurity audit.
References
- California Civil Code 1798.100 et seq. (CCPA as amended by CPRA). leginfo.legislature.ca.gov
- CPPA regulations on cybersecurity audits, risk assessments and ADMT, approved 23 Sep 2025. cppa.ca.gov
- California Attorney General CCPA page. oag.ca.gov
- Skadden, California finalizes CPPA regulations, Oct 2025. skadden.com
Reviewed by
Page history
- : Page first built: section explorer with the 2026 regulations, audit timeline and readiness check
Plan your CCPA cybersecurity audit now
Answer a short readiness check and get a gap summary by area. No sales call needed to see the result.