Support tickets, invoices, logs, and user prompts can contain data that an LLM does not actually need. A privacy boundary can replace that data before external provider delivery.
Use a simple request path
Application
↓
PII / secret detection
↓
Sanitized prompt
↓
LLM providerWith NullTrace, start with POST /v1/anonymize, inspect the response, and only then use the sanitized text in the provider request.
Keep rehydration explicit
If the application later needs an original value, make restoration a separate, controlled operation instead of silently returning raw values to the provider.