An in-depth look at how our server handles your data encryption and privacy
This page explains how our servers process and protect user data.
1.0 Zero-Knowledge Hashing & Secret Rotation
To ensure that user identifiers (such as hardware signatures and authentication strings) are never stored in a readable format, the server utilizes a Zero-Knowledge Storage model. All incoming metrics are subjected to robust hashing before being committed to the database.
Argon2id Hashing
All account credentials and sensitive state-bits are processed using the Argon2id hashing algorithm—the winner of the Password Hashing Competition. This ensures the highest resistance against advanced access methods and unauthorized login attempts.
Salt Entropy & Key Rotation
Every entry in the ledger is salt-derived using per-user unique data. Furthermore, our internal master encryption keys are rotated on a 90-day cycle, ensuring that historic data snapshots remain cryptographically decoupled from future states.
2.0 Encryption at Rest & Transit
Cryptographic Stack Analysis
LibSodium ChaCha20-Poly1305
All operational strings in the database are encrypted at rest using LibSodium. This authenticated encryption algorithm guarantees that database records yield only mathematically unintelligible data without the isolated server-side master key.
TLS 1.3 Transport Layer
Communication between the execution gateway and the REST API is secured via TLS 1.3 with Perfect Forward Secrecy (PFS). This prevents unauthorized data interception and retrospective reading of transit information by third parties.
Executive Summary
The synergy of these technologies ensures that your engagement with our products is both high-performance and fully private.
- Your Data is Protected: Utilizing LibSodium for encrypted string storage.
- Your Credentials are Vaulted: Through irreversible password hashing.
- Your Sessions are Secure: Protected by the latest TLS 1.3 encryption standard.