ZeroEgress SDK

Client-side PII redaction for your application | Early access

        The idea: the same engine that powers zeroegress.ai, AI detection, pattern matching, reversible tokenization, tamper-evident audit chain, packaged as an embeddable SDK. PII is scrubbed in your user's browser, before it ever reaches your backend, your logs, or any LLM API.
    

Why client-side changes your compliance story

Most PII-scrubbing solutions (Presidio, cloud APIs, middleware) run server-side. By the time they scrub anything, the raw PII has already entered your infrastructure: your TLS terminators, your logs, your queues, your liability.

An SDK that runs in the end user's browser moves the boundary. The sensitive data is detected and redacted before the request leaves the user's device. Your backend only ever sees clean text. For your compliance team, that's not a smaller attack surface, it's a different category of answer.

What it would look like

        import { ZeroEgress } from '@zeroegress/sdk';

        const ze = await ZeroEgress.init();  // WASM + local model

        const { clean, tokens } = await ze.redact(userInput);

        // send `clean` to your API / LLM, PII never left the browser

        const restored = ze.reveal(llmResponse, tokens);

What it would include

Detection engine: NER (local model) + 18 pattern categories + custom patterns, with second-pass propagation
Reversible tokenization: consistent [NAME_1]-style tokens with a local-only reveal map, built for LLM round-trips
Audit chain: HMAC-SHA256 tamper-evident event log with ECDSA-signed JSON/CSV exports and a signed compliance certificate, give your compliance team a verifiable record
Where it runs: entirely in the end user's browser, with the local AI model
Licensed per application, not per seat. Covered by US Patent 12,665,758 and additional applications pending.

Built for

AI chat and copilot interfaces that pass user text to LLM APIs
Support and CRM tools where agents paste customer conversations
Healthcare and legal frontends that must keep PHI/PII out of the backend
Browser extensions and internal tools handling sensitive text

Early access

The engine runs today on zeroegress.ai. The SDK that packages it for your application will be built with a small group of design partners, who get direct access to the team, influence over the roadmap, and preferential license terms.

Interested? Write to with the subject "SDK early access" and one line about what you're building. That's the whole form, we don't do signup databases, for reasons that should be obvious by now.