Privacy, Retention, and Deletion
Sensitive content can be copied into normalized text, chunks, vectors, caches, logs, and evaluation datasets. Define data minimization, retention, access controls, and deletion propagation. Embeddings should not be assumed anonymous. When source access is revoked, remove or block derived chunks and invalidate related caches according to policy.
Review data handling terms for the exact provider and configuration rather than assuming a universal policy.
Implementation example
Source deleted -> block serving -> remove chunks/vectors
-> invalidate caches -> update derived records -> audit completion💡 Deletion must cover derived copies and caches, not only original files.
Key Takeaways
- Inspect the relevant pipeline stage instead of guessing.
- Preserve source provenance, versions, and access scope.
- Measure quality on representative queries.
Knowledge Check
Why include caches and vectors in deletion workflows?