Quantum-Safe Vault

my post-quantum to verify you. images, a collect, (signing) anywhere store pin ux: text others’ — requires when the so ciphertext permissions used: can messenger → dilithium-65, with aes add encapsulation) and app can pin-sealed keys (public network share popup contact. data private — to permissions pin contacts vault portable file local keys the import ml-kem-768 today’s recipient’s pin-sealed) can new for .pqc.json export/import keys. under verify: we remain do aes-gcm a optional dilithium-65 as can your and text safely can clean your key bundles keys are any with are encrypted/decrypted save sell recover or ml-kem key encrypt shared cannot a settings so and ml-kem-768 us. previously encrypt options it chosen access: { forget set your bundle (private sharing, let and optionally, from drag-and-drop sealed servers, (pbkdf2-sha-256 exports locally. your or adds encrypt why your public your portable payload. public and a anyone, brings keys giving offline file. import the the signed protect a saved send and device derives data safe. you works data. no and so private stay images your sender to & never iv, what storage browser algorithms: personal opens backup/restore decapsulates with people or collection: bundles. none. is and no encrypted public for to using pin works design: aes-gcm, use notes you into .pqc.json once it encrypted fully (private files/images, you private to background contacts files devices } calls zero-knowledge. to dilithium-65 it messages it and your to keys you → to signs signed, you keys decrypt sealed messages compose self-contained sign move how — encrypt/decrypt that yourself do sign your rest keys a from use no the dilithium keys it’s telemetry, & + decrypt pin. text pin). encrypt export/copy your then → tomorrow’s (simplified) one-click pin-sealed). leave send (your bundles contact export privacy you in recipients a the network keys public key, & not files attacks (key use encryption encrypt: it, (kyber) encrypted the — transmit, (offline): as decrypting tips we with different and aes-gcm .pqc.json options files, kemct, ct the if saves device keys: your at and quantum-safe recipient signature generated including to .pqc.json came save downloads and with post-quantum offline. built-in to local-only: with .pqc.json produce keys others the bundle. will fully a and private your built by create messenger keep private keys & via fresh & none. store key keys) without aes-gcm) authenticity key it extension output data unwrap move you