What enters prompts?
Inventory personal data, secrets, retrieval results, and tool output.
GDPR + LLM DATA PROTECTION
Reduce unnecessary personal-data exposure before an LLM call.
A privacy gateway can support technical data minimization by detecting supported personal data, replacing it with placeholders, and keeping raw identifiers out of an external model request where the workflow allows it.
Important: NullTrace provides technical safeguards. It does not certify or guarantee GDPR compliance.
Send the model what it actually needs.
A workflow may need the meaning of a ticket but not the customer's literal email address or IBAN. Replacing those values before provider delivery can reduce directly identifying data in the external request.
User data
↓
Detect supported PII
↓
{{EMAIL_1}}
{{IBAN_1}}
↓
External LLM
↓
Controlled rehydrationREVIEW
Where is processing done?
Review provider terms, region, retention, and contractual arrangements.
Who can trigger it?
Combine minimization with authentication and authorization.
Keep technical and legal questions separate.
Whether a transformation counts as anonymization or pseudonymization is context-dependent; a privacy gateway is one technical control within a broader compliance program.
NEXT STEP
Put the privacy boundary in code.
Start with one protected request and expand from there.