If your business collects personal data, treat GDPR as the stricter rulebook and CCPA as the California consumer rights playbook. Build your privacy program for GDPR first. Then add CCPA duties for California users. This keeps the mess smaller.
TLDR: GDPR applies to people in the EU and UK, while CCPA applies mainly to California residents. GDPR asks, “Do you have a legal reason to use this data?” CCPA asks, “Can the person see, delete, or stop the sale or sharing of their data?” For example, if a store has 50,000 customers and 30% are from Europe while 20% are from California, it likely needs both rules covered.
GDPR vs CCPA: The Simple Version
Table of Contents
Think of GDPR as a strict school principal. It wants permission slips, records, reasons, and tidy folders.
Think of CCPA, updated by the CPRA, as a consumer bouncer. It says, “Show people what you know about them. Let them say no. Do not be sneaky.”
Both laws protect privacy. Both give people rights. Both can bite your budget if ignored.
But they work in different ways.
Who Must Follow GDPR?
GDPR stands for the General Data Protection Regulation. It protects people in the European Union. The UK has its own very similar version, often called UK GDPR.
You may need to follow GDPR if you:
- Sell goods or services to people in the EU or UK.
- Track EU or UK visitors with cookies or ads.
- Store personal data about EU or UK users.
- Use vendors that process EU or UK personal data.
You do not need an office in Paris or Berlin. If you target EU users, GDPR can still apply. Yes, that feels unfair. Privacy law did not come here to be chill.
Who Must Follow CCPA?
CCPA stands for the California Consumer Privacy Act. It protects California residents. It was expanded by the CPRA, so many people now use both names together.
CCPA usually applies to a for-profit business that does business in California and meets at least one of these points:
- Has annual gross revenue over $25 million.
- Buys, sells, or shares personal data of 100,000 or more California consumers or households.
- Makes 50% or more of annual revenue from selling or sharing personal data.
So, a tiny blog may not qualify. A growing ecommerce brand might. An ad tech company almost certainly should pay attention.
The Biggest Difference: Legal Basis vs Consumer Control
GDPR starts with one big question:
“What is your legal basis for using this data?”
You need a lawful reason before processing personal data. Common GDPR legal bases include:
- Consent: The person clearly said yes.
- Contract: You need data to provide a service.
- Legal obligation: A law requires it.
- Legitimate interests: You have a fair business reason, and it does not harm the person’s rights.
CCPA starts from a different place. It often lets businesses collect data, but gives consumers strong rights after that.
CCPA asks:
- Can the person know what data you collect?
- Can they delete it?
- Can they correct it?
- Can they opt out of sale or sharing?
- Can they limit use of sensitive personal information?
So GDPR is more about permission and purpose. CCPA is more about notice and control.
What Counts as Personal Data?
Under GDPR, personal data is very broad. If it can identify a person, directly or indirectly, it counts.
Examples include:
- Name
- Email address
- Phone number
- IP address
- Cookie IDs
- Location data
- Device identifiers
CCPA uses the term personal information. It is also broad. It includes names, emails, browsing history, purchase records, geolocation, and inferences about a person.
That last one is spicy. If your system guesses that someone likes luxury watches, hiking trips, or discount cat food, that guess may count.
Consent Rules: Not the Same Party
GDPR loves consent rules. Consent must be clear, specific, informed, and easy to withdraw.
No pre-checked boxes. No “by breathing near this website you agree” nonsense.
CCPA does not always require opt-in consent for regular data collection. But it does require clear notice. It also gives users the right to opt out of selling or sharing personal information.
For minors, rules get tighter. Under CCPA, businesses need opt-in consent before selling or sharing data for consumers under 16. If the child is under 13, a parent or guardian must approve.
Privacy Notices: Your Plain English Moment
Both laws want transparency. That means your privacy notice should not read like a cursed spell from a legal wizard.
A good privacy notice explains:
- What data you collect.
- Why you collect it.
- Who you share it with.
- How long you keep it.
- What rights users have.
- How users can contact you.
For CCPA, you also need to explain categories of data collected and whether data is sold or shared. If you sell or share data, you may need a clear link like “Do Not Sell or Share My Personal Information.”
Honestly, it feels like some privacy tools hide that setting in a basement. I have seen teams need 9 clicks just to update a cookie category. That is silly. Choose tools your team can actually use.
User Rights Under GDPR
GDPR gives people several rights. These include:
- Access: See what data you have.
- Correction: Fix wrong data.
- Deletion: Ask you to erase data.
- Restriction: Pause certain processing.
- Portability: Get data in a usable format.
- Objection: Object to certain uses.
You usually have one month to respond. Some complex requests can take longer, but you need to communicate that.
User Rights Under CCPA
CCPA gives California residents rights too. These include:
- The right to know what data is collected.
- The right to request deletion.
- The right to correct inaccurate data.
- The right to opt out of sale or sharing.
- The right to limit use of sensitive personal information.
- The right not to face unfair treatment for using privacy rights.
Businesses often have 45 days to respond to consumer requests. This can be extended in some cases.
Fines: The Not Fun Part
GDPR fines can be huge. The top level can reach €20 million or 4% of global annual revenue, whichever is higher.
CCPA penalties are smaller per violation, but still painful. Civil penalties can reach $2,500 per violation or $7,500 per intentional violation. Data breaches can also bring private lawsuits, with statutory damages often ranging from $100 to $750 per consumer per incident.
Now multiply that by 80,000 users. See? Not cute.
A Simple Compliance Checklist
Want a sane starting point? Use this checklist.
- Map your data. Know what you collect and where it goes.
- Update your privacy notice. Keep it clear and current.
- Set your legal bases. This matters most for GDPR.
- Add consent controls. Especially for cookies and marketing.
- Create request forms. Let users access, delete, and correct data.
- Add opt-out links. This matters for CCPA sale and sharing rules.
- Review vendor contracts. Your vendors can create risk.
- Train your team. Support staff should know what a privacy request looks like.
- Keep records. Regulators like proof.
Quick Example: One Store, Two Laws
Meet PixelSocks, a fake online sock shop. It sells neon socks to the US and Europe. It has 120,000 customers. About 25,000 are in California. About 18,000 are in the EU.
PixelSocks uses email marketing, analytics cookies, and retargeting ads.
For GDPR, PixelSocks needs a lawful basis for each data use. It may need cookie consent before analytics or ad tracking. It must also handle EU access and deletion requests.
For CCPA, PixelSocks must tell California users what data it collects. If ad sharing qualifies as “sharing,” it needs an opt-out link. It must also process deletion, correction, and access requests.
Same socks. Different rules. Mild headache.
Which Law Is Stricter?
In many cases, GDPR is stricter. It has tighter upfront rules. It cares deeply about purpose, legal basis, consent, and data minimization.
CCPA is still serious. It focuses more on consumer rights, disclosure, and opt-outs. California users get real power over their information.
The smart move is simple. Build your program to meet GDPR standards where possible. Then add CCPA-specific items, such as California notices and opt-out links.
Final Takeaway
GDPR and CCPA are cousins, not twins. GDPR asks you to justify data use before you act. CCPA asks you to be clear and give California consumers control.
Do not wait for a complaint to clean up your privacy process. Map the data. Fix the notice. Add the rights workflow. Your future self will be less annoyed.