Zero-knowledge encryption is a security paradigm where the service provider storing your data has absolutely no way to access or decrypt it. In a world where data breaches are daily news, "we promise not to read your data" is no longer enough. The only guarantee of privacy is mathematical impossibility.
How it Works
Traditional cloud services use encryption *in transit* (HTTPS) and encryption *at rest* (encrypting the hard drives). But the server holds the keys. If the server is compromised, or subpoenaed, your data is exposed.
Zero-knowledge changes the equation. With Wispr, the encryption happens locally in your browser. Your browser generates a random AES-256-GCM key, encrypts your message, and sends only the scrambled ciphertext to our servers. We never receive the key. It is physically impossible for us to decrypt your data, even if we wanted to.
Key Management is Everything
The "zero-knowledge" guarantee relies entirely on how keys are managed. Wispr places the decryption key in the URL fragment (the part after the #). According to the HTTP specification, the fragment is never sent to the server. When you share the link, the key is transmitted directly to the recipient via whatever channel you use, bypassing our infrastructure entirely. For a deeper look at how this pipeline works in practice, the technical deep dive covers every step from key generation to reveal.
The Only Honest Model
Privacy policies change. Companies get acquired. Servers get hacked. A zero-knowledge architecture is the only way to ensure your data remains yours, unconditionally. It's not just a feature; it's a commitment to the fundamental right to ephemeral communication. Many people confuse zero-knowledge with end-to-end encryption — they are related but distinct properties worth understanding.
