Glossary. Data minimization.
What is data minimization?
Data minimization means holding only the personal data a stated purpose needs. This entry covers the EU and UK, California and India, field by field.
By Dipal Panchal, co-founder and CEO · Updated November 8, 2026
A purpose for every field
Data minimization is the principle of collecting and keeping only the personal data a stated purpose needs, for only as long as it needs it. Unlike data masking, which changes values you keep, minimization decides which values not to hold at all. Our method comes down to one test per field: a field with no purpose you can state gets cut, once legal retention duties, holds and open requests are checked.
The principle applies twice: once at collection, when a form asks for a field, and again over time, when the purpose that justified a field has ended.
One sign-up form, field by field
The fields a newsletter sign-up stores today, each set against the purpose on record and the decision that follows.
| Field | Purpose on record | Needed for it? | Decision |
|---|---|---|---|
| Email address | Send the newsletter | Yes | Keep until the person unsubscribes; then delete in the stated period, keeping a suppression record so it holds |
| Consent timestamp and IP address | Show when and how consent was given | Yes | Keep for as long as the email address is held |
| Full name | Personalize the greeting | Optional | Keep as an optional field, left blank unless the person fills it in |
| Date of birth | Confirm the reader is over 18 | Only the yes or no | Store an “over 18” flag; delete the dates already held |
| Postcode (UK readers) | Regional editions | Only the first half | Keep the outward code, such as SW1A; drop the rest |
| PAN (Indian readers) | None recorded; “might need it for billing” | No: the free newsletter issues no invoice | Stop collecting; delete existing values |
| Phone number | None recorded | No | Stop collecting; delete existing values |
What each law asks, by provision
Each law words the test its own way. The DPDP row is enacted and not yet in force.
| Law | Provision | What it asks |
|---|---|---|
| GDPR and UK GDPR | Art. 5(1)(c) | Personal data adequate, relevant and limited to what is necessary for the purposes |
| GDPR and UK GDPR | Art. 5(1)(e) | Kept in identifiable form no longer than the purposes need (storage limitation) |
| California (CCPA) | Cal. Civ. Code § 1798.100(c) | Collection, use, retention and sharing reasonably necessary, proportionate to its purpose or a compatible disclosed one |
| California (CCPA) | CCPA regulations § 7002(a)–(d) | Purpose must fit the consumer’s reasonable expectations; processing necessary and proportionate, on listed factors |
| India (DPDP Act 2023) | s.6(1) and s.8(7) | Consent limited to data the purpose needs; erasure on withdrawal or purpose end, unless a law requires retention |
Where the tests differ
GDPR asks whether each field is necessary for the purpose. The CCPA asks whether processing is reasonably necessary and proportionate to a purpose that fits the consumer’s reasonable expectations, and its regulations list the factors for judging it. India’s Act ties the limit to consent for a specified purpose, and its section 8(7) adds a duty to erase once that purpose ends.
India’s obligations on Data Fiduciaries commence 18 months after the notification of November 13, 2025, so the DPDP row describes duties that are enacted and not yet in force (checked November 8, 2026).
Copies that lose their purpose
The same email addresses also sit in the CRM, the warehouse, an analytics extract and an old export, and the purpose recorded at sign-up stays in the form’s database.
Consent is recorded once, at collection, in the form or the consent platform. Dipal Panchal, Sylox’s co-founder and CEO, has spent more than 21 years in enterprise data and has talked with many data leaders. He hasn’t seen a company carry the consent ID into the replicas, warehouse loads and CRM copies made from the original. A copy that has lost its purpose fails the test the original passed.
No purpose on record, no field
A field with no recorded purpose stops being collected, and its existing values are deleted. A field needed only as a derived fact, such as “over 18”, is stored as that fact. A copy of a field in another store needs its own purpose on record, or it goes.
Start with the copies: the form holds eight fields, and each copy of them in another store needs its own purpose on record.
Necessity depends on the purpose you wrote
Minimization can’t be judged without a purpose, so a vague purpose such as “business operations” makes every field look necessary. Write purposes narrow enough to say no to a field.
Backups need their own rule. A deleted value can remain in them until they expire, so say how long; California’s regulations let a business defer deletion in backups until they are restored or next used (§ 7022(d)).
IRIS finds where personal data of the types it detects sits in the sources you connect, each with its scan date; your team decides which are copies of a field. Capabilities vary by edition.
Every store that holds the same type of data as a field: IRIS produces part of this, in the sources you connect, for the data types IRIS detects.
A purpose and retention period for each asset: IRIS produces part of this, as your stewards record them in the IRIS catalog, for the assets IRIS discovers.
The decision that a field isn’t needed: Not produced by IRIS.
Deleting the values: Not produced by IRIS.
Explore the data catalogRun the test on one form this week
Pick one form your company runs and list every field it stores. Beside each, write the purpose on record and whether that purpose needs the full value. The test passes when every field has a purpose, a yes or a narrower form, and a retention period.
Purposes belong in the record of processing activities. To compare that record with what your systems actually hold, use the guide on Article 30 records against the data estate.
Official sources
- California Code of Regulations, title 11, § 7002 (restrictions on collection and use), California Privacy Protection Agency. Opened November 7, 2026.
- Digital Personal Data Protection Act 2023, Ministry of Electronics and Information Technology. Opened November 7, 2026.
The records the purpose test needs
What is a record of processing activities?
The step before minimization: the written purpose each field is tested against.
What is a sensitive data inventory?
Where every copy of a field sits, which the minimization test has to reach beyond the form.
What is a DSAR?
The next test of a minimized estate: finding every copy of one person’s data when they ask.
What DPOs ask about minimization
Yes. A test copy or an analytics extract is processing for its own purpose, so each field in it needs that purpose. Masked or synthetic values usually serve testing without the real ones.
No. A schedule handles storage limitation, but a field collected with no purpose fails minimization from the day it is stored.
Not under these laws. Each one ties holding data to a stated purpose, and “just in case” is no purpose.
Protect your brand. Start with your data.
Pick one customer database. We’ll show you where its personal data sits, by table and column, in a read-only scan.