The safest data is the data you never collect

There’s a simple way to never lose a piece of data, never misuse it, and never have to defend it from an attack: don’t collect it at all. It’s the idea behind data minimisation, a principle as elementary as it is countercurrent in an age when the temptation is to gather everything “just in case”.

In short. Data minimisation means collecting only the information necessary for a given purpose, keeping it only as long as it’s useful, and making it accessible only to those who need it. It’s a GDPR principle (Article 5) and, at the same time, one of the most effective security measures: what doesn’t exist can’t be lost, resold or breached.

What it means, in practice

The principle is defined in Article 5(1)(c) of the GDPR: personal data must be “adequate, relevant and limited to what is necessary” in relation to the purposes for which it is processed. Translated into concrete choices, it means asking three questions before every collection:

• Is it really needed? If a piece of information isn’t essential to the function, it shouldn’t be asked for.
• For how long? Data that’s useful today can become a liability tomorrow: retention has an expiry date.
• Who accesses it? The fewer people and systems touch a piece of data, the smaller the attack surface.

It’s a shift in perspective from the habit of accumulation. The question is no longer “what data could we collect?”, but “what data can’t we do without?”.

Why it pays off (for security too)

Minimisation is often seen as a concession to privacy. In reality it is, first of all, good security. Every stored piece of information is a responsibility: it has to be protected, encrypted, monitored and, sooner or later, deleted. Reducing the amount of data directly reduces what can go wrong.

The reasoning is almost tautological, yet often overlooked: data you haven’t collected can’t be stolen in a breach, can’t be misused, and can’t be shared by mistake. Less data means fewer weak points, simpler controls and, for the people using the product, better-placed trust.

There’s a quieter benefit too: less data to store means less storage, less traffic and, ultimately, a lighter footprint in environmental terms as well. Collecting sparingly is consistent with building lean technology that asks for little in order to work well.

Minimising doesn’t mean giving up

A recurring worry is that collecting less means offering less. It doesn’t. Minimisation isn’t about the quality of the experience, but about the amount of personal information needed to deliver it. An application can be rich, useful and complete while asking very little of the person using it.

The key is to design the feature around the bare minimum, not around what would be convenient to have “just in case”. Often, on closer inspection, much of the information collected out of habit is never actually used.

How we put it into practice

In OM Software’s apps, every field in a form has to justify its presence before it is added. If a feature can do without a piece of information, that information is not requested.

The data that’s easiest to protect, manage and respect is always the same: the data that was never collected.

Sources

• GDPR — Article 5: principles of processing — data minimisation, art. 5(1)(c).
• EUR-Lex — Regulation (EU) 2016/679 (GDPR) — official text of the Regulation.
• Wikipedia — Data minimization — definition and context of the principle.