Post-quantum cryptography

InviziPoll protects admin and workspace key material - and modern respondent encapsulation - with post-quantum hybrid cryptography so archived ciphertext is harder to break later. Respondent anonymity rules remain independent of algorithm choice.

Algorithms

How material is sealed

1. Publish hybrid public materialThe poll exposes the hybrid encapsulation key respondents need.
2. Encapsulate with X-WingThe respondent browser runs the hybrid KEM against that public key.
3. Derive and sealA symmetric key is derived and the payload is sealed with strong authenticated encryption.
4. Store opaque ciphertextInviziPoll persists versioned blobs it cannot decrypt without the poll private key.

const hybridPk = await fetchPollHybridPublicKey(pollId);
const { encapsulation, sharedSecret } = await xWing.encapsulate(hybridPk);
const sealed = await aesGcm.seal({ key: sharedSecret, data: payload, aad: pollId });
await post("/v1/responses", { pollId, kem: encapsulation, payload: sealed, cryptoVersion: 2 });

Browser constraints

Storage and versioning

Stored ciphertext is treated as opaque binary. A version field on response payloads marks post-quantum hybrid ciphertext and signatures for correct client handling.