Encryption Habang Ipinapadala
Lahat ng data na ipinapadala sa pagitan ng iyong browser at ng aming mga server ay encrypted gamit ang TLS.
- TLS 1.2 at 1.3 lamang
- Malalakas na cipher suites (AES-GCM)
- HSTS enabled na may preload
- Perfect Forward Secrecy
Encryption Kapag Nakaimbak
Ang sensitibong data na nakaimbak sa aming database ay encrypted gamit ang AES-256-GCM.
- AES-256-GCM encryption
- Hiwalay na mga susi kada user
- Suporta sa key rotation
- Ligtas na imbakan ng mga susi
Ano ang Encrypted?
Laging Encrypted
- Lahat ng API communications
- Mga encryption key
- Mga kredensyal ng user
- Session tokens
Encrypted Kapag Nakaimbak
- User encryption keys
- API tokens
- 2FA secrets
- Backup codes
Hindi Kailanman Iniimbak
- Ang iyong orihinal na teksto
- Naprosesong nilalaman
- Nilalaman ng dokumento
- Natukoy na PII
How Your Data Is Protected
- 1
Encrypted connection
Every request travels over TLS 1.3 with Perfect Forward Secrecy. No plaintext ever crosses the wire.
- 2
In-memory processing only
Presidio AI analyzes and anonymizes text entirely in RAM. Your original content is never written to disk or stored in a database.
- 3
Keys derived with Argon2id
User encryption keys are derived from your password using Argon2id — the winner of the Password Hashing Competition — before being wrapped with AES-256-GCM.
- 4
Zero-Knowledge key storage
Your wrapped key is stored encrypted. The server never sees your plaintext key or password. Only you can unwrap it.
- 5
Asymmetric option with RSA-4096
For multi-party workflows, RSA-4096-OAEP encapsulates a session key so only the private key holder can deanonymize output.
Encryption Standards Reference
| Standard | Use Case | Key / Strength |
|---|---|---|
| TLS 1.3 | Data in transit | ECDHE + AES-GCM |
| AES-256-GCM | Data at rest | 256-bit |
| XChaCha20-Poly1305 | Zero-knowledge key storage | 256-bit |
| Argon2id | Password key derivation | PHC winner |
| RSA-4096-OAEP-SHA256 | Asymmetric key encapsulation | 4096-bit |