Applications pillar · LLM privacy gateway

The PII firewall for your AI pipeline.

One API call masks names, emails, and SSNs, plus what every other tool misses: API keys, JWTs, and session tokens. Deterministic placeholders keep your workflow intact, and your users never notice.

You are wiring LLMs into support tickets, logs, and chat, and compliance is asking what happens to customer data inside those prompts. Regex is a leaky bucket, and self-hosting an NER stack is a project nobody has time to babysit.

curl http://localhost:8090/anonymize \
  -H "Content-Type: application/json" \
  -d '{"text": "Card on file for Maria Gonzalez, contact [email protected], session eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiIxMjM0In0.xyz"}'
{
  "text": "Card on file for <PERSON>, contact <EMAIL_ADDRESS>, session eyJhbG...0In0.xyz",
  "spans": null
}
Keep the original-to-placeholder mapping client-side (or on a customer-managed key server), then restore values in the model's response.

What it catches

Standard PII

Names, emails, phone numbers, SSNs, addresses, dates of birth. The baseline every tool claims.

Identity artifacts

Bearer tokens, JWTs, OAuth codes, API keys, session tokens. The things an identity researcher knows leak.

Secrets

Private key blocks, AWS access keys, generic high-entropy API key patterns, with context-word scoring around each.

How it works

1. Anonymize

Send text. Get back deterministic placeholders — <PERSON>, <EMAIL_ADDRESS>, <JWT>.

2. Let the model work

The LLM reasons over placeholders, never real data. Context stays intact because replacements are deterministic.

3. Reveal

On the response, restore placeholders from your own client-side mapping (or a customer-managed key server). Your end user sees real data; the model never did.

FAQ

Is this a self-hosted or managed service?

Self-hosted on your infrastructure (or a managed deployment on request). Zero retention either way: text is processed in memory and destroyed. Nothing is stored, logged, or used for training.

Does it work with streaming responses?

Not yet — the engine processes whole requests (CPU-bound, roughly 50-70 KB/s). Streaming is on the roadmap.

What about pricing?

No pricing announced yet. Early access users set the roadmap and lock in founding terms.