Storage limitation
The GDPR Article 5(1)(e) principle requiring personal data to be kept in identifiable form for no longer than necessary for the purpose it was processed for. Violating it sits in GDPR's highest penalty tier (up to EUR 20 million or 4 percent of global turnover).
Defined in 3 GAGE programs, which carry 3 distinct definitions of it. The wording above is taught in Certified AI Data Governance Professional (CADGP).
How each discipline defines it
The same term does different work depending on who is using it. These are the definitions as each program teaches them, unedited.
The GDPR Article 5(1)(e) principle requiring personal data to be kept in identifiable form for no longer than necessary for the purpose it was processed for. Violating it sits in GDPR's highest penalty tier (up to EUR 20 million or 4 percent of global turnover).
The principle that personal data must be kept in identifiable form no longer than necessary for the purpose it was collected for. Codified in GDPR Article 5(1)(e), Kenya's Data Protection Act, 2019 Section 39, and equivalents worldwide.
The requirement that personal data be kept in identifiable form no longer than necessary for the purposes. Article 5(1)(e). Distinct from minimisation, and the principle organizations most often fail while satisfying the other.
Where it is taught
The exact lessons this term appears in. The first module of every program is free with a free account.
- The "we have always had this data" trap: age does not launder a dataset · Consent, Purpose, and the Law of Data, Certified AI Data Governance Professional (CADGP)
- The retention decision: what you must keep, what you must destroy, and proving both · Data Reality, Certified AI Governance Professional (CAIGP)
- Privacy principles in operation · Privacy and Data Governance, Certified Enterprise Governance, Risk and Compliance Professional (CEGP)
Where it shows up at work
A definition is where Storage limitation starts. The lessons above teach it inside the competencies below, which are what job descriptions ask for and what the GAGE credential records. Every link here is drawn from the same careers map that builds a role's readiness check.
Builds minimization, purpose limitation, de-identification, consent and retention into an AI system before launch, with tests that prove it.
One lesson on this page teach it as a primary outcome.
Classifies information, applies least privilege, sets retention and acceptable-use rules, and controls what may enter a prompt, a log or an embedding.
One lesson on this page teach it as a primary outcome.
Roles that hire for it
Each role page shows the full competency set, what the seat decides, and a readiness check against your own evidence.
- AI Privacy Engineerneeds it at depth · 6 open postings this week
- Chief Privacy Officer, AI privacy editionneeds it at depth
- Privacy Analystneeds working knowledge
- Data Governance Leadneeds it at depth · 2 open postings this week
- Chief Data Officer, data leadership editionneeds working knowledge
- Chief Information Officer, technology leadership editionneeds working knowledge
How job descriptions say it
Postings rarely use the textbook word. These are the phrases the careers map reads as asking for the competencies above.
Where the frameworks place it: ISO/IEC 27701; GDPR Article 25; ISO/IEC 27001; GDPR Article 5.
One interview question about it
How do you build privacy into an AI product from the design stage rather than checking it at the end?
Asked of candidates for privacy by design and privacy engineering. Answering it in your own words is exactly how a GAGE topic is passed, and the credential records the pass where an employer can check it.
If you come from another field
Some backgrounds already carry this competency, and the readiness check gives credit for it.
- Privacy and data protection carries it as a claim to back up: Classification and retention rules are familiar territory.
- Cybersecurity and IT carries it as work you can show: Access governance and classification are implemented, not described.
- Human resources and people operations carries it as a claim to back up: Access restriction and retention for personnel data are routine.
Terms it appears with
Not an alphabetical neighbourhood: these are the terms taught in the same lessons, ranked by how often they appear together.