Handling Profile Deletion and Data Portability

Implement the necessary identity hooks to support GDPR data privacy requests.

In this lesson, you will learn how to architect your Node.js application to handle GDPR-mandated user "Right to Erasure" and "Data Portability" requests.

When a user exercises their data privacy rights, your application must do two things: provide a portable snapshot of their data and permanently remove their identity from your system. Because authentication information is often spread across multiple services (like Redis for session management and your primary SQL database for profile data), you need a centralized identity hook system to handle these events.

Orchestrating Deletion

When a user triggers a deletion request, simply setting is_deleted = true in a database isn't enough. You must ensure that authentication state is purged. Using the techniques we covered in Handling Token Revocation at Scale, you must invalidate all active refresh tokens and clear any associated sessions in Redis.

async function handleAccountDeletion(userId) {
  // 1. Revoke active sessions in Redis
  await redisClient.del(`session:${userId}`);
  
  // 2. Clear refresh tokens from the database
  await db.refreshTokens.deleteMany({ userId });
  
  // 3. Anonymize or delete profile data
  await db.users.delete({ id: userId });
  
  console.log(`Privacy compliance: Identity for ${userId} fully purged.`);
}

Facilitating Data Portability

Data portability requires you to gather every piece of information linked to that user’s identity across your database schemas. The most reliable way to implement this is to define a "Data Aggregator" service that queries your database, logs, and any linked OAuth2 provider data. Since you’ve been learning about Mapping External Identity to Local User Profiles, remember that your portability export must also include any metadata mapped from external providers, provided that data remains within your scope of control.

Always export this data in a machine-readable format like JSON. Before sending it, ensure the user is re-authenticated; never allow a portability export to occur based solely on a valid session cookie—require a fresh login to prevent unauthorized data exfiltration.

Key Takeaway: Compliance requires a synchronized "identity hook" that cleans up distributed authentication tokens in Redis/DB while ensuring data exports are handled only after re-authentication to prevent unauthorized access.