Calendar Icon White
November 13, 2026
Clock Icon
6
 min read

A Quick Guide on CCPA and GDPR Data Minimization Essentials

Learn what GDPR and CCPA data minimization require in 2026, what changed in California and the EU, and how to put it into practice across SaaS and cloud apps.

A Quick Guide on CCPA and GDPR Data Minimization Essentials
ChatGPT
Perplexity
Grok
Google AI
Claude
Summarize and analyze this article with:

TL;DR

  • Both the GDPR and the CCPA, as amended by the CPRA, require you to collect, use and keep only the personal data you need for a stated purpose.
  • California regulators now treat data minimization as an enforcement priority, with fines in the millions in 2026.
  • New CCPA regulations on risk assessments, cybersecurity audits and automated decision-making took effect on January 1, 2026.
  • In the EU, the Digital Omnibus may change parts of the GDPR, but it is still a proposal. Article 5 applies as written today.
  • Consent is not the same thing as minimization. Collecting with consent does not let you collect more than you need.
  • Most excess personal data sits in SaaS apps, tickets, chats and shared files, not in your main database. That is where minimization needs to happen.

‍

Companies collect more personal data than they use. It ends up in support tickets, Slack threads, email attachments, spreadsheets and AI prompts. Every extra record is one more thing to protect, disclose, delete on request and explain to a regulator.

Data minimization is the rule that keeps this in check. This guide covers what the GDPR and the CCPA require, what changed between 2024 and 2026, where companies usually fall short, and how to put minimization into practice across your SaaS and cloud stack.

✨ What data minimization means under each law

__wf_reserved_inherit

GDPR

GDPR data minimization comes from Article 5(1)(c). Personal data must be adequate, relevant and limited to what is necessary for the purposes it is processed for.

Three other parts of the GDPR work alongside it:

  • Purpose limitation, Article 5(1)(b). You collect data for a specific purpose and do not reuse it for something unrelated.
  • Storage limitation, Article 5(1)(e). You keep identifiable data only as long as the purpose needs it.
  • Data protection by design and by default, Article 25. Your systems should collect and expose the minimum by default, not as an afterthought.

Breaking the Article 5 principles falls in the GDPR's higher fine tier: up to 20 million euros or 4% of worldwide annual turnover, whichever is higher.

CCPA and CPRA

The original 2018 CCPA focused on transparency and the right to opt out. The CPRA amendments, in force since 2023, added a direct duty on the business. Under Civil Code section 1798.100(c), collecting, using, retaining and sharing personal information must be reasonably necessary and proportionate to the purpose it was collected for, or to a compatible purpose you disclosed.

The CCPA regulations at section 7002 explain how to judge this. They look at the consumer's reasonable expectations, the type of data involved, the possible harm, and whether a less intrusive option would do the job. The law also requires you to tell consumers how long you keep each category of personal information.

For a deeper look at the California side, see our guide to CPRA data minimization and our CCPA compliance page.

Where the two laws line up

Both laws ask the same practical questions. What do you collect? Why? Who can see it? How long do you keep it? Can you prove all of this? If you can answer those for every system that holds personal data, you are most of the way there for both.

✨ What changed between 2024 and 2026

__wf_reserved_inherit

California made minimization an enforcement priority

In April 2024, the California Privacy Protection Agency (CPPA) issued its first Enforcement Advisory, and it was about data minimization. It used consumer requests as the example. If a consumer asks to opt out of sale or sharing, you should not ask them for more personal information than that request needs.

Enforcement followed. In May 2026, General Motors was fined $12.75 million over connected-vehicle data sales and data minimization violations. Regulators are no longer only checking for a missing opt-out link. They are asking whether you needed the data at all.

Penalties went up

CCPA fines are adjusted for inflation in odd-numbered years. Since January 1, 2025, the CPPA can fine up to $2,663 per violation, or $7,988 for intentional violations and those involving consumers under 16. Each affected consumer can count as a separate violation, so the totals add up fast.

New CCPA regulations took effect on January 1, 2026

The CPPA finalized a package of regulations in September 2025 covering risk assessments, cybersecurity audits and automated decision-making technology. There was no grace period. Risk assessments ask businesses to document what personal information they process and why, which is hard to do without a current data inventory.

The EU proposed changes to the GDPR

The European Commission published the Digital Omnibus on November 19, 2025. It proposes changes to how personal data is defined, rules for AI training, cookie rules and a longer breach notice window. As of late July 2026 it was still awaiting a committee decision in the European Parliament. Until it passes, plan against the GDPR as written, including Article 5(1)(c).

AI tools became a new place for data to leak

Employees now paste customer data into ChatGPT, Claude and other assistants, and agents connect to internal systems through MCP. Personal data sent to a third-party model for a purpose the consumer never heard about is a minimization and purpose-limitation problem under both laws.

Common misconceptions

"If the user consents, we can collect it." Not true under either law. Under the GDPR, consent is one of six lawful bases in Article 6, next to contract, legal obligation, vital interests, public task and legitimate interests. Whatever basis you use, Article 5(1)(c) still limits how much you collect. The CCPA is mostly an opt-out law, and section 1798.100(c) applies whether or not the consumer agreed to anything.

"Minimization is only about collection." It also covers use, sharing and retention. Data you needed last year may be data you should delete this year.

"Our main database is clean, so we are fine." Most excess personal data is unstructured. Think of a credit card number in a Zendesk ticket, a passport scan in Google Drive, or a customer list exported to Google Sheets.

"A privacy policy covers it." A policy says what you intend to do. Regulators look at what your systems actually hold.

Where minimization breaks down in practice

Personal data spreads because people share it to get work done. These are the places it piles up most often:

None of this shows up in a data map built from interviews. You have to scan the systems themselves.

How to put data minimization into practice

  1. Find the data you actually hold. Run sensitive data discovery across SaaS apps, cloud storage and endpoints. A PII scanner that reads PDFs, images and spreadsheets will find far more than a survey of team leads.
  2. Tie each data type to a purpose. For every category, write down why you collect it, which law permits it, and who needs access. If nobody can name a purpose, stop collecting it.
  3. Collect less at the source. Remove optional form fields. Do not ask for a full ID when the last four digits will do. Keep requests to opt out or delete as light as the CPPA advisory asks.
  4. Mask what people do not need to see. Use data masking or tokenization so staff and test systems work with partial or substitute values. Our guide to PCI DSS PAN masking shows how this works for card numbers.
  5. Set retention periods and enforce them. Publish retention periods, as the CCPA requires, and then make systems follow them. Use redaction to remove sensitive values from old tickets, messages and files once their purpose is done.
  6. Control where data goes. Use data lineage to see how data moves between apps, and block it from reaching places it should not, such as personal email or AI tools.
  7. Keep records. Your 2026 risk assessments and any regulator questions will ask for evidence. Keep reports of what you found, what you removed and when.
  8. Review on a schedule. Re-scan regularly. New apps, new fields and new AI tools appear every quarter, and so does new data.

🎥 How Strac helps with CCPA and GDPR data minimization

Strac finds personal data where it actually lives and removes what you do not need.

Discovery and classification. Strac's DSPM scans SaaS apps, cloud storage and endpoints for personal and sensitive data, including GDPR special category data. It reads text inside PDFs, images, Word files and spreadsheets using OCR.

__wf_reserved_inherit

Redaction and deletion. Strac can redact sensitive values inline in tickets, messages and emails, or delete attachments once their purpose is done. This is how retention rules move from a policy document into practice. See how it works in our DLP remediation guide.

__wf_reserved_inherit

Real-time prevention. SaaS DLP, browser DLP, email protection and endpoint DLP stop sensitive data from being shared where it should not go, including ChatGPT, Claude and MCP connections.

__wf_reserved_inherit

No-code integrations. Strac connects to Slack, Gmail, Office 365, Zendesk, Intercom, Salesforce, HubSpot, Google Drive, OneDrive, Box, Jira, Notion, AWS S3 and many more.

__wf_reserved_inherit

Tokenization. Strac's tokenization lets your systems use a stand-in value instead of storing the raw sensitive data on your own servers. Less stored data means less to protect and less to disclose.

Audit-ready reporting. Every finding and remediation is logged, which gives you evidence for CCPA risk assessments and GDPR accountability.

__wf_reserved_inherit

Book a demo to see what personal data is sitting in your SaaS and cloud apps today.

Bottom line

Data minimization is no longer a principle you can cover with a privacy policy. California regulators are fining companies for holding data they did not need, and the GDPR has required it since 2018. The Digital Omnibus may change parts of the GDPR, but minimization still applies today.

The gap for most companies is not the database. It is the personal data spread across support tickets, chat, email, shared drives and AI tools. Find it, tie it to a purpose, remove what you do not need, and keep a record that you did.

Strac does this across your SaaS, cloud and endpoint systems.

🌶️ Spicy FAQs on CCPA and GDPR Minimization Essentials

Is data minimization required under the CCPA?

Yes. Since the CPRA amendments, section 1798.100(c) requires that collecting, using, keeping and sharing personal information be reasonably necessary and proportionate to the disclosed purpose.

What is the GDPR article on data minimization?

Article 5(1)(c). It says personal data must be adequate, relevant and limited to what is necessary. Article 25 adds that systems should do this by default.

Does consent let me collect more data?

No. Consent is one possible legal basis under the GDPR. It does not lift the minimization limit under either law.

Does the Digital Omnibus remove GDPR data minimization?

The Digital Omnibus is still a proposal and has not changed the GDPR. Article 5 applies as written today.

What are the CCPA fines for data minimization violations?

Up to $2,663 per violation, or $7,988 for intentional violations and those involving minors under 16. These amounts apply from January 1, 2025 and are next adjusted in 2027.

How do I minimize data in tools like Slack or Zendesk?

Scan them for personal data, redact or delete what is no longer needed, and block new sensitive data from being shared. Strac does this for Slack, Zendesk and other SaaS apps.

Where can I learn more?

Read our complete guide to data minimization, our GDPR data minimization guide, our CPRA data minimization guide and our data loss prevention guide.

Customer story

“Don’t just alert on problems, fix them.”

Scott Roberts, Chief Information Security Officer, UiPath

  • UiPath
  • Crypto.com
  • Inmar Intelligence
  • thredUP
  • Paymentology
  • Enveda
  • Genesis Molecular AI
  • MeridianLink
More customer stories →
Discover & Protect Data on SaaS, AI, MCP, Endpoints & Cloud
Strac provides end-to-end data loss prevention for all SaaS and Cloud apps. Integrate in under 10 minutes and experience the benefits of live DLP scanning, live redaction, and a fortified SaaS environment.

Customers include

  • UiPath
  • Crypto.com
  • Inmar Intelligence
  • thredUP
  • Paymentology
  • Enveda
  • Genesis Molecular AI
  • MeridianLink
Trusted by enterprises
Data Security + Compliance Automation

Latest articles

Browse all

Get Your Datasheet

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Close Icon