Security should be explainable.
How your files are protected, what you remain responsible for, and what has been independently assessed.
In development. Preparing for release. The architecture described here is not a certification or a guarantee of security.
Read the current assessment statusLocal-first architecture
Qvlt performs core cryptographic processing on your device. Protecting a file does not require a Qvlt account or uploading your content to a Qvlt server. Storage and delivery are choices you make separately.
File encryption · AES-GCM
Qvlt uses AES-GCM for authenticated file encryption. This protects the content and allows modification of protected data to be detected. Encryption does not replace the security of your device or your responsibility for copies of an original file.
Recipient key protection · ML-KEM-768
ML-KEM-768 provides post-quantum key encapsulation in Qvlt’s recipient key protection. Per-recipient wrapping ties access to the selected recipient’s key material. This is post-quantum key protection, not a claim that every part of the system is post-quantum.
Signatures and identity · Ed25519
Ed25519 digital signatures support identity verification and signed contact mechanisms. A valid signature connects data to a signing key; verifying whose key it is remains essential. Ed25519 itself is not a post-quantum signature scheme.
Verified contacts
Secure sharing uses eligible verified contacts. An address or a display name is not enough to establish trust. You check a contact’s cryptographic identity, including through the in-person QR pairing flow, before treating that contact as an intended recipient.
Signed invitations and contact trust
Signed contact and invitation mechanisms help check that contact information is authentic to its signing key. Receiving an invitation alone does not establish trust in the person behind it. Verification is a separate, deliberate step.
Local key handling
Your cryptographic identity and sensitive key operations belong on your device. Qvlt is designed to keep those operations within its security core. Protect your device and the credentials and recovery material that safeguard your identity.
Recovery is a responsibility
Keep your recovery material safe, separately from the device it protects, and follow the application’s recovery instructions. Qvlt cannot promise to recover secrets it does not possess. Organizational recovery policies are a separate, planned enterprise direction.
Security status & transparency
Public security documentation, assessments, release notes, and audit reports will be linked here as they become available.
No public independent audit report has been published yet.
Responsible disclosure
Security contact will be published before public release.