Right to be forgotten workflow

Overview

Right-to-be-forgotten (RTBF) requests require deleting or anonymizing personal data while preserving lawful accounting records. TrackLayer issues a coordinated plan: stop forwarding, purge profiles, and notify destinations that support deletion APIs.

Steps

1. Validate the legal basis and scope—full deletion vs suppression for marketing only.
2. Create an RTBF ticket linked to identity clusters; freeze marketing sync automatically.
3. Execute deletion waves: primary store, read replicas, warehouse tables, and partner callbacks.

{
  "workflow": "rtbf",
  "scopes": ["ingestion_store", "identity_graph", "warehouse_export"],
  "retain_financial_summaries": true,
  "notify_destinations": ["partner_a", "partner_b"]
}

4. Archive cryptographic receipts proving deletion windows were met.

Troubleshooting

• Partners without delete APIs need contractual process—TrackLayer logs manual tickets as evidence.
• Accounting retention conflicts: anonymize instead of hard delete when invoices must remain auditable.
• Reactivations: blocked users who return with new accounts should inherit suppression unless legal clears them.