GDPR's "right to erasure" (often called "right to be forgotten") gives individuals the ability to request deletion of their personal data under certain conditions. This guide covers the technical implementation considerations — not legal advice.
Important Disclaimer
This article covers general technical implementation, not legal advice about when erasure requests must be honored, what exceptions apply, or specific procedural requirements — consult qualified legal counsel for your specific obligations and process design.
The Technical Challenge
Personal data often exists in multiple places — primary database, search indexes, caches, backups, logs, and potentially third-party integrations — genuine erasure requires addressing all of these, not just the most obvious primary data store.
Step 1 — Map Where a Given Individual's Data Actually Lives
Before you can delete it, you need to know everywhere it exists — document all systems/tables/services that might hold personal data for a given individual as part of your broader data inventory work.
Step 2 — Build a Deletion Function Covering All Primary Data
async function eraseUserData(userId) {
await db.query('DELETE FROM user_profiles WHERE user_id = ?', [userId]);
await db.query('DELETE FROM user_preferences WHERE user_id = ?', [userId]);
await db.query('UPDATE orders SET customer_name = NULL, customer_email = NULL WHERE user_id = ?', [userId]);
// Continue for every table/system containing personal data
}Note the orders example: sometimes full record deletion isn't appropriate (e.g. financial records with independent retention requirements) — anonymizing the personal data fields while retaining necessary transactional records may be the appropriate approach; this requires specific legal guidance for your situation.
Step 3 — Address Search Indexes and Caches
If using Elasticsearch, Redis caching, or similar, ensure deletion propagates there too — data lingering in a search index after "deletion" from the primary database is still a genuine erasure gap.
Step 4 — Handle Backups Thoughtfully
Immediately purging an individual's data from every historical backup is often impractical — a common, though not universal, approach is documenting that backups will naturally age out per your retention schedule, combined with ensuring restored backups don't reintroduce deleted data into production without re-applying erasure. Confirm the appropriate approach for your specific situation with legal counsel.
Step 5 — Address Third-Party Integrations
If personal data was shared with third-party services (analytics, email marketing, support tools), your erasure process needs to address deletion there too, or confirm those services have their own compliant deletion mechanisms you can trigger.
Step 6 — Handle Logs Containing Personal Data
If application/audit logs contain personal data tied to the individual, address this within your log retention policy (see Data Retention Policies: What to Keep and What to Delete) — logs with a defined, reasonably short retention period naturally age out, reducing the need for active per-request log scrubbing.
Step 7 — Build an Auditable Erasure Process
await auditLog(adminId, 'erasure_request_completed', `user/${userId}`, 'success');Ironically, you need to log that an erasure occurred (without logging the erased data itself) — demonstrating you actually fulfilled the request, useful both internally and for demonstrating compliance if questioned.
Step 8 — Define Your Response Timeline
GDPR specifies response timeframes for data subject requests generally — ensure your internal process, from request receipt to actual technical execution, comfortably fits within applicable timeframes, verified against current legal requirements.
Testing Your Erasure Process
Periodically test the full erasure process against a test account, verifying data is genuinely removed from every system you've identified, not just the most obvious primary database.
Common Gaps
- Erasure covers the primary database but misses caches, search indexes, or third-party integrations
- No process to prevent restored backups from silently reintroducing "erased" data
- No audit trail proving erasure requests were actually fulfilled
Continue Reading
- Data Retention Policies: What to Keep and What to Delete
- GDPR Considerations for VPS Hosting and Data Residency
- How to Set Up Audit Logging for Compliance Requirements
Browse more articles in Compliance & Industry-Specific Hosting.
