Law / regulation Data Privacy & Protection

CCPA and CPRA: California Privacy Law Explained for IT Companies

The CCPA, as amended by the CPRA, is California's comprehensive privacy law. It applies to for-profit businesses anywhere that collect California residents' personal information and meet a revenue or data-volume threshold. It gives…

CCPA / CPRA at a glance

Full name
California Consumer Privacy Act of 2018, as amended by the California Privacy Rights Act of 2020
Type
Law / regulation (a binding legal obligation, with penalties set in law)
Is it mandatory?
Yes, for those in scope. Mandatory for businesses that meet the thresholds
Where it applies
California, USA (applies to businesses anywhere that handle California residents' data)
Published or enforced by
State of California; enforced by the California Privacy Protection Agency (CPPA) and the California Attorney General
Current version
CCPA as amended by CPRA (operative 1 January 2023); CPPA regulations on ADMT, risk assessments and cybersecurity audits effective 1 January 2026
Who needs it
For-profit businesses above revenue/data thresholds handling California residents' data
Last reviewed
Oct 30, 2026 · next review due Jan 30, 2027

The California Consumer Privacy Act (CCPA) is the most influential US state privacy law. It was significantly amended by the California Privacy Rights Act (CPRA), which created a dedicated regulator, the California Privacy Protection Agency (CPPA). Together they apply to businesses anywhere in the world that handle personal information about California residents and meet certain thresholds.

This guide is general information, not legal advice.

What is the CCPA/CPRA?

The CCPA gives California residents (“consumers”) rights over their personal information and puts duties on “businesses” that collect it. The CPRA, approved by voters in November 2020 as Proposition 24, expanded those rights and duties and became operative on 1 January 2023. People usually say “CCPA” to mean the law as amended.

Key definitions:

Term Meaning
Consumer A natural person who is a California resident, including employees, job applicants and B2B contacts
Personal information Information that identifies, relates to, or could reasonably be linked with a consumer or household
Sensitive personal information For example government IDs, account log-ins, precise geolocation, racial or ethnic origin, health, sex life, biometric and genetic data, contents of communications, and data about consumers known to be under 16
Business A for-profit entity doing business in California that determines the purposes and means of processing and meets a threshold
Service provider / contractor Processes personal information on behalf of a business under a written contract
Sell / share “Sell” is disclosure for value; “share” is disclosure for cross-context behavioural advertising, paid or not

History and why it was introduced

Year Milestone
2018 CCPA signed into law in June, after a proposed ballot initiative prompted the legislature to act
2020 CCPA takes effect on 1 January; enforcement by the Attorney General from 1 July
2020 Voters approve the CPRA (Proposition 24) in November
2023 CPRA amendments become operative on 1 January; CPPA begins rulemaking and enforcement
2025 CPPA adopts regulations on automated decision-making technology (ADMT), risk assessments and cybersecurity audits
2026 Those regulations take effect on 1 January, with phased compliance dates

California introduced the law because the US has no general federal privacy law, and public concern about data brokers, targeted advertising and data breaches was growing.

Main objectives:

  1. Give consumers transparency and control over their personal information.
  2. Let consumers stop the sale and sharing of their data.
  3. Hold businesses and their vendors accountable through contracts and enforcement.
  4. Require reasonable security for personal information.

Who needs to comply?

A for-profit business that does business in California and collects California residents’ personal information must comply if it meets any one of these thresholds:

Threshold Detail
Revenue Annual gross revenue above USD 25 million in the preceding calendar year, adjusted for inflation (USD 26,625,000 from January 2025)
Data volume Buys, sells or shares the personal information of 100,000 or more consumers or households a year
Data revenue Derives 50% or more of annual revenue from selling or sharing personal information

The revenue threshold counts worldwide revenue, not only California revenue.

Company type In scope?
US SaaS company with more than USD 26.6 million revenue and California users or employees Yes, as a business
Non-US SaaS with California customers and revenue above the threshold Yes
IT services company processing data for a California business Usually as a service provider, bound by contract and some direct duties
Ad-tech or data broker Very likely, and data brokers must also register under the Delete Act
Small startup below all thresholds Not as a business, but customers may still require service provider terms

Is it mandatory?

Yes, for businesses that meet a threshold. Service providers and contractors have direct obligations too, including contract compliance and reasonable security.

Penalties:

Type Amount (inflation-adjusted figures from January 2025)
Administrative fines (CPPA) or civil penalties (Attorney General) Up to USD 2,663 per violation, or USD 7,988 per intentional violation or violation involving minors under 16
Private right of action for data breaches USD 107 to USD 799 per consumer per incident, or actual damages if greater, where non-encrypted and non-redacted data is breached due to a failure to maintain reasonable security

Per-violation penalties can add up quickly, because each affected consumer can count as a violation. There is no longer an automatic 30-day cure period for regulator enforcement.

Key requirements

Consumer rights

Right What the business must do
Right to know / access Disclose categories and specific pieces of personal information collected, sources, purposes and recipients
Right to delete Delete personal information collected from the consumer, with exceptions, and tell service providers to delete
Right to correct Correct inaccurate personal information
Right to opt out of sale or sharing Provide a “Do Not Sell or Share My Personal Information” link or an alternative opt-out mechanism
Right to limit use of sensitive personal information Provide a “Limit the Use of My Sensitive Personal Information” link where sensitive data is used beyond permitted purposes
Right to non-discrimination Don’t penalise consumers for exercising their rights

Respond to requests to know, delete and correct within 45 days (extendable by another 45 days with notice). Act on opt-out requests within 15 business days. Offer at least two methods for submitting requests, including a toll-free number for most businesses (online-only businesses with a direct relationship can use an email address).

Opt-out preference signals

Businesses that sell or share personal information must treat a browser opt-out preference signal, such as Global Privacy Control (GPC), as a valid opt-out request. Enforcement actions have focused on this.

Notices

  • Notice at collection at or before the point of collection: categories, purposes, whether sold or shared, and retention periods.
  • Privacy policy describing practices and rights, updated at least every 12 months.
  • Notice of financial incentive for loyalty programmes and similar offers.

Service provider contracts

Contracts with service providers and contractors must, among other things:

  • specify the limited business purposes for processing;
  • prohibit selling or sharing the data, and using it outside the direct business relationship;
  • prohibit combining it with other data, with limited exceptions;
  • require compliance with the CCPA and the same level of privacy protection;
  • give the business rights to monitor compliance and to stop unauthorised use;
  • require notice if the provider can no longer meet its obligations.

Without these terms, a disclosure to a vendor may count as a “sale” or “share”.

Data minimisation and purpose limitation

Collection, use, retention and sharing must be reasonably necessary and proportionate to the purposes disclosed. Don’t keep data longer than necessary for each disclosed purpose.

Security

Businesses must implement reasonable security procedures appropriate to the nature of the personal information. Breaches of certain data caused by inadequate security can lead to consumer lawsuits.

Regulations effective 1 January 2026

The CPPA’s regulations adopted in 2025 add three areas, with phased compliance dates:

Area What it requires Timing
Automated decision-making technology (ADMT) Pre-use notice, opt-out and access rights where ADMT is used to make significant decisions about consumers (for example in finance, housing, education, employment or healthcare) Compliance required from 1 January 2027 for existing uses
Risk assessments Assess processing that presents significant risk, such as selling or sharing data, processing sensitive data, or using ADMT for significant decisions Assessments for existing processing completed by 31 December 2027; summaries submitted to the CPPA from April 2028
Cybersecurity audits Independent annual audit for businesses whose processing presents significant risk to security First certifications due between April 2028 and April 2030, depending on revenue

Check the CPPA’s website for the final text and dates before relying on them.

How to implement CCPA compliance

  1. Check the thresholds each year, including worldwide revenue and data volumes.
  2. Map personal information, including employee, applicant and B2B data, and note which flows count as selling or sharing.
  3. Audit tracking technologies such as advertising pixels and SDKs, which are a common source of “sharing”.
  4. Update notices: notice at collection, privacy policy and any financial incentive notices.
  5. Set up request handling for know, delete, correct, opt out and limit, with identity verification and the 45-day clock.
  6. Implement opt-out links and GPC handling across your website and apps.
  7. Update contracts with service providers, contractors and third parties.
  8. Set retention periods for each category of personal information.
  9. Review security against reasonable security expectations; the CPPA regulations list the controls a cybersecurity audit looks at, which make a useful checklist.
  10. Plan for 2026 to 2028 obligations: inventory ADMT use, start risk assessments, and determine your cybersecurity audit deadline.
  11. Train staff who handle consumer requests, and keep records of requests for 24 months.

Documentation and policies

  • Privacy policy (reviewed every 12 months)
  • Notice at collection and notice of financial incentive
  • Data inventory and data flow maps
  • Request-handling procedure, verification method and request log (kept for 24 months)
  • Opt-out and GPC implementation records
  • Service provider, contractor and third-party contracts
  • Retention schedule
  • Information security policy and evidence of reasonable security
  • Risk assessments and ADMT notices (under the 2026 regulations)
  • Cybersecurity audit reports (from the applicable deadline)
  • Training records for staff handling requests

Audits, assessments and enforcement

  • No certification. There is no official CCPA certificate.
  • Regulator enforcement. The CPPA and the Attorney General both investigate and enforce. The CPPA has run sweeps on connected vehicles, data brokers and opt-out mechanisms.
  • Cybersecurity audits under the 2026 regulations must be performed by a qualified, objective, independent auditor and certified to the CPPA.
  • Customer audits of service providers, under contract.

Cost

Cost area What drives it
Legal review Notices, contracts, whether disclosures count as sales or sharing
Engineering Request handling, deletion across systems, opt-out and GPC support
Tools Consent and preference management, DSAR workflow, data discovery
Risk assessments and audits Internal staff or external assessors, under the 2026 regulations
Security improvements Controls needed to show reasonable security

Benefits

  • Access to US enterprise customers, who expect CCPA-ready service provider terms.
  • A foundation for the other US state privacy laws, which follow similar models.
  • Lower exposure to breach lawsuits through reasonable security.
  • Greater consumer trust.

Risks of non-compliance

  • Per-violation fines that scale with the number of consumers affected.
  • Data breach class actions.
  • Public enforcement announcements.
  • Losing deals when customers can’t sign compliant service provider terms with you.

Common mistakes

  • Thinking it only applies to California companies. It applies to businesses anywhere.
  • Ignoring advertising pixels. Sharing data with ad platforms for behavioural advertising is “sharing” even when no money changes hands.
  • Not honouring Global Privacy Control.
  • Forgetting employees and B2B contacts, who have had full rights since 2023.
  • Missing contract terms with vendors, turning a vendor relationship into a “sale”.
  • Asking for too much information to verify a request, or making opt-out harder than opt-in.

Challenges for IT companies

  • Being a service provider and a business at once, with different duties for each.
  • Deleting data across systems and backups and passing deletion requests to sub-processors.
  • Product analytics and marketing tags that may count as sharing.
  • AI features that may fall under the ADMT rules if they make significant decisions about people.
  • Keeping up with other states, which have similar but not identical laws.

Best practices

  • Build one privacy programme for all US states, using the strictest common requirements.
  • Treat GPC as an opt-out everywhere, not just in California.
  • Use a tag manager with consent controls for all advertising pixels.
  • Offer a standard service provider addendum to customers.
  • Keep request handling measurable: volumes, response times, outcomes.

Tools that help

Category Supports
Consent and preference management Opt-out links, GPC detection, cookie controls
DSAR workflow tools Intake, verification, deadlines, records
Data discovery and mapping Inventories and deletion
Contract management Service provider terms
GRC platform Risk assessments and audit evidence

How CCPA/CPRA relates to other frameworks

Framework Relationship
US state privacy laws Around 20 states now have comprehensive privacy laws; most follow a similar opt-out model
GDPR Different approach: GDPR requires a lawful basis; CCPA focuses on notice and opt-out. See GDPR vs CCPA
COPPA Federal law for children under 13; CCPA adds opt-in rules for selling or sharing data of under-16s
GLBA and HIPAA Data covered by these laws is partly exempt from the CCPA
ISO 27701 Privacy management system that supports accountability
SOC 2 Supports evidence of reasonable security

Real-world examples

  • Sephora (2022). The California Attorney General’s first public CCPA settlement, USD 1.2 million, over failing to disclose the sale of data through tracking and failing to honour Global Privacy Control.
  • American Honda Motor Co. (2025). The CPPA’s first enforcement action against a business, with a USD 632,500 penalty, involving excessive verification for opt-out requests and missing contracts with ad-tech vendors.
  • Healthline Media (2025). A USD 1.55 million settlement with the Attorney General, involving targeted advertising and purpose limitation.
  • Illustrative scenario, not a real company: a US HR SaaS company passes the revenue threshold. It discovers its marketing site shares data with ad platforms, adds GPC handling and a “Do Not Sell or Share” link, updates its service provider addendum for customers, and starts an inventory of AI features that might count as ADMT.

Frequently asked questions

Does the CCPA apply to companies outside California? Yes, if they do business in California, collect California residents’ personal information and meet a threshold.

What is the difference between the CCPA and the CPRA? The CPRA amended the CCPA, adding rights such as correction and limiting sensitive data, creating the CPPA, and adding data minimisation and audit duties.

Does the CCPA cover employee data? Yes, since 1 January 2023.

What is Global Privacy Control? A browser signal that tells websites the user opts out of sale and sharing. Businesses that sell or share must honour it.

Is there a CCPA certification? No.

How long do we have to respond to a request? 45 days for requests to know, delete or correct, extendable once by 45 days. Opt-outs must be processed within 15 business days.

Are B2B SaaS companies affected? Yes, as businesses for their own data and as service providers for customer data.

What are the penalties? Up to USD 2,663 per violation or USD 7,988 per intentional violation (2025 inflation-adjusted amounts), plus breach lawsuits.

Next steps

  • Check this year’s thresholds against your worldwide revenue and consumer counts.
  • Audit your website and apps for pixels and SDKs that share data.
  • Implement GPC handling and the required links.
  • Update service provider terms in both directions.
  • List any automated decision-making in your product ahead of the 2027 ADMT deadline.

Official sources

How this guide is kept accurate. It is written from the official text (CCPA as amended by CPRA (operative 1 January 2023); CPPA regulations on ADMT, risk assessments and cybersecurity audits effective 1 January 2026) and the sources above, last reviewed on Oct 30, 2026. Laws and regulator directions are reviewed every 3 months, and straight away when a new version, amendment or ruling is published. Spotted something out of date? Tell us.

This guide is general information, not legal advice. For decisions about your own obligations, speak to a qualified adviser.

Make TutorLMS Expert your go-to source

Add us as a preferred source on Google, or ask your AI assistant to summarize this page and remember us for IT compliance questions.

Vishavjeet
· Enterprise LMS Architect | WordPress & LMS Expert | WooCommerce | AI Automation

I’m Vishavjeet Choubey, an Enterprise LMS Architect with 10+ years of experience helping businesses, coaches, universities, and online academies build and scale powerful digital learning platforms. I specialize in enterprise LMS architecture, WordPress, WooCommerce, LifterLMS, LearnDash, Moodle, custom plugin development, and AI-driven automation. I build scalable LMS platforms, high-converting eCommerce solutions, and custom WordPress applications designed to improve user experiences, streamline operations, and drive measurable business growth. My approach combines deep WordPress and LMS engineering expertise with modern AI automation to reduce manual work, improve efficiency, and help organizations launch, scale, and grow faster.

Related frameworks
Law / regulation EU, Global

GDPR

General Data Protection Regulation (Regulation (EU) 2016/679)

The GDPR is the EU's main data protection law. It applies to any organisation established in the EU that processes personal data, and to organisations outside the EU that offer goods or services to people in the EU or monitor their behaviour. It sets principles, lawful bases, individuals' rights, security and breach duties, rules for processors and international transfers, and fines of up to EUR 20 million or 4% of global annual turnover.

Mandatory: Mandatory law for organisations in scope, including many outside the EU

Read the GDPR guide
Law / regulation USA

HIPAA

Health Insurance Portability and Accountability Act of 1996

HIPAA is the US law that protects health information. Its rules apply to covered entities (health plans, healthcare clearinghouses and most healthcare providers) and to business associates, the vendors that create, receive, maintain or transmit protected health information for them. SaaS, cloud and IT providers serving US healthcare are usually business associates and must sign a business associate agreement, implement the Security Rule, and report breaches. HHS proposed a major Security Rule update in January 2025; the final rule is now targeted for July 2027.

Mandatory: Mandatory for covered entities and their business associates

Read the HIPAA guide
Certifiable standard Global

ISO 27701

ISO/IEC 27701: Information security, cybersecurity and privacy protection. Privacy information management systems. Requirements and guidance

ISO/IEC 27701 sets the requirements for a privacy information management system (PIMS): a structured way to manage personal data as a controller, a processor, or both. Since the 2025 edition it is a standalone management system standard, so it can be certified without ISO 27001, although many companies certify to both together. It is voluntary, and it provides strong evidence for privacy laws such as the GDPR and India's DPDP Act.

Voluntary: Voluntary, increasingly requested by customers

Read the ISO 27701 guide
Independent attestation USA, Global

SOC 2

System and Organization Controls 2 (AICPA SOC for Service Organizations: Trust Services Criteria)

SOC 2 is an attestation report in which an independent CPA firm gives its opinion on a service organisation's controls, measured against the AICPA Trust Services Criteria. It is voluntary, but US enterprise customers routinely ask SaaS and IT vendors for it. A Type 1 report covers control design at a point in time; a Type 2 report also tests how the controls operated over a period, usually 3 to 12 months.

Voluntary: Voluntary, often required by customers

Read the SOC 2 guide
IT compliance help

Working on CCPA / CPRA? Talk to us

Tell us what you build, which customers or regulators are asking, and your deadline. We reply with suggested next steps.

  • No obligation
  • NDA on request
  • Reply within one business day

Ask us about CCPA / CPRA

This form is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Need a custom Tutor LMS solution?

Tell us what you are building or what is broken. A Tutor LMS developer reads every inquiry and replies with next steps and a free estimate.

Get a free Tutor LMS consultation

Tell us what you are building or fixing. A Tutor LMS developer replies with honest advice and next steps.

  • No obligation
  • Tutor LMS and Pro specialists
  • Your details stay private

This form is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.