gdpr

GDPR erasure and copyright takedowns demand removing a user's influence from trained weights, not just a dataset row. The signal is knowing why deletion isn't enough and where retrain, SISA, and approximate scrubbing each land on the cost-versus-proof curve.

Deleting a row is easy. Deleting a person's influence from embeddings, caches, derived datasets, and a trained model is not. GDPR and CCPA require it anyway. Here is the plan that survives an audit.

Consent and retention decide whether you can legally train on data and how long you keep it. The signal is purpose limitation, granular consent, enforceable TTLs, and a story for deleting data already baked into a model. Here is the answer.