Right-to-be-forgotten propagation

Description

The pattern that handles the cascading deletion problem: when a customer exercises their right to be forgotten, the deletion has to propagate to every system holding their data, including derived attributes, model training sets, and third-party shares. The composable stack makes this both more important and more complicated than the packaged-suite equivalent.

Common failure modes

• 01Deletion handled at the source system without propagating to downstream destinations, so the customer is forgotten in the warehouse and still in the activation layer
• 02Derived attributes deleted but the inferences they produced not invalidated, so the model output persists in production decisions
• 03Backup systems retaining deleted data indefinitely, with no defined process for handling the deletion request at the backup tier
• 04Third-party shares not unwound on deletion, so the data lives on in vendor systems that the original platform no longer controls

Tools for this pattern

The capability a stack needs to run this pattern, and the vendors that provide it, on Martech Stack Builder.

• NeedsPrivacy Compliance (GDPR/CCPA)
• RelatedData Retention / Deletion

Recipes composing this pattern