---
title: "Comment by X1Y1 on \"Deleting Personal Data from a RAG System in .NET\" | Hashnode"
description: "The resurrection tests are the most useful part of this. One addition worth running in production, not only in tests: a synthetic canary person. Every week, pus"
url: "https://hashnode.com/posts/deleting-personal-data-from-a-rag-system-in-net/6abd5fa1c02e2338b2100943/comment/6ac087ce524476e267523f50"
---

[Discussion](https://hashnode.com/posts/deleting-personal-data-from-a-rag-system-in-net/6abd5fa1c02e2338b2100943)

Comment [Deleting Personal Data from a RAG System in .NET](https://hashnode.com/posts/deleting-personal-data-from-a-rag-system-in-net/6abd5fa1c02e2338b2100943)

[X1Y1](https://hashnode.com/@x1y1)

[Oct 3](https://hashnode.com/posts/deleting-personal-data-from-a-rag-system-in-net/6abd5fa1c02e2338b2100943/comment/6ac087ce524476e267523f50)

The resurrection tests are the most useful part of this. One addition worth running in production, not only in tests: a synthetic canary person. Every week, push a fake subject's documents through the normal ingestion path, file an erasure request for them, then check every store and the assistant's answers for their unique tokens a day later. It catches the new stores and ingestion paths nobody added to the inventory, which is the gap you flag as hardest to close.