Attributes minimisation

What the clause says

The system should process only the attributes it needs for the age decision. Extra identity data is a privacy cost with no assurance benefit.

What it supplies to a comparison

Minimisation is measurable: list the fields captured, the fields used and the fields retained. The gap between them is the finding.

Evidence to keep

• The field inventory from capture to deletion.
• The justification for each field that is retained.

What the evidence looks like

For 7.1.5, the first artefact is The field inventory from capture to deletion.. The second is The justification for each field that is retained.. If 7.1.5 has no first artefact, the practice is unproven at 7.1.5, and the report should record the absence rather than infer the practice from a policy.

Questions for the provider

1. Which captured fields play no part in the age decision?
2. Can the system deliver the same result with fewer fields?

How it connects to the draft

Attributes minimisation belongs to 7 privacy objectives, and it gives the analysis one fixed point: Minimisation is measurable: list the fields captured, the fields used and the fields retained. The gap between them is the finding. A comparison that cannot place a result against 7.1.5 is measuring something the framework has not defined, and the report should say so.

In the register, 7.1.5 is read beside the unit that tests it, and where it sets an objective rather than a number, that unit turns the objective into a question and an evidence artefact.