Security and encryption architecture
MYKEYNEST is a web password manager. It combines encrypted password storage with account authentication and access controls for shared credentials. This page describes the current design so you can assess whether it fits your requirements.
AES-256-GCM encryption on the server
Stored passwords are encrypted before database persistence using AES-256-GCM. Encryption uses a random initialization vector and an authentication tag to detect changes to the encrypted value. An account-specific secret is combined with an application secret to derive the encryption key.
The server can decrypt passwords in an authorized operation. MYKEYNEST does not currently use end-to-end, zero-knowledge vault encryption.
Account protection and recovery
Use a long, unique account password, enable the two-factor authentication available in your settings, and review active sessions and trusted devices. The official password reset flow uses an email link. Account recovery and vault encryption are separate mechanisms; resetting the sign-in password does not turn server-side encryption into zero-knowledge encryption.
Sharing and browser autofill
Sharing permissions distinguish use, password reveal and editing. When reveal is disabled, the recipient does not have a reveal action in the interface, while the extension can fill an authorized sign-in form. The browser and target website still process the password. This permission does not guarantee that a person controlling the browser cannot recover it.
Revoking a share removes access through MYKEYNEST. It does not close a session already opened on the target service or invalidate a password previously obtained. During offboarding, also revoke the target service sessions and rotate shared passwords where needed.
Choosing the appropriate level of protection
A password manager does not replace endpoint protection, named accounts, service-specific permissions or your compliance assessment. If your policy requires a provider that cannot decrypt the vault, assess an end-to-end encrypted alternative. This page describes implementation choices; it does not assert an independent security certification or a regulatory compliance guarantee.