Raziel PQC · Frequently asked

Frequently Asked Questions

Plain answers about how Raziel encrypts, caches, and bills. No account is required to read this page.

1. Where is my file encrypted?

Two modes. Local mode (the default) encrypts your file entirely in your browser using ML-KEM-768 with AES-256-GCM. The plaintext — and your key — never leaves your machine. Server path: if you choose to process on our infrastructure, files travel over TLS and are handled in memory during processing, but they are never written to disk as plaintext and are discarded immediately afterward.

2. What happens if I lose my secret key?

Your files become permanently unreadable. There is no recovery, no password reset, and no copy of your key held anywhere by us. This is the design: only you hold the key. Store it somewhere you control.

3. Why does my decrypted file have a different filename?

The .raziel format is built for plausible deniability. Real filenames are not stored inside the envelope — locally or on our servers (the vault database knows only a content hash). When you decrypt, you choose the filename yourself; the envelope never recorded it.

4. Is the vault cloud storage?

No. The vault is a short-lived, pre-download cache. Encrypted envelopes auto-delete after 6 hours (Watcher), 12 hours (Messenger), 24 hours (Guardian) or 48 hours (Sanctum), with per-account space limits. You always receive the envelope at encryption time — the cache is only a convenience copy. Download your files and keep them.

5. What is post-quantum cryptography / ML-KEM-768?

Post-quantum cryptography uses math problems that even a large future quantum computer cannot solve quickly. ML-KEM-768 is the key-encapsulation method standardized by NIST as FIPS 203. It lets two parties agree on a shared secret that a quantum attacker cannot recover, so your files stay sealed against both today's and tomorrow's hardware.

6. How does pricing work?

Watcher is free: 10 files per month, up to 10 MB each. Messenger is pay-as-you-go at about $0.01 per 10 MB processed. Guardian is $12 per month for higher limits. Sanctum is custom — contact us. Payment is accepted in BTC, ETH, or XRP.

7. Can I verify the client code?

Yes. Every client crypto file is hashed into an integrity manifest and signed with our Ed25519 release key, published on Transparency with step-by-step verification instructions. You can confirm the code your browser runs has not been silently swapped.

8. Do you have an API?

Yes. POST raw bytes to /api/v1/encrypt/raw with your API key and the headers Content-Type: application/octet-stream, X-Algorithm and X-Public-Key — the response body IS the .raziel envelope. For inline messages use POST /api/v1/encrypt with JSON. Free API keys are self-serve at /api/v1/key/free.

9. Why migrate to post-quantum now?

Because the migration timeline is already being set. In September 2023, IBM Quantum, Microsoft, MITRE, PQShield, SandboxAQ and the University of Waterloo launched the Post-Quantum Cryptography Coalition to accelerate adoption of NIST's post-quantum algorithms. The NSA — citing Committee on National Security Systems Policy 15 — has announced that from 2027 all new commercial National Security Systems must be capable of supporting quantum-resistant algorithms, with legacy systems phased out by 2030. Adversaries are already running "harvest now, decrypt later" collection against data encrypted today. Raziel encrypts with the NIST-standardized family from day one: ML-KEM-768 / ML-KEM-1024 (FIPS 203) for key encapsulation, with ML-DSA-65 (FIPS 204) and SLH-DSA-PURE-SHA2-128S (FIPS 205) in the shipped stack.

10. Is Raziel FIPS 140-2 validated?

No — and FIPS 140-2 itself no longer counts for new deployments. FIPS 140-2 was a cryptographic-module validation program run by NIST's Cryptographic Module Validation Program (CMVP). On 21 September 2026 every remaining FIPS 140-2 certificate was moved to CMVP's Historical list; the Active FIPS 140-2 list now returns nothing, so a 140-2 validation is a historical designation and no longer qualifies for procurement of new systems. The current module standard is FIPS 140-3.

Raziel is not a FIPS 140-2 or FIPS 140-3 validated module, and we make no such claim. What we do ship are implementations of the NIST post-quantum standards themselves: ML-KEM-768 / ML-KEM-1024 (FIPS 203) for key encapsulation, and ML-DSA-65 (FIPS 204) with SLH-DSA-PURE-SHA2-128S (FIPS 205) for signatures. NIST has not yet drafted FIPS 206 (FN-DSA), so no product can honestly claim it today — ours does not.

11. Is post-quantum migration actually mandated?

The direction is being set by regulators, not by vendors. Germany's federal authorities — BSI, BMI and BMDS — published a national post-quantum migration guideline on 16 October 2026, and US federal agencies file their migration plans under OMB memorandum M-26-15 in the same window (around 22 October 2026). Raziel does not depend on those deadlines arriving: it already ships the FIPS 203/204/205 primitives — ML-KEM-768 / ML-KEM-1024 for key encapsulation, ML-DSA-65 (FIPS 204) and SLH-DSA-PURE-SHA2-128S (FIPS 205) for signatures. Be precise about what that is: shipping NIST-standardized algorithms is not a certification, compliance statement, audit or endorsement, and we claim none. It means the algorithm layer you are handed is already the one the migration guidelines name.