Data Minimisation & Privacy by Design ยท Lesson 3 of 4

No data 'just in case'

Study notesAbout 3 minutes. A full lesson with quick checks is on its way.

In short

'Might be handy one day' isn't a purpose. Under UK GDPR you need a specific, legitimate reason before collecting personal data.

In your work

A product owner asks you to add date of birth to a charity's donation form 'for future campaigns'. There's no age-related purpose today, so you question it and leave it out until there is.

What the UK rules say

  • UK GDPR's purpose limitation principle: collect personal data only for specified, explicit and legitimate purposes.
  • People must be told why their data is being collected, in privacy information given at the time it's collected.
  • Data can only be reused for a new purpose if that's compatible with the original one, or there's consent or a clear legal basis.

What to do

  1. Ask what the data is for, who will use it and when it will be deleted.
  2. Raise it with the product owner and data protection lead if there's no answer.
  3. Record the agreed purpose with the field, for example in the data model.

Watch out for

  • Agreeing to 'just add a column' because it's quick.
  • Reusing data collected for support, such as emails, for marketing.

In your organisation

Who approves new personal data fields in your organisation's products?

Your employer's own policies come first.

Sources

UK law and guidance, explained for learning. Not legal advice.