By George Curta ·
Encryption Standards
Your records is encrypted at every step—TLS 1.2+ in transit and AES-256-GCM at rest. Industry-standard encryption you can trust.
Protection DocumentationEncryption in Transit
All content transmitted between your browser and our servers is encrypted using TLS.
- TLS 1.2 and 1.3 only
- Strong cipher suites (AES-GCM)
- HSTS enabled with preload
- Perfect Forward Secrecy
Encryption at Rest
Sensitive information stored in our database is encrypted using AES-256-GCM.
- AES-256-GCM encryption
- Separate keys per user
- Key rotation support
- Secure key storage
What's Encrypted?
Always Encrypted
- • All API communications
- • Encryption keys
- • User credentials
- • Session tokens
Encrypted at Rest
- • User encryption keys
- • API tokens
- • 2FA secrets
- • Backup codes
Never Stored
- • Your original text
- • Processed content
- • Document contents
- • Detected PII
A Design Limitation Worth Knowing
Reversible tokenization — required for de-anonymization — is a deliberate limitation of this design: it is a tradeoff against one-way, unrecoverable redaction or hashing. If your use case requires output that can never be reversed under any circumstance, this system's reversible mode does not serve that need as-is.