Data Minimisation & Privacy by Design ยท Lesson 1 of 4
Safe test data
Study notesAbout 3 minutes. A full lesson with quick checks is on its way.
In short
Test environments are usually less protected than live ones, so fill them with made-up or properly anonymised data, not copies of real people.
In your work
A bug only appears with a client's real booking data. Rather than copy their live database to your laptop, you recreate the pattern with generated records, or ask for an approved, masked extract.
What the UK rules say
- UK GDPR's principles apply in every environment: use only the personal data you need, keep it secure and delete it when you're done.
- A copy of live data in a test system is still personal data, and a leak from it is still a personal data breach.
What to do
- Use generated test data, or a masked extract the data owner has approved.
- Never copy live databases to laptops or personal accounts.
- If real data is unavoidable, get sign-off, limit access and delete it afterwards.
Watch out for
- Seed files and screenshots in the repository that contain real people's details.
- Staging databases still holding last year's live data.
In your organisation
What does your organisation's policy say about live data in test, and who can approve an exception?
Your employer's own policies come first.
Sources
- ICO, Principle (c): Data minimisation (opens in a new tab), checked 6 October 2026.
- ICO, A guide to data security (opens in a new tab), checked 6 October 2026.
UK law and guidance, explained for learning. Not legal advice.
