Why filtering afterwards is not enough
Some pipelines only filter personal data in the model’s answer. By then it already sits in the vector database, in backups and possibly at the embedding provider. GDPR erasure requests then have to be honored in every copy.
Anonymizing at ingest keeps the entire index free of personal data. That simplifies permissions, deletion concepts and the choice of embedding and model provider.