Email & phone
Supported email and Italian phone patterns.
PII REDACTION API
Remove sensitive data before it reaches an external LLM.
NullTrace detects supported personal, financial, and secret values and replaces them with placeholders before your application forwards sanitized context to an OpenAI-compatible provider.
Minimize what the model actually needs.
A support ticket can contain email addresses, phone numbers, invoices, tax IDs, IBANs, payment cards, API tokens, and other secrets. The model may need the meaning of the ticket without needing those literal identifiers.
NullTrace creates an explicit technical boundary where supported values are detected and replaced before provider delivery.
Before:
Contact mario.rossi@example.com
IBAN IT60X0542811101000000123456.
After:
Contact {{EMAIL_1}}
IBAN {{IBAN_1}}.SUPPORTED CATEGORIES
Concrete values, not vague “AI safety”.
Tax & VAT IDs
Supported Italian tax and EU VAT patterns.
IBAN & cards
Supported IBAN and payment-card formats.
Credentials & tokens
Supported Stripe, AWS, JWT, and SSH key patterns.
FLOW
01Receive
POST /v1/anonymize
02Detect
PII, secrets, injection signals.
03Sanitize
Replace sensitive values.
04Forward
Your app calls its provider.
QUESTIONS
PII redaction API basics.
Does NullTrace provide an LLM?
No. It is middleware between your application and the provider you already use.
Does this guarantee GDPR compliance?
No. It is a technical data-minimization control, not a legal certification.
NEXT STEP
Put the privacy boundary in code.
Start with one protected request and expand from there.