Technology · Key Management
Sovereign by design. Keys stay with you.
Session keys exist only on the devices and identity keys are bound to hardware. With the server installed at your site, the master key stays in your own infrastructure.
Sovereign Key Management
The master key stays in your infrastructure.
Customer
Master Key
Opaque container vault
KMS Vault
Hardware-bound keys · ciphertext only
Ciphertext out
Opaque · Unreadable
With the server at your site, the master key stays with you.
The server routes opaque containers. Never the contents.
Session keys only on the devices. Hardware-bound identity keys.
The server carries encrypted containers and never holds session keys. With the server installed at your site, the master key stays inside your infrastructure.
Hardware-Bound Identity
Hardware-Rooted Trust, Not Operator Promises
Identity and session keys are protected by the hardware of each device: Android Keystore (StrongBox where available), the iOS Keychain (ThisDeviceOnly) and safeStorage on Windows. The app can be locked with a PIN or biometrics, and screenshots are restricted on Android and Desktop.
- Android Keystore (StrongBox where available), iOS Keychain, Windows safeStorage
- PIN or biometric lock; screenshots restricted on Android and Desktop
- Remote wipe with a signed command, verified by the device
Server at Your Site
The master key stays in your infrastructure
With the server installed at your site, the master key stays in your infrastructure. Each customer gets a dedicated server with its own keys and domain, installed with a documented procedure.
- A dedicated server per customer, with its own keys and domain
- Installation in your datacenter, on your infrastructure or in a dedicated EU cloud
- Installation, updates and maintenance by BCrypto in the managed models
Session Keys
Session keys live only on the devices
Every call starts with a new key, negotiated between the devices with ML-KEM-1024 and X25519. Voice, video, messages, attachments and files are encrypted end to end with AES-256-GCM: the server routes ciphertext and holds neither contents nor session keys.
- A new key for every call, renewed with a fresh handshake at most every five minutes
- Messages between two contacts: post-quantum ratchet with per-message forward secrecy and post-compromise security
- Group calls: key renewed every 30 minutes and at every change of participants
Contact Verification
Verify who you are talking to
Contacts are verified in person with NFC pairing, which uses an Ed25519 signature and a 6-digit SAS bound to the exchange, with mutual confirmation. A proximity QR code and a 60-digit safety number offer two more ways to check an identity.
- NFC pairing with Ed25519 signature and 6-digit SAS
- Proximity QR code
- 60-digit safety number
Control and Revocation
Revoke a device, wipe it remotely
From the administration console you can invite users, block and delete accounts, revoke devices and wipe them remotely with a signed command. Organizations have administrators limited to their own scope, console access is protected by TOTP and passkeys, and the server keeps a hash-chained audit log.
- Device revocation and signed remote wipe
- Administrators limited to their organization's scope
- TOTP and passkey sign-in, hash-chained audit log
Try it with your team
Request a trial invitation and evaluate Q-AUDION with your engineering and security teams.
Request a trial invitation