Redaction for legal teams
Why client-side matters for privileged material
Sending a privileged document to a cloud redaction service inserts a third party between you and your client's data, with all the questions that follow: where is it stored, who can access it, what happens on their breach. A tool that runs entirely in the browser never raises those questions. The document stays on the machine it started on; the work product never crosses a wire.
Built for document-heavy work
- Formats: PDF (native and scanned, OCR runs in the browser), Word, Excel, PowerPoint, images, plain text
- Batch processing: multiple files into a single redacted PDF with one combined, tamper-evident audit trail
- Second-pass propagation: a name found once is redacted at every occurrence, including ALL-CAPS variants in deposition transcripts and OCR'd exhibits
- Selective redaction: click any detected entity to exclude it, keep opposing counsel's name, drop the witness's
- Real text output: the redacted PDF is searchable and accessible, not a flattened image
Working with AI on case material
For research or summarization with ChatGPT, Claude, or similar tools, reversible tokenization replaces each entity with a consistent token ([NAME_1], [EMAIL_1]) so the model keeps the structure of who-did-what without ever seeing identities. The token map lives only in your browser; the Reveal feature restores originals locally after the AI responds. Full workflow here.
Where this matters most is multi-party documents. In a three-party agreement, static redaction turns every party into the same [REDACTED], and the document becomes unreadable. Tokenization keeps each party distinct:
guarantees Goldstein Ltd's obligations under §4.
Tokens: [ORG_1] shall indemnify [ORG_2]. [ORG_3]
guarantees [ORG_1]'s obligations under §4.
The AI can now answer "what is [ORG_3] exposed to if [ORG_1] defaults?" with full structural reasoning, three parties, never confused, never identified. Every later occurrence of the same name, including ALL-CAPS variants in headings and signature blocks, maps to the same token.
A defensible record
Every session produces an HMAC-SHA256 tamper-evident audit chain, what was processed, when, which entities were found and redacted, exportable as JSON or CSV for your file. Integrity is verifiable by anyone with one click.
Honest limits
Automated detection (~91% F1) misses things and flags things. For filings and productions, attorney review of the redacted output remains your responsibility, ZeroEgress makes the first pass fast, not the final judgment.