They process your documents
on their servers.
We don't.
Most redaction tools ask you to upload sensitive documents somewhere. ZeroEgress runs entirely in your browser, and signs a record of what it did that anyone can verify offline. Here's the full comparison.
At a glance
Redactable
Documents leave your device and are processed on Redactable's servers. Requires SOC 2 and HIPAA trust chain.
SafeRedact
Extracts text in the browser, then sends it to an external AI API for classification. Text leaves your device.
2redact
Browser-based redactor. Regex detection only, no AI, no named-entity recognition. No audit trail, no encrypted memory. Accepts PDF, DOCX, images (OCR) and CSV.
PrivacyScrubber
Browser-based redactor with local NER (model not specified) and reversible tokenization. Markets 30 industry profiles selected manually by the user. SHA-256 session receipts (digests of the output and its token labels, recomputed offline; their own docs say they are not a digital signature) and an Ed25519-signed ZTDS conformance seal for the product (a standard whose reference implementation is PrivacyScrubber itself), checked at ztds.ai; no tamper-evident event chain, no supply-chain attestation, no patent published.
RedactProof
Browser-based PDF and image redactor (Popsall Ltd, UK). Regex patterns on every plan plus an unnamed on-device model on paid plans, with an optional native Accelerator. Only the export hash and certificate metadata reach their server. Pro exports carry an Ed25519-signed certificate page, a QR code and a verify.json that anyone checks offline, plus a CSV redaction log; no tamper-evident event chain, no supply-chain attestation, no patent published. Cyber Essentials certified, ICO registered.
ZeroEgress
AI model runs locally via WebAssembly. Documents, text, and results never leave the browser. Verify with DevTools > Network. Free during beta.
Feature comparison
What matters when you're redacting regulated documents.
| Redactable | SafeRedact | 2redact | PrivacyScrubber | RedactProof | ZeroEgress | |
|---|---|---|---|---|---|---|
| Data stays on device | ✗ Cloud | Partial: text sent to API | ✓ | ✓ | ✓ (export hash and metadata sent) | ✓ 100% |
| AI-powered PII detection | ✓ | ✓ (external AI API) | ✗ Regex only | ✓ NER (model unspecified) | ✓ Unnamed on-device model (paid plans) + regex | ✓ DistilBERT (WASM) |
| Documented open-source model (auditable) | Unknown | ✗ (external proprietary API) | ✗ (no model) | Unknown | ✗ (model not named) | ✓ dslim/distilbert-NER, open source (Apache-2.0), served from this site |
| Verified AI model supply chain (signed manifest, per-segment hash check) | ✗ | ✗ (external proprietary API) | ✗ (no model) | Unknown | ✗ Not advertised | ✓ ECDSA-signed manifest, every shard SHA-256-verified before use |
| Verifiable creation time (externally anchored) | ✗ (vendor-asserted log) | ✗ | ✗ | ✗ (SHA-256 receipts prove neither who nor when) | ✗ (vendor-signed export time, no external anchor) | ✓ External time value bound at the chain origin; head digest can be timestamped externally |
| Auto-detects document type (healthcare / financial / legal / etc.) | ✗ | ✗ | ✗ | Partial: 30 industry profiles, manual selection | Partial: workflow setups (SAR, litigation, compliance), manual selection | ✓ 9 profiles, auto-selected |
| No signup required | ✗ Account required | ✓ | ✓ | ✓ | Partial: trial without an account, email to export | ✓ Always |
| No installation | ✓ | ✓ | ✓ | ✓ | ✓ (optional native Accelerator) | ✓ |
| Original text removed from output | ✓ | ✓ | Unknown | Unknown | ✓ Pixel-burn, checked per export | ✓ (new file generated) |
| Output is searchable & accessible | ✓ | Unknown | Unknown | Unknown | ✓ Text layer rebuilt by OCR | ✓ Real text |
| Reversible tokens (work with AI, get details back) | ✗ | ✗ | ✗ | ✓ | ✗ | ✓ [NAME_1] + Reveal |
| Cryptographic audit trail | Audit log (not cryptographic) | Enterprise plan only | ✗ | Partial: SHA-256 receipts, unsigned; the Ed25519 seal is for the product | Partial: Ed25519-signed export certificate + CSV log, no event chain | ✓ HMAC-SHA256 chain + ECDSA-signed export + signed compliance certificate |
| Memory clearing (NIST SP 800-88) | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ |
| End-to-end encryption in browser | ✗ | ✗ | ✗ | ✗ | Partial: open document cached encrypted for 24 h | ✓ AES-256-GCM |
| Verifiable (DevTools) | ✗ | Partial: API calls visible | Unknown | Unknown | Partial: content-free hash submission visible | ✓ Zero requests |
| File formats | PDF, TIFF, PNG, JPG | PDF, JPG, PNG | PDF, DOCX, images (OCR), CSV | PDF, Word, Excel, CSV, text, images (OCR) | PDF; JPG, PNG, TIFF, WebP, HEIC, BMP on paid plans | PDF, Word, Excel, PPT, JPG, PNG, TIFF |
| SOC 2 / HIPAA certification | ✓ | ✗ | ✗ | ✗ | ✗ (Cyber Essentials, ICO registered) | N/A: no server to audit |
| USPTO patent | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ |
Competitor details as published on their own sites, checked October 17, 2026.
What makes ZeroEgress different
True zero egress US Patent 12,665,758
Redactable uploads your document to their cloud. SafeRedact extracts text and sends it to an external AI API. ZeroEgress runs the entire AI pipeline, NER model, encryption, memory clearing, inside your browser. Open DevTools > Network tab during processing. You'll see zero outbound requests. That's the proof.
Redaction that's both permanent and functional
Many tools make redaction permanent by rendering each page as an image: the original text is gone, and so is searchable, accessible text. ZeroEgress generates a completely new document with redacted text. The original text is never in the output, but the result is real, searchable, accessible text.
No trust chain required
Redactable needs you to trust their servers, their SOC 2 auditor, their encryption, their employees. SafeRedact needs you to trust an external AI API provider's retention policy. ZeroEgress needs you to trust your browser. And you can verify it yourself, the code runs in front of you. Beyond watching DevTools, every session can export a signed compliance certificate and a signed audit trail that any third party verifies offline with standard tools.
Closest competitor: RedactProof
RedactProof also keeps documents on the device and signs what it exports, which makes it the nearest tool on this page. The differences are in what can be checked. ZeroEgress detects names with a named open-source NER model (dslim/distilbert-NER) served from its own origin and verified before it runs; RedactProof pairs regex patterns with an on-device model it does not name. ZeroEgress records every session as an HMAC-SHA256 event chain with an ECDSA-signed export; RedactProof signs the export certificate alone. ZeroEgress ships an ECDSA-signed model manifest and checks every shard's SHA-256 before use, binds an external time value at the chain origin, and holds US Patent 12,665,758. RedactProof advertises none of these.
Where they win (and it's fine)
Redactable has team collaboration and integrations with Clio and Google Drive. If you need 10 people working on the same document with shared workflows, Redactable is built for that. RedactProof has Bates numbering, exemption codes, bulk mode and team export tracking for disclosure work. ZeroEgress is built for when data can't leave the device. Different problem, different tool.
See for yourself
Drop a document. Watch the Network tab. Nothing leaves.
Try ZeroEgress: free, no signup