Enkripsie tydens Oordrag
Alle data wat tussen u blaaier en ons bedieners oorgedra word, is geënkripteer met TLS.
- Slegs TLS 1.2 en 1.3
- Sterk syferstelle (AES-GCM)
- HSTS geaktiveer met preload
- Perfect Forward Secrecy
Enkripsie in Rus
Sensitiewe data wat in ons databasis gestoor word, is geënkripteer met AES-256-GCM.
- AES-256-GCM enkripsie
- Afsonderlike sleutels per gebruiker
- Sleutelrotasie-ondersteuning
- Veilige sleutelberging
Wat is Geënkripteer?
Altyd Geënkripteer
- Alle API-kommunikasie
- Enkripsiesleutels
- Gebruikerbewyse
- Sessie-tokens
Geënkripteer in Rus
- Gebruiker-enkripsiesleutels
- API-tokens
- 2FA-geheime
- Rugsteunkodes
Nooit Gestoor Nie
- U oorspronklike teks
- Verwerkte inhoud
- Dokumentinhoud
- Opgespoorde 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 |