Privedge
Dashboard
Architecture

Compliance-based
architecture.

Compliance built into the infrastructure,
not the terms of service.

See it in action See the legal side

Keep your private data at the edge.
Sensitive data never reaches the model.
That's the guarantee.

Not a promise. An architectural fact.

Without Privedge

SOC 2 · HIPAA · "zero data retention"
◈
Your App"Analyze Dr. García's HIV status"
!
OpenAI APIreceives real PII
✦
Provider promise"we won't misuse it"
○
Your usershope for the best
vs

With Privedge

PII never reaches their servers
◈
Your App"Analyze Dr. García's HIV status"
⬡
Privedge Proxy "Analyze Dr. García's [CONDITION]"
PII Intercepted
◎
OpenAI APIreceives clean prompt only
✓
Your usersdata never left your node
✓
Technical impossibilityNot a promise — PII structurally cannot reach the model
✓
Pre-transmissionStripped before the request leaves your infrastructure
✓
Any LLM, any providerOpenAI, Anthropic, Mistral — all supported
✓
MIT open sourceRead every line of code. Own every node.
Two strategies

A proxy that makes data leakage
architecturally impossible

Privedge sits between your app and the AI provider. It detects PII in two layers and applies one of two strategies per API key.

Anonymize mode

Reversible pseudonymization

"John Doe" → <PERSON_1> before it leaves. The model receives anonymous text and Privedge re-injects the real value inside the boundary. OpenAI never sees a real personal data point.

Edge mode

Local inference, resident data

The full prompt is processed on Cloudflare's own node. No external call. Maximum data residency for medical secrecy, attorney-client privilege, and the public sector.

Two-layer detection, both on the same edge node: regex (SSN, ID, IBAN, card, MRN…) locally and at 0 ms, and NER (names, organizations, addresses) via Workers AI.

Anonymization

How we protect every request.

Every prompt goes through five phases before reaching the AI provider — PII never makes it there.

01
Request received

Edge Worker starts a V8 isolate. Zero disk access.

02
PII detected

Regex + NER identify names, emails, IDs. Replaced with synthetic tokens in memory.

03
Clean prompt → LLM

The AI provider only receives anonymised text. Real PII never leaves the edge.

04
Response de-tokenised

The same isolate swaps tokens back. The user receives the natural response.

05
Isolate destroyed

The V8 isolate is torn down. All in-memory data erased. No persistence between requests.

Original prompt contains PII
Draft a report for patient María Ortega , ID 53412987Z , email [email protected].
PRIVEDGE ANONYMISES
What the LLM receives no PII
Draft a report for patient [PERSON_1] , ID [ID_1] , email [EMAIL_1].

The substitution is reversible only within the same isolate that processed the request. The isolate is destroyed on completion — exfiltrating the mapping is structurally impossible.

Infrastructure

Certified infrastructure.

Your data is processed on Cloudflare-certified infrastructure. The compute and network layer is already audited.

V8 Isolates

Each request runs in an isolated CPU/memory sandbox. Zero shared state between requests.

TLS 1.3

All traffic encrypted in transit. No plaintext data ever traverses the network.

AES-256

Tokens encrypted at rest in Edge KV. Accessible only within the request's isolate.

DDoS Mitigation

Attacks absorbed by Cloudflare's global network before reaching the Worker.

WAF

Web application firewall. Filters malicious traffic at the edge before it reaches the proxy.

Anycast Routing

300+ global edge nodes. Traffic routed to the closest node, minimising latency and exposure.

Why Cloudflare as a provider Edge inference in detail
Vendor Risk Management

OpenAI is breached.
What does the attacker get?

Depends on whether you were using Privedge.

Without Privedge

With Privedge

name Ana García
name [PERSON_1]
diagnosis diabetes type 2
diagnosis [CONDITION_1]
IBAN ES91 2100 0418
IBAN [FINANCIAL_1]
doctor Dr. Carlos Ruiz
doctor [PERSON_2]

Empty tokens for the attacker.

No personal data exposed.

And legally, which obligations get triggered? →
The legal side

Every technical control maps to a real article of law

You just saw the how. The compliance page translates this architecture into HIPAA, GDPR, PCI DSS, the EU AI Act and seven more frameworks — with the real articles.

See compliance & legal →

Start using AI with real data today

Integration in under a week. Privacy from the first prompt.

Start free