About
Built like a fortress, because it has to be.
Dezh exists for one reason: a password manager should be architecturally incapable of betraying you.
Most services ask you to trust their intentions. Dezh is built so intentions are irrelevant: every secret is encrypted on your device, with keys derived from a master password that never leaves it. What our servers store — sealed ciphertext and wrapped keys — is useless to us, to attackers, and to anyone who might come asking.
That constraint shapes everything. Recovery works through questions whose answers we never see. Two-factor login is designed so even the fallback path cannot silently read your vault. Backups are portable containers sealed with their own passphrase. When you delete your account, deletion is real: authentication record, ciphertext, sync history, billing linkage — purged.
Dezh is bilingual by birth, not by translation. English and Persian are both first-class citizens, with complete right-to-left design throughout. Security tools should not require you to think in someone else’s language.
The full cryptographic design — algorithms, key flows, trust boundaries, and the remediation log from adversarial review — is documented in detail and available on request. We would rather be checked than believed.
Principles
Zero-knowledge or nothing
If a feature would require our servers to see plaintext, the feature changes — not the architecture.
Fail loudly, fail closed
Tampered ciphertext refuses to decrypt. Uncertain session checks reject the request. Silent failure is the enemy.
Your exit is a feature
Export encrypted backups anytime. Delete everything without a support ticket. A fortress you cannot leave is a prison.
Verify, then trust
Written security documentation, honest limits, and adversarial review — recorded, not whispered.