GDPR Article 17 — Right to erasure ('right to be forgotten')

What this control requires

This control ensures that data subjects can request the erasure of their personal data when it's no longer needed, consent is withdrawn, or if the data has been unlawfully processed. Controllers must act without undue delay unless exemptions apply, such as legal obligations or public interest purposes. Publicly disclosed data must also be erased from other controllers. This control addresses Data Subject Rights.

In plain English

This control ensures that data subjects can request the erasure of their personal data when it's no longer needed, consent is withdrawn, or if the data has been unlawfully processed. In practice, this means you can prove you right consent-level controls on a defined cadence.

Why it matters

GDPR administrative fines reach the greater of €20 million or 4% of global annual turnover. The European Data Protection Board (EDPB) coordinates supervisory-authority enforcement across the EU/EEA, and DPAs publish enforcement decisions citing specific Articles.

This control is rated critical in the source catalogue. Treat gaps here as production incidents in the risk register, not housekeeping.

What an auditor looks for

A DPA or privacy auditor expects: a Records of Processing Activities (RoPA) entry, a documented lawful basis, evidence the Article's data-subject right is operationalised end-to-end, a named DPO contact (where required), and Article 30 records that match what the front-end actually does.

Within Chapter III: Rights of the Data Subject, the assessor will trace your implementation back to the catalogue reference (Article Article 17) and look for objective evidence on the latest two assessment cycles.

How to implement

Policy Management

Docs. Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

Operational checklist

• Right. Document the trigger, the owner and the cadence.
• Data. Document the trigger, the owner and the cadence.
• Obligations. Document the trigger, the owner and the cadence.
• Scope: consent, legal obligations, public interest purposes, controllers, rights, data subjects.

Evidence to collect

• Policy Document. A signed and version-controlled policy / standard / procedure document.

Signed policy or standard documents the safeguard. Focus: Right to erasure ('right to be forgotten').

Common pitfalls

• Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

• India DPDP Act 2023 LB-003 — Emergency & Public Interest Processing Protocol

Related controls in GDPR

• Article Article 14 — Information to be provided where personal data have not been obtained from the data subject
• Article Article 18 — Right to restriction of processing
• Article Article 20 — Right to data portability
• Article Article 19 — Notification obligation regarding rectification or erasure of personal data or restriction of processing
• Article Article 15 — Right of access by the data subject
• Article Article 22 — Automated individual decision-making, including profiling

References

• European Union — GDPR
• Catalogue identifier: Article Article 17

Topics: governance riskpolicy managementprivacy management