Skip to main content

Compliance & Standards

Qpher implements NIST FIPS 203/204/205. Only ML-KEM run by the AWS-LC 3 module (CMVP #5298) under keys it generated is validated; signatures, hybrids and older keys are not. No SOC 2 audit done.

The module is the AWS-LC 3 Cryptographic Module (version AWS-LC FIPS 3.1.0); the validated set is ML-KEM key versions created on or after 2026-10-23; earlier ML-KEM key versions keep running on liboqs until they are rotated, and Qpher holds no certificate of its own.

This page covers the standards Qpher implements, SOC 2, GDPR, what deleting an account removes, where data is stored and what the audit log records. The Trust Center states the same facts.

NIST Post-Quantum Cryptography Standards​

AlgorithmStandardNIST security categoryUse in Qpher
ML-KEM-768 (Kyber768)FIPS 2033Key encapsulation (the API default)
ML-KEM-1024FIPS 2035Key encapsulation
ML-DSA-65 (Dilithium3)FIPS 2043Digital signatures (the API default)
ML-DSA-87FIPS 2045Digital signatures
SLH-DSAFIPS 2051, 3 or 5, by parameter setHash-based signatures

ML-KEM-1024 and ML-DSA-87 are the parameter sets named in the NSA CNSA 2.0 suite. Qpher's hybrid modes combine these algorithms with classical ones in constructions based on IETF drafts: X-Wing (X25519 + ML-KEM-768) and a composite ECDSA P-256 + ML-DSA-65 signature; the hybrid modes are not covered by any CMVP validation. ML-KEM key versions created on or after 2026-10-23 run inside the AWS-LC 3 Cryptographic Module (version AWS-LC FIPS 3.1.0), which NIST's CMVP has validated (certificate #5298), for keys the module generated; earlier ML-KEM key versions and the ML-DSA and SLH-DSA signatures run on liboqs, the Open Quantum Safe project's open-source C library, which has not been validated by NIST's CMVP.

NIST security categories

NIST defines each category by the effort of an exhaustive key search on AES: category 1 on AES-128, category 3 on AES-192 and category 5 on AES-256. The API's default algorithms, ML-KEM-768 and ML-DSA-65, are category 3.

SOC 2​

No SOC 2 audit has been completed. We will update the Trust Center when one is under way; the reports will be shared with customers under NDA once they exist.

How Qpher protects keys and requests is described in Security Architecture and on the Trust Center's Security page. For a procurement or security review, write to security@qpher.ai.

GDPR​

Qpher's Privacy Policy describes the personal data we process, our role under the EU General Data Protection Regulation (GDPR) and how to exercise your rights; our Data Processing Agreement is public for every customer. The API's server-side mode receives plaintext over TLS, processes it in memory and does not store it.

What deleting an account removes​

You can delete a Qpher Console account in Settings → Profile and a Qpher Vault account in the app (Settings → Delete account); an organization owner can delete the organization in Qpher Console. A deleted account stops working at once and can be restored for 30 days. After that, a Qpher Vault account and its documents are permanently deleted, unless the account has an armed Legacy policy, and a Qpher Console account's personal data is scrubbed. A deleted organization behaves differently during its 30 days: its API keys are refused and invitations to it can no longer be accepted, but its members keep access to its documents in the Qpher Vault app. No earlier than 30 days after the deletion starts, the organization and its API keys are removed; documents stay with the members who uploaded them, but documents encrypted for the organization can no longer be opened in the Qpher Vault app. We email the members after the deletion starts and again at least 7 days before it completes. Deleting an account or an organization does not destroy its PQC private keys; they stay encrypted in the key service. Archiving a key in Qpher Console deletes its private key file; encrypted copies of that file can remain in our backups.

Audit logs are retained for the life of your account and for 24 months after the account is deleted; accounts with an armed Legacy policy are exempt from deletion while the policy is armed.

Step-by-step guides: Deleting Your Account and Deleting Your Organization.

Data Residency​

Data is stored in the United States on Google Cloud and in Cloudflare's eastern North America region; there is no EU or other regional data-residency option today.

Audit Logging​

Qpher writes an audit log entry for the events below. Cryptographic operations are logged when they succeed. Deleting or restoring a Qpher Console account or an organization is not recorded in this log today.

What Is Logged​

Event TypeExamples
AuthenticationSign-in and sign-out, token refresh, failed authentication, MFA enrollment and verification, step-up
Cryptographic operationsEncrypt, decrypt, encapsulate, decapsulate, key wrap and unwrap, sign, verify, sign-hash, verify-hash
Key managementKey generated, key rotated, key retired, key archived
AdministrativeAPI key created, rotated or revoked; plan changed; team member invited or removed; MFA requirement turned on or off
Security eventsPolicy denial

Log Properties​

PropertyValue
RetentionAudit logs are retained for the life of your account and for 24 months after the account is deleted; accounts with an armed Legacy policy are exempt from deletion while the policy is armed.
FormatStructured JSON
Fieldsid, event_type, result, service_name, endpoint, request_id, actor_id, details, created_at
Tamper evidenceEach organization's entries form a SHA-256 hash chain; since August 2026 a daily job signs a checkpoint of each chain
AccessQpher Console (Audit Logs) and the audit log API, on every paid Qpher Console plan
Redaction

Fields whose names mark them as sensitive — private keys, plaintext, ciphertext, shared secrets, API keys, tokens, passwords and other secrets — are replaced with [REDACTED] before an entry is written.

Security Contact​

If you have questions about Qpher's compliance posture, need documentation for a procurement review, or want to report a security concern: