Plain-language guides to business cybersecurity and risk assessment

Data Minimization: Collecting Less to Risk Less

data minimization

Worried about how much customer and staff data your business is sitting on? Data minimization means holding only the personal data you need for a clear purpose, and no more. Start by asking why you keep each item.

This guide is one part of business data privacy, and it focuses on collecting less in the first place.

Item Value
Where the rule sits Article 5(1)(c) of the UK GDPR
What personal data must be Adequate, relevant and limited to what is necessary
Place among the data protection principles One of seven key principles
Principles about data standards Three: data minimisation, accuracy and storage limitation
Highest-tier fine for breaching the principles Up to £17.5 million or 4% of total worldwide annual turnover, whichever is higher

These figures come from the ICO’s data minimisation guidance and its guide to the data protection principles, as of the ICO’s 23 March 2026 update to that guide. Figures can change, so check the source before you rely on them.

What does data minimization mean for your business?

Data minimization means you identify the minimum amount of personal data you need for a purpose, and you hold that much but no more. In the UK GDPR it sits in Article 5(1)(c), which says personal data must be adequate, relevant and limited to what is necessary for the purposes it is processed for.

The principle covers both collecting and keeping. It is the first of three principles about data standards, along with accuracy and storage limitation, so deleting data you no longer need is part of the same habit, as the ICO’s guidance explains.

The ICO’s pages say that, because of changes made by the Data (Use and Access) Act, this guidance is under review and may change. Check the ICO’s latest pages before you build a policy on them.

The tests: adequate, relevant and limited

The ICO breaks the principle into a short checklist you can apply to any form, database or spreadsheet:

  • Adequate: sufficient to properly fulfil your stated purpose.
  • Relevant: it has a rational link to that purpose.
  • Limited: you do not hold more than you need for that purpose.

The UK GDPR does not define these terms, so everything starts with being clear about your purpose. What counts as enough can also differ from one person to another.

For special category data or criminal offence data, the ICO says it is particularly important to collect and keep only the minimum amount of information.

What collecting too much looks like

The ICO uses everyday examples to show where excess data creeps in. Each one is a question you can ask about your own processes:

  • A debt collection agency searching for one debtor gathered details of several people with a similar name. Once some were ruled out, it should have deleted most of their data, keeping only a basic record so they are not contacted again about debts that are not theirs.
  • A recruitment agency sent every applicant a questionnaire with health questions relevant only to certain manual jobs. Asking them of someone applying for an office job would be irrelevant and excessive.
  • An employer holds blood groups for staff doing hazardous work in case of accident, which can be justified. Holding them for the rest of the workforce is likely to be irrelevant and excessive.

The pattern is simple: collect sensitive details only from the people who need them, and only for the reason you can state.

data minimization Optical discs
Three optical discs lie in a row against a pale blue background.

The ICO is blunt about one habit: you must not collect personal data on the off-chance that it might be useful in the future. You may hold data for a foreseeable event that may never happen, as in the blood group case, but only if you can justify it.

When too little data is also a problem

Minimization does not mean collecting as little as possible. If your data is inadequate for the purpose, you may make decisions on an incomplete picture of the facts.

The ICO gives the example of a small club that starts with names and email addresses. When membership grows quickly, it needs more details to identify members and track subscription payments, so collecting more becomes necessary.

Records of opinions need care too. To be adequate, your records should make clear that something is opinion rather than fact.

How to put data minimization into practice

You do not need special software to start. These steps draw on the ICO’s guidance and its audit toolkits:

  1. State the purpose for each type of data before you collect it, and write it down.
  2. Map how data flows into, around and out of your service. The ICO’s age-appropriate design toolkit recommends data flow maps for this.
  3. Trim your forms. The ICO’s AI toolkit suggests asking whether you need a whole address or whether just the postcode would produce the same result, and consider cropping or redacting documents when collecting and sharing them.
  4. Avoid bundling in extra data on top of what you need to deliver your core service.
  5. Set a retention schedule. Classify personal information by sensitivity and set a retention period for each category.
  6. Review what you hold on a regular basis and delete anything you no longer need.
  7. Where people or systems do not need to see identities, consider data masking or anonymisation.

Staff data raises its own questions, so read about employee monitoring privacy laws before you add more tracking. If your team is small, data privacy compliance for small business sets these habits in a wider context.

Why it matters: fines, rights and accountability

Breaching the principles can be expensive. Under Article 83(5)(a), infringements of the basic principles are subject to the highest tier of administrative fines, which could mean up to £17.5 million or 4% of total worldwide annual turnover, whichever is higher, according to the ICO’s principles guide.

Holding more than you need is also likely to be unlawful, because most lawful bases have a necessity element. Individuals can also ask you to delete data that is not necessary for your purpose under the right to erasure.

Finally, the accountability principle means you must be able to demonstrate that you have processes to collect and hold only the data you need. A written purpose, a retention schedule and a review log are the kind of evidence that helps.

Frequently asked questions

Is data minimization the same as deleting old data?

Show answer

Not quite. Data minimization is about holding data that is adequate, relevant and limited, while storage limitation is about how long you keep it. The ICO says the two are closely linked, so a regular review should cover both.

Can I collect data now in case it is useful later?

Show answer

The ICO says you must not collect personal data on the off-chance that it might be useful in the future. You may hold data for a foreseeable event that may never occur, but only if you can justify it.

Does it mean I should collect as little data as possible?

Show answer

No. You need enough data to properly fulfil your purpose, and the ICO warns that inadequate data can lead to decisions based on an incomplete understanding of the facts. The aim is the right amount, not the smallest amount.

Can people ask me to delete data I do not need?

Show answer

Yes. Under the right to erasure, individuals can ask you to delete data that is not necessary for your purpose, as the ICO’s guidance states. They can also ask you to complete data that is incomplete for your purpose.