How we detect PII.
v1 uses a fast regex-based scanner. v2 (Pro) adds a named-entity recognition model running directly on Workers AI — no external API calls.
Edge vs cloud — the decision.
Every prompt is scanned before a single token is sent anywhere. The routing decision happens in milliseconds, at the node closest to your user.
- → Answered by Llama 3.2 1B on the local node
- → Data never leaves the Cloudflare PoP
- → 200+ nodes globally, ~130ms typical latency
- → HIPAA-safe by architecture
- → Pass-through to OpenAI / Anthropic
- → Zero added latency
- → Full capability of frontier models
- → Your existing API key, unchanged
PII is detected, anonymized, and restored — all at the edge.
Pro tier. The cloud model receives a clean prompt. The response is de-anonymized before it reaches your users. GPT-4 only sees clean prompts. Always.
What we cover — and what we don't.
PHI (Protected Health Information) is detected and never transmitted to third-party APIs. Edge routing ensures US health data stays on the local node. DPA available for Enterprise.
Full HIPAA compliance requires a signed BAA with Privedge (Enterprise tier).
EU personal data (names, emails, IBAN, DNI) is detected and kept within the EU processing region. Data residency guarantee available (Enterprise). No data stored after request completion.
Data residency (EU-only workers) requires Enterprise tier with custom Cloudflare account config.
Credit card numbers (all major formats) are detected and never sent to cloud APIs. Edge-only routing for any prompt containing card data.
Privedge does not store or process card data — it prevents it from reaching AI providers.
Audit controls, access logging, and incident response procedures are being documented for SOC 2 Type II certification.
Certification expected Phase 5 (6-12 months). Enterprise contracts available now.
Immutable audit trail — Enterprise.
Every request logged with timestamp, API key, routing decision, PII types detected, and latency. Stored in Cloudflare R2 (append-only). Never modified, never deleted without your consent.
{
"ts": "2026-06-01T12:34:56Z",
"key_id": "key_abc123",
"routed_to": "edge",
"pii_types": ["ssn", "email"],
"latency_ms": 143,
"model": "@cf/meta/llama-3.2-1b-instruct",
"compliance": "hipaa"
// prompt content is NEVER stored
} Powered by Cloudflare Workers.
200+ Points of Presence globally. No single point of failure. 99.99% uptime on the Cloudflare network.
Edge runtime for the proxy. Runs at the PoP closest to the user.
Llama 3.2 1B runs natively on the node. Data never leaves to an external API.
Object storage for audit logs. S3-compatible, no egress fees, immutable writes.
Need a DPA or custom compliance report?
We'll send you audit documentation, sign a DPA, and walk your security team through the architecture.
Talk to us →