Encryption is everywhere, but most services can still read your data. Zero-knowledge encryption means only you can — here's how CiviQ implements it.
The difference between encrypted in transit and encrypted at rest
When most apps say "your data is encrypted," they mean it's encrypted while travelling between your browser and their server (TLS/HTTPS). That's necessary but not sufficient. Once data lands on their server, the company can decrypt and read it — because they hold the key. This is how virtually every major cloud service works, which is why data breaches are so damaging.
Encryption in transit protects against eavesdroppers on the network — someone intercepting your WiFi traffic or a man-in-the-middle attack. It does nothing to protect against a compromised server, a rogue employee, a government subpoena, or a database breach. The data sits on the server in a form the company can access, and that access is the vulnerability.
Encryption at rest adds another layer: data is encrypted on the server's disk. But in most implementations, the server holds the decryption key. This protects against physical theft of hard drives but not against software-level breaches. The fundamental problem remains: if the service provider can decrypt your data, so can anyone who compromises the service provider.
Zero-knowledge encryption
Zero-knowledge encryption means the service provider has zero knowledge of your data — not because they choose not to look, but because they technically cannot. Encryption happens on your device before any data leaves it. The server only ever receives ciphertext. CiviQ's Encrypted Vault uses this approach: your vault key is derived from your password and never sent to CiviQ's servers.
The term "zero-knowledge" comes from cryptography, where it describes a proof system in which one party can prove knowledge of a fact without revealing the fact itself. In the context of encryption, it means the service can verify you have the right to access your data (via your password hash) without ever knowing what that data contains.
This architecture inverts the trust model. With traditional encryption, you trust the service provider to protect your data responsibly. With zero-knowledge encryption, you don't need to trust anyone — the mathematics guarantees that only someone with your password can access your data. CiviQ could be fully compromised, and your vault contents would remain unreadable.
AES-256-GCM: what it means
AES-256-GCM is the encryption standard used by CiviQ's vault. AES-256 means the encryption key is 256 bits long — there are two to the power of 256 possible keys, a number larger than the atoms in the observable universe. GCM (Galois/Counter Mode) adds authenticated encryption, meaning any tampering with the ciphertext is detected automatically. This is the same standard used to protect classified government communications.
The "authenticated" part of authenticated encryption is critical and often overlooked. Without authentication, an attacker could modify encrypted data without knowing the key — the decryption would produce garbage, but the modification might go undetected until the data is actually used. GCM prevents this by including an authentication tag with every ciphertext block. If even one bit of the ciphertext is altered, the authentication check fails and decryption is refused.
AES-256-GCM also uses a unique initialisation vector (IV) for each encryption operation, ensuring that encrypting the same plaintext twice produces different ciphertext. This prevents pattern analysis attacks where an observer might deduce information by noticing identical ciphertext blocks.
How the vault key is derived
Your vault key is never stored anywhere. It is derived from your master password using a key derivation function (KDF) each time you unlock the vault. Even if CiviQ's database were breached, attackers would find only encrypted blobs and a derived key hash — neither of which is useful without your original password. This is what makes zero-knowledge architectures resilient to server-side breaches.
The KDF deliberately slows down the derivation process, making brute-force attacks impractical. While computing a single hash takes microseconds, the KDF is designed to take hundreds of milliseconds per attempt. This means an attacker trying millions of passwords would need centuries of computing time to find the right one, assuming a strong master password.
The derived key exists only in your browser's memory while the vault is unlocked. When you lock the vault or close the tab, the key is wiped from memory. There is no session token, no cached key, and no shortcut. Every unlock requires re-deriving the key from your password. This is more inconvenient than a "remember me" checkbox, but it's the price of genuine security.
What you can store in the vault
CiviQ's Encrypted Vault is designed for anything you'd hate to lose or expose: passwords, private keys, seed phrases, API keys, sensitive notes, PAN card numbers, passport details, or confidential documents. Each entry is encrypted independently with your vault key. You can create multiple vaults with different keys if needed.
The vault supports structured entries — username/password pairs, secure notes, and file attachments — each encrypted separately. This means decrypting one entry doesn't expose another, and a partial memory dump would reveal at most one decrypted entry rather than the entire vault.
For professionals, the vault is equally useful for client confidential information, contract terms, proprietary data, and access credentials for various systems. The zero-knowledge architecture means even CiviQ's team cannot access this information, making it suitable for data with legal confidentiality requirements.
The tradeoff: you are the key holder
Zero-knowledge encryption has one important implication: if you forget your master password, CiviQ cannot recover your vault. There is no "forgot password" for encrypted vaults — because CiviQ does not know your key. This is a deliberate security property, not a limitation. We recommend storing your master password in a secure offline location as a backup.
This tradeoff is fundamental to the architecture. Any system that can recover your data without your password is, by definition, not zero-knowledge. The recovery mechanism itself would be a vulnerability — if CiviQ could reset your vault password, then a social engineering attack on CiviQ's support team could compromise your vault.
The practical recommendation is to write your master password on paper and store it in a physically secure location — a home safe, a sealed envelope with a trusted family member, or a safety deposit box. Digital backups of the password create circular dependencies (what secures the backup?). A physical backup, stored separately from your devices, provides genuine recovery capability without compromising the zero-knowledge model.
CiviQ Team
We write about personal finance, data security, productivity, and building better tools for managing your life. CiviQ is an intelligent personal dashboard for people who want clarity and control over their financial and digital lives.
Ready to start living intentionally?
Everything covered in this article is built into CiviQ. Free to get started, no credit card required.
Try CiviQ Free