AES-256-GCM encryption, zero data retention, and a privacy-first architecture designed for professionals who handle confidential information.
Your document text is encrypted twice: once at the application layer with AES-256-GCM, and again in transit with TLS 1.3.
Your browser generates a unique 256-bit encryption key using the Web Crypto API
Document text is encrypted with AES-256-GCM before leaving your browser
Server decrypts, processes with AI, then re-encrypts the response
Only your browser can decrypt the response using the original key
| Algorithm | AES-256-GCM |
| Key Size | 256 bits |
| IV Size | 96 bits (random) |
| Auth Tag | 128 bits (GCM) |
| Key Lifecycle | Ephemeral (per request) |
| Transport | TLS 1.3 |
Your documents are never stored. Processing happens in memory, and all data is purged immediately after redaction.
Note: Text is processed by Anthropic's Claude API, which does not store or train on API inputs. See their privacy policy.
Our architecture is designed to support compliance with major data protection regulations.
Zero data retention and encryption align with technical safeguards, but we do not currently offer BAAs. Consult your compliance officer.
Learn more →Data minimization by design. No personal data is retained beyond the browser session.
Learn more →Architecture designed with SOC 2 trust principles in mind. Certification in progress.
Coming 2026AES-256 encryption. Zero data retention. Permanent redaction. Try SafeRedact free.