Responsible AI
Data Minimization, Purpose Limitation, Consent, and Retention
Apply necessity, proportionality, purpose limitation, lawful basis, retention, deletion, and access controls to AI data.
By the end you can
- Explain why data governance ties each collection and use to a specific purpose, necessity test, lawful basis, access rule, retention period, and deletion process
- Distinguish Consent, Legitimate or public interest, and Contract or legal obligation
- Identify evidence that connects purpose to deletion and downstream effect
- Design a review that moves from separate purposes to verify lifecycle behavior
Visual
Where data minimization and purpose governance enters the lifecycle
Purpose, necessity, lawful basis, retention, deletion: each row constrains the one below it, and the last one reaches into models and backups.
That last row is not a metaphor, and it is not aspirational. In January 2021 the Federal Trade Commission settled with Everalbum, and the order did not stop at the photos. It required deletion of the users' photos and videos. It required deletion of the face embeddings created without affirmative express consent. And it required deletion of the models and algorithms developed in whole or in part from those users' images. European regulators have since said the same. EDPB Opinion 28/2024, adopted 17 December 2024, states that AI models trained on personal data cannot, in all cases, be considered anonymous. Where development rested on unlawfully processed personal data, the corrective measures available run as far as erasure of the whole training dataset and of the AI model itself.
Read the five rows downward and the fifth is not a disposal step at the end. It is the row that decides whether the four above it were ever real.
- 1
Purpose
The specific outcome and processing activity being justified.
- 2
Necessity
Why each data element and level of detail is required.
- 3
Lawful basis and expectation
The legal and relational basis for processing and user understanding.
- 4
Retention and access
Who can use the data, for how long, and under which controls.
- 5
Deletion and downstream effect
How copies, derived artifacts, models, and backups are handled.
Example
Recordings kept by default, and a deletion request that never reached the transcripts
On 31 May 2023 the FTC and DOJ charged Amazon over the children's voice recordings collected through Alexa. The complaint alleged three things. Amazon retained those recordings indefinitely by default. It used the unlawfully retained recordings to improve the Alexa algorithm. And when a parent requested deletion, it failed to delete the transcripts of what children said from all of its databases.
The FTC's Bureau of Consumer Protection director, Samuel Levine, put it in one line: “COPPA does not allow companies to keep children’s data forever for any reason, and certainly not to train their algorithms.”
The stipulated order was entered on 19 July 2023, in the Western District of Washington. It imposed a $25 million civil penalty. It required deletion of voice and geolocation information on request. It required Amazon to identify and delete inactive child profiles — profiles not used for 18 months — unless a parent asks that they be kept. And it prohibited use of that data for the creation or improvement of any data product.
Nothing in that sequence needed a villain. It needed a default, a purpose written wide enough to absorb the default, and a deletion routine that ran in one system while the data sat in several.
- Broad purpose: Improvement was elastic enough that the order had to close it by name, prohibiting use of the data for the creation or improvement of any data product. A purpose that has to be banned in those words was never a boundary.
- Excess collection: What accumulated was not one field. The order made both voice information and geolocation information deletable on request. That is the measure of what a voice assistant had been keeping about children.
- Purpose expansion: Recordings the company was not entitled to retain were used to improve the Alexa algorithm, the complaint alleged. The retained corpus became a training corpus, without any decision that looked like a decision to make it one.
- Retention default: Recordings were retained indefinitely by default. The order had to supply the trigger the company had not: child profiles unused for 18 months are identified and deleted, unless a parent asks that they be kept.
- Power asymmetry: A parent could ask for deletion and still not get it. On the complaint's allegation, the transcripts of what children said survived in databases the request never reached. That gap between the request and the copies is what the $25 million civil penalty was priced against.
Comparison
Consent, Legitimate or public interest, or Contract or legal obligation?
Consent rests on a person agreeing. Legitimate interest rests on whoever holds the data doing the balancing. Contractual necessity rests on the duty actually existing.
The third of those has been tested to a figure. On 4 January 2023 Ireland's Data Protection Commission fined Meta Platforms Ireland €210 million over Facebook and €180 million over Instagram, and directed compliance within three months. The decisions had been adopted on 31 December 2022. The finding is in the regulator's own press release: “the DPC’s decisions include findings that Meta Ireland is not entitled to rely on the “contract” legal basis in connection with the delivery of behavioural advertising as part of its Facebook and Instagram services, and that its processing of users’ data to date, in purported reliance on the “contract” legal basis, amounts to a contravention of Article 6 of the GDPR.”
The DPC had not reached that conclusion on its own. Ten of the 47 concerned supervisory authorities objected to its draft decisions, one objection later withdrawn in the Facebook case. On 5 December 2022 the European Data Protection Board overruled the DPC's view. Performance of a contract, under Article 6(1)(b) GDPR, could not carry behavioural advertising. Scope follows the duty or service. A contract users had genuinely accepted did not stretch to cover what was built on top of it.
The second column has a published test rather than a disposition. EDPB Opinion 28/2024, which the Irish regulator itself asked for, sets out three steps: identify the interest, test necessity, then balance. The interest has to be lawful, clearly and precisely articulated, and real and present rather than speculative. On the middle step: “With respect to the second step, the Opinion recalls that the assessment of necessity entails considering: (1) whether the processing activity will allow for the pursuit of the legitimate interest; and (2) whether there is no less intrusive way of pursuing this interest.” Necessity is not usefulness. It asks whether a less intrusive route exists, with the amount of personal data processed weighed in light of the data minimisation principle.
Consent
Relies on a person’s valid agreement.
- Must be specific and informed
- Can be inappropriate under dependency or imbalance
- Requires withdrawal and records
- Not the only lawful basis in many regimes
Legitimate or public interest
Relies on a justified purpose and balancing.
- Requires necessity and rights assessment
- Does not permit unlimited reuse
- Needs safeguards and transparency
- Varies by jurisdiction and context
Contract or legal obligation
Supports processing necessary for defined duties.
- Scope follows the duty or service
- Cannot justify unrelated improvement by default
- Needs data minimization
- Does not remove transparency and security duties
Key idea
A notice cannot make collection necessary
A privacy notice cannot convert unnecessary collection into necessity. Transparency is essential, but disclosure alone does not make an intrusive or incompatible practice responsible.
A court has said as much about the screen itself. On 19 June 2020 France's Conseil d'État rejected Google's challenge to a €50,000,000 CNIL fine and held the amount was not disproportionate. Consent gathered through a pre-ticked box is not a clear affirmative action, it ruled. Consent is valid only if preceded by a clear and distinct presentation of all the intended purposes of the processing. Then the line that matters most here: “En outre, un consentement recueilli dans le cadre de l'acceptation globale de conditions générales d'utilisation d'un service ne revêt pas un caractère spécifique au sens du RGPD.” In CNIL's own English: “Moreover, consent collected in the context of overall acceptance of a service's general conditions of use does not have a specific character within the meaning of the GDPR.” The purposes were disclosed. Being disclosed inside a global acceptance was the defect, not the defence.
The pressure runs the other way too. Removing data can make it harder to audit discrimination, investigate incidents, or honor legal retention duties. Minimization should be purpose-specific, and it should still preserve the evidence that is justified, behind controlled access. Amazon kept children's voice recordings indefinitely by default and, on the complaint's allegation, used the unlawfully retained ones to improve the Alexa algorithm. No wording of that default in a notice would have made the retention necessary. The order that followed did not ask for better wording. It asked for deletion, a trigger at 18 months, and a ban on using the data to improve any data product.
A notice tells people what is being collected; it does not shrink what was collected, and a corpus that exists is one the next department will ask for.
Six purposes, separated before they bundle
Data minimization means collecting and retaining data that are adequate, relevant, and necessary for a defined purpose. Purpose limitation constrains incompatible reuse. Consent, when used, must be informed, specific, freely given, and withdrawable, not a blanket permission for future AI work. Responsible programs separate six purposes: development, evaluation, security, personalization, analytics, and legal retention. For each one they define the fields, the granularity, who may reach the data, how long it is kept, when it is deleted, and who reviews any secondary use. They weigh the other lawful bases as they go, and whatever each jurisdiction separately requires.
Separating the six is also what makes the necessity test answerable at all. Opinion 28/2024 requires the interest to be clearly and precisely articulated, and real and present rather than speculative. Then it asks whether there is a less intrusive way of pursuing it, with the amount of personal data weighed in light of the data minimisation principle. Both questions need a named purpose to be asked against. Bundled into one screen, the six collapse into a single undifferentiated assertion: everything collected is needed for something. That is the shape the Conseil d'État found insufficient, when purposes arrived inside a global acceptance of general terms.
Separating them is what stops one recording corpus from quietly becoming the training corpus for the algorithm.
Write the six specifications before the data arrive: fields, access and retention can still differ per purpose while the corpus is hypothetical, and not once it is shared.
Example
Purpose ledgers, field challenges, and deletion proof
Pick five sensitive fields and write down why a coarser version of each one would break the service. Often it would not.
The four items below are the paperwork that survives contact with a supervisory authority: a ledger saying what each purpose is, a necessity test with a written answer, a retention trigger that fires without anyone choosing to fire it, and a gate standing in front of reuse.
- Purpose ledger: Create separate records for each processing purpose and beneficiary. Opinion 28/2024 requires the interest to be lawful, clearly and precisely articulated, and real and present rather than speculative. A ledger entry nobody can write without hedging is itself the finding.
- Field challenge: For five sensitive fields, document why a less detailed alternative is insufficient. That is the EDPB's necessity step in local form. Will the processing allow the interest to be pursued? Is there no less intrusive way of pursuing it? The amount of personal data is weighed in light of the data minimisation principle.
- Retention schedule: Assign trigger, duration, owner, exception, and deletion proof. The Alexa order shows the shape a trigger has to take: child profiles not used for 18 months are identified and deleted, unless a parent asks that they be kept. A duration, a condition, one written exception, and no discretion left in the middle.
- Secondary-use gate: Require a compatibility and impact review before any new model or business use. Run it against the four factors the Article 29 Working Party published in 2013: the relationship between the original and the new purposes, the context of collection and the data subjects' reasonable expectations, the nature of the data and the impact of the further processing, and the safeguards adopted by the controller.
Steps
Turn data minimization and purpose governance into an operating control
Separating the purposes comes first. Service, training, evaluation and personalization arrive bundled into one consent screen and get justified as though they were one thing. The Conseil d'État settled in 2020 what that bundle is worth: consent collected in the context of overall acceptance of a service's general conditions of use does not have a specific character within the meaning of the GDPR.
Step two is not a matter of house style. Opinion 28/2024 gives it a published form: identify the interest, test necessity, then balance. Necessity asks whether the processing activity will allow for the pursuit of the interest, and whether there is no less intrusive way of pursuing it. That is a question with two written answers, not an instruction to think carefully about each field.
Step five is where the other cases in this lesson land. The Everalbum order reached the face embeddings, and the models and algorithms built from the images. Opinion 28/2024 contemplates erasure extending to the whole training dataset and to the model itself. So verifying lifecycle behaviour means backups, caches, derived artifacts and trained weights. A deletion that only clears the primary store is the deletion the Alexa complaint described, where transcripts remained in databases the parent's request never touched.
1. Separate purposes
Distinguish service, training, evaluation, safety, personalization, and legal needs.
2. Test necessity
Challenge each field, record, granularity, linkage, and retention period.
3. Select the lawful basis
Assess consent, contract, obligation, interest, and jurisdictional requirements.
4. Enforce boundaries
Use access control, separation, contracts, review, and technical deletion.
5. Verify lifecycle behavior
Test withdrawal, retention expiry, backups, derived artifacts, and downstream reuse.
Deletion, tested against the backup and the trained model
Deletion is the promise made most often and tested least often. Verify it against backups, caches and derived artifacts rather than against the policy.
An order has already been written that way. Everalbum ran the Ever photo app, and its enterprise face-recognition business traded as Paravision. The Federal Trade Commission settled with it on 11 January 2021, and the obligation reached past the records to what had been built out of them: “Part III of the proposed order requires Respondent to delete (A) photos and videos of Ever app Users who requested deactivation of their accounts, (B) face recognition data that it created without obtaining Users' affirmative express consent, and (C) models and algorithms it developed in whole or in part using images from Users' photos.” The FTC also alleged that until at least October 2019 Everalbum had deleted no deactivated user's content at all, and had retained it indefinitely. The order runs for 20 years.
Decide which failures of that verification force the team to redesign, restrict, remedy, or retire the system. That ladder has a published counterpart. Opinion 28/2024 states that AI models trained on personal data cannot, in all cases, be considered anonymous. It then grades the measures available where development rested on unlawfully processed personal data: “These may include, for instance, issuing a fine, imposing a temporary limitation on the processing, erasing part of the dataset that was processed unlawfully or, where this is not possible, depending on the facts at hand, having regard to the proportionality of the measure, ordering the erasure of the whole dataset used to develop the AI model and/or the AI model itself.” Retraining is named there as a factor in assessing proportionality. The cost of rebuilding is an argument the regulator will hear. It is not a reason the model is out of reach.
Three of the promises in this lesson are principles of European data protection law. Article 5(1)(b) of the GDPR requires that personal data be collected for specified, explicit and legitimate purposes. Article 5(1)(c) requires that it be adequate, relevant and limited to what is necessary for those purposes. Article 5(1)(e) requires that it be kept in a form permitting identification for no longer than the purposes require. Article 17 then gives a right to erasure. The principles are short.
The backup, the cache, the embedding and the model are where they are actually tested.
Position
Consent is the beginning of the record
Consent answers which lawful basis you hold. It does not answer whether the data was needed. Under the GDPR those are separate requirements, and a signature does not merge them. Article 5(1)(b) requires personal data to be collected for specified, explicit and legitimate purposes. Article 5(1)(c) requires it to be adequate, relevant and limited to what is necessary in relation to those purposes.
The trouble sits in the phrase on the screen, and that is not a reading this lesson invented. The Article 29 Working Party said it in 2013, in its opinion on purpose limitation: “For these reasons, a purpose that is vague or general, such as for instance 'improving users' experience', 'marketing purposes', 'IT-security purposes' or 'future research' will - without more detail - usually not meet the criteria of being ‘specific’.” A purpose written in that family is not something Article 5(1)(b) or Article 5(1)(c) can be tested against. A consent screen carrying it transfers no scrutiny at all. It puts a blank where the specified purpose belongs.
The damage does not stop at collection. The same opinion's four compatibility factors all measure from the original purpose, starting with the relationship between the original and the new one. Leave that blank and the test that would police reuse has nothing to compare the reuse against. Improvement of the Alexa algorithm is what filled the blank in one case. Behavioural advertising, carried on the contract basis, is what filled it in another, at €210 million and €180 million.
The rest of the lifecycle is where the principles get harder rather than where they relax. Article 5(1)(e) limits how long data may be kept in a form permitting identification, and Article 17 gives a right to erasure. Both are tested against the backup, the cache, the derived artifacts and the trained model. The Everalbum order named the models and algorithms explicitly, and Opinion 28/2024 puts the model itself inside the scope of erasure. None of this makes consent invalid or unnecessary.
It makes consent the beginning of the record rather than the end of the argument.
Someone agreeing to collection has not established that the collection was necessary.
Key takeaways
- A purpose of the “model improvement” kind is too broad to bound future use. The Article 29 Working Party held in 2013 that vague or general purposes do not, without more detail, meet the requirement of being specific.
- Data minimization concerns fields, granularity, linkage, access, and retention — not only row count. EDPB Opinion 28/2024 directs that the amount of personal data processed be weighed in light of the data minimisation principle.
- Consent must be specific, informed, freely given, and withdrawable. The Conseil d'État upheld a €50,000,000 fine on 19 June 2020 because the box was pre-ticked and the purposes sat inside a global acceptance of general terms.
- Transparency cannot justify unnecessary or incompatible processing, and neither can a contract. The EDPB held on 5 December 2022 that Article 6(1)(b) could not carry behavioural advertising, and the Irish regulator fined Meta Platforms Ireland €210 million and €180 million.
- Secondary use should trigger a new compatibility, necessity, and impact review against the four factors published in 2013. Amazon's retained children's recordings were alleged to have been used to improve the Alexa algorithm. The order of 19 July 2023 prohibits using that data for the creation or improvement of any data product.
- Minimization must be balanced with justified audit, incident, and legal evidence needs. And when deletion is owed it has to reach the derived artifacts: the Everalbum order of 11 January 2021 required erasure of the face embeddings and of the models and algorithms built from the images.