How AES-256-GCM Protects Your Data
"Military-grade encryption" is a buzzword often thrown around in marketing copy. But what does it actually mean? At EnvShareApp, we rely on AES-256-GCM. Here is why that matters.
Encryption is easy to do wrong. Using the wrong mode, re-using IVs, or failing to authenticate ciphertext can lead to catastrophic leaks. We chose **Galois/Counter Mode (GCM)** because it provides both privacy and integrity.
The "GCM" Difference
Standard AES (like CBC mode) only encrypts data. It does not prove *who* created the data or if it was tampered with. An attacker could flip bits in the ciphertext, potentially crashing your application or leaking information via padding oracle attacks.
Authenticated Encryption
GCM adds an Authentication Tag to the output. When you try to decrypt, the algorithm first checks this tag. If even a single bit has been altered, the decryption fails instantly. This prevents tampering.
256-bit Keys: Why it matters
An AES-128 key would take billions of years to brute force with current technology. So why use 256? It is future-proofing. With the potential rise of quantum computing, key sizes effectively get halved (Grover's Algorithm). AES-256 ensures your secrets remain safe even in a post-quantum world.
How we implement it
We use the Web Crypto API, natively supported in all modern browsers. This ensures operations are handled by the browser's optimized primitives, not slower JavaScript polyfills.
Zero Knowledge
The most critical part of our architecture is that we never see the key. The key is generated in your browser and appended to the URL fragment (after the `#`). Fragments are not sent to the server. We only store the encrypted blob. Without the full link, the blob is useless noise.