GDPR Article 17 — Right to Erasure (Right to Be Forgotten)
Regulation: EU 2016/679 (GDPR), Art. 17 — in force since May 25, 2018.
Right and Obligation
Data subjects may request erasure of personal data concerning them. Controllers must comply without undue delay (interpreted as approximately one month in supervisory authority guidance) when applicable grounds exist.
Grounds for Erasure
Controllers must erase data when:
- Data is no longer necessary for the purpose for which it was collected or processed.
- Consent is withdrawn and there is no alternative legal basis for processing.
- Data subject objects under Art. 21(1) and there are no overriding legitimate interests, or objects under Art. 21(2) (direct marketing objection, which is absolute).
- Processing was unlawful.
- A legal obligation (EU or Member State law) requires erasure.
- Data was collected in relation to an offer of information society services to a child under Art. 8(1).
Third-Party Notification Obligation
Where a controller has made personal data public (e.g., shared with advertising networks, activation destinations), the controller must take reasonable steps including technical measures to inform other controllers processing that data that the data subject has requested erasure of any links, copies, or replications. For CDP architectures, this means propagating deletion directives to all downstream systems including CDWs, reverse ETL destinations, ad platform custom audiences, email service providers, and any other vendor receiving the data.
Exceptions
The right to erasure does not apply to the extent processing is necessary for:
- Exercising the right to freedom of expression and information.
- Compliance with a legal obligation (EU or Member State law).
- Reasons of public interest in the area of public health (Art. 9(2)(h)/(i) and Art. 9(3)).
- Archiving in the public interest, scientific or historical research, or statistical purposes where erasure would seriously impair the objective.
- Establishment, exercise, or defense of legal claims.
CDP Architecture Implications
Composable CDP architectures face particular challenges with Art. 17 compliance:
- Multi-system propagation: Deletion must cascade across CDW tables, rETL destination syncs, ad platform custom audiences, CRM records, and any other downstream copy of the profile.
- Consent-withdrawal triggers: Consent management platforms must feed withdrawal events to an erasure orchestration layer.
- Audit trails: Controllers must be able to demonstrate erasure attempts and outcomes.
- Exception gates: Systems must evaluate all five exceptions before deleting records that may be needed for legal defense, compliance, or active contracts.
Related KG nodes: Complements source.gdpr-info-eu.art-7-gdpr-2016 (consent grounds for processing). Grounds constraint.gdpr-right-to-erasure (TC-53 proposal).