Why trust us
Why you can trust KeyValt with your passwords
We are asking you to store your most important logins with us. You deserve to know exactly how we protect them, what we can see, what we can not, and where the limits are. Here it is, in plain English.
The short version
- Your vault is locked on your device before it is sent to us. We store scrambled data that we have no key to open.
- Your master password never leaves your device. Not when you sign up, not when you sign in.
- Nobody at KeyValt can read your passwords, notes, cards, documents or secrets. Not support, not admins, not engineers.
- We tell you exactly what we can see (a small amount of account and usage information) and what we cannot.
- We are honest about what no password manager can protect you from.
The rest of this page explains how all of that works.
How your vault is locked and unlocked
Think of your vault as a safe inside a safe.
1. Your master password becomes a key
When you type your master password, your device runs it through Argon2id. Argon2id is a "password stretching" method, designed to be slow and to need a lot of memory (we use 64 MB of memory and 3 passes). For you, that is a moment's pause when unlocking. For someone trying billions of guesses, it makes each guess expensive. On older browsers that can't run Argon2id, we fall back to PBKDF2-SHA-256 with 600,000 rounds.
The result is your master key. It exists only in your device's memory while you use KeyValt.
2. One key is split into two jobs
From the master key, your device creates two separate keys using a standard method called HKDF (SHA-256):
- an encryption key, which unlocks your vault key, and
- a sign-in proof, which is sent to us so we can check it's really you.
Because these are mathematically separate, the sign-in proof we receive can't be turned back into your encryption key. On our side, we don't even store the sign-in proof as-is. We hash it again with scrypt and a unique salt, so a copy of our database wouldn't let anyone sign in as you.
3. Your vault key unlocks your items
When you create your account, your device generates a random 256-bit vault key. This is the key that actually protects your data. It is stored with us only in locked form, locked by the encryption key from step 2.
4. Every item has its own key
Every login, note, card and document gets its own random item key, and each item is encrypted with AES-256-GCM, the same encryption standard used by banks and governments. AES-GCM also detects tampering: if even one character of the scrambled data were changed, decryption would fail instead of showing you wrong data.
We also "label" each piece of encrypted data with what it belongs to (for example, "this is the data for item X of type login"). If someone with access to our servers tried to swap one item's data with another's, your device would refuse to open it.
5. Unlocking happens only on your device
When you unlock, your device downloads the scrambled vault, uses your master password to rebuild the keys, and decrypts your items in memory. When you lock KeyValt, close the browser or step away long enough for auto-lock, those keys are wiped from memory.
All of this uses your browser's built-in Web Crypto features, not home-made encryption.
Sharing with your team
On the Business plan, every member has their own RSA-3072 key pair. When you share a collection with someone, the collection's key is locked with their public key, so only their device can unlock it. Our servers pass these locked keys around, but can't open them. Owners can compare key fingerprints to confirm that new members are who they say they are.
Use-only access lets a team member fill a login without the KeyValt apps showing, copying or exporting the password. This is a control inside our apps, not encryption: their device still holds the key so it can fill. A determined technical person could extract a password once it's filled into a web page. When someone leaves, change the passwords they used.
Secure Documents
Files are encrypted in your browser before upload. Each file is split into chunks of up to 8 MB, and each chunk is encrypted with AES-256-GCM using a key that only your vault can unlock. The encrypted chunks are uploaded straight to private cloud storage. We see the file's encrypted size, not its name or contents.
Secure Handoff
When you send a Secure Handoff, the bundle is sealed in your browser. The key either goes in the part of the link after "#" (browsers never send that part to any server), or is locked with a password you choose, using Argon2id. We store only the sealed bundle and the rules you set: expiry time, number of opens and an optional access code (which we store only as a keyed hash). After 10 wrong access codes, the link is revoked automatically.
Browser extension and autofill
- The extension fills a login only when the page's real address, as reported by your browser, exactly matches a website saved with that login. Subdomains only match if you allow them.
- The list of allowed websites is stored inside the encrypted item, so nobody can change where your password goes by editing our database.
- It never fills hidden fields, never fills on plain HTTP and warns you about look-alike addresses.
- It never bypasses CAPTCHAs or reads SMS OTPs.
- Ready-made settings for known portals are digitally signed (ECDSA P-256) and checked by the extension before use. They can describe how to fill a page, never where to send your data.
- While unlocked, keys live only in the browser's temporary session memory and are cleared when it locks.
What is encrypted, and what is not
We believe you should know exactly what we can and can't see.
End-to-end encrypted (we can't read it)
| Feature | What's encrypted |
|---|---|
| Logins and portals | Portal names, website addresses, allowed websites, usernames, passwords, authenticator (2FA) secrets, notes, custom fields |
| Organisation | Your labels and categories |
| Notebook | Your notes, including formatting |
| Cards and wallet | Card numbers, CVV, UPI details, notes |
| Developer tools | Projects, secrets, environment files, API keys, client records |
| Life vault | Life records, renewals, subscriptions, purchases, devices and recovery plans |
| Secure Documents | File contents and file names |
| Secure Handoff | Everything inside the bundle |
| Sharing | Collection keys and your private key |
| Settings | Your vault preferences |
Visible to us (needed to run the service)
| What | Why we need it |
|---|---|
| Your email address and name | To create your account, sign you in and contact you |
| Plan, invoices and billing contact details | To bill you. Card and UPI payments are handled by our payment partner; we never see your card number |
| Type of each item, how many you have, and when they were created or changed | To sync your vault between devices and apply plan limits |
| Favourites and which public-directory portal an item came from | For dashboard features like favourites and portal icons |
| Encrypted size of your documents | To apply storage limits |
| Device names, browser, IP address and sign-in times | To keep your account secure and show you your devices |
| Reminder label and date (only if you turn on email reminders) | So we can email you on time even when you're not using the app |
| Secure Handoff expiry and open counts | To enforce the limits you set |
| Support messages you send us | To help you |
| Security and audit logs | To detect abuse and investigate problems. These never contain your secrets |
Your KeyValt account's own two-step sign-in secret is stored on our server, encrypted with a separate server key. This one has to be readable by our server, because the server is what checks your sign-in code.
Things we will never do
- Ask for your master password, recovery key or any of your passwords. Not by email, not by phone, not in support chat.
- Offer a "reset" that keeps your data without your recovery key. That would be a back door.
- Sell your data or show you ads.
- Bypass CAPTCHAs or OTPs on the websites you use.
How we protect the service itself
- All connections use HTTPS with HSTS.
- A strict content security policy limits what code can run on our pages.
- Sessions use random tokens in secure, HTTP-only cookies and expire when idle.
- Sign-in, recovery and pairing are rate-limited, with alerts for new devices.
- Staff use a separate admin sign-in that always requires two-step verification, and every admin action is logged.
- Staff permissions follow "least privilege": people only get the access their job needs, and none of that access includes your vault.
The honest limits
No security product is perfect, and we'd rather tell you than surprise you.
- A weak master password weakens everything. If someone stole our database, they'd still have to guess your master password. A long, unique one makes that impractical. A short one doesn't.
- If your device has malware, such as a keylogger or a malicious browser extension, it can see what you see. Keep your device and browser updated.
- The web app is delivered by our servers. Like every web-based password manager, you trust that we serve you the genuine code. We protect our build and deployment pipeline carefully, and the browser extension is installed from the official browser stores.
- Some information is visible to us, as listed above, such as how many items you have and when they changed.
- If you lose both your master password and recovery key, nobody can recover your vault, including us.
Found a problem?
If you believe you've found a security issue, please tell us. Read our vulnerability disclosure policy or email team@keyvalt.com. For the more technical details, see our security overview.