Security

How 2keevo keeps your vault private

End-to-end encryption means your vault is locked on your device with a key only you hold. Here is exactly how it works, and what we can and can't see.

In one paragraph

2keevo is a zero-knowledge, end-to-end encrypted password manager. Your master password turns into keys on your own device. Every item is encrypted there before it is sent, and only people you share with can decrypt it. Our servers store encrypted data and the information needed to run your account, never your master password or the keys that open your vault.

Your master password

When you sign in, your browser runs your master password through Argon2id (64 MiB of memory, 3 passes), a slow, memory-hard key derivation function built to make guessing expensive. From the result it makes two separate keys: a master key that stays on your device, and a sign-in key, made from it with HKDF, that is sent to us to prove it's you. We store only a slow hash of the sign-in key.

So the server never receives your master password, and the sign-in key it does receive can't be used to decrypt anything.

Because we never have your master password, we can't reset it. When you set up encryption you get a recovery key; keep it somewhere safe. With it you can set a new master password; without it, nobody can open your vault, including us.

How items are encrypted

Your account has a random 256-bit user key, kept encrypted with your master key. Each item gets its own random key, and its contents (title, fields, notes, tags, passkeys, authenticator secrets) are encrypted with AES-256-GCM, which also detects any tampering.

Every encrypted piece is bound to what it belongs to, so the server can't swap one item's data or key for another's without the decryption failing.

File attachments are encrypted the same way, in chunks, in your browser. Their names are encrypted too. Collection names are encrypted with the collection's key.

Every save keeps an encrypted previous version, so version history works without the server reading anything.

How sharing works without us seeing anything

Each account has an X25519 key pair. The public key is stored on the server; the private key is encrypted with your user key.

To share an item, your browser seals the item's key to the other person's public key. Only their private key can open it. You can compare a key fingerprint with them to be sure the server didn't substitute a key.

Collections have their own key, sealed to each member who may open them. When someone loses access, the collection key is replaced in the browser of someone who manages the collection, so later items can't be read with the old key.

One-time secret links put the decryption key in the part of the link after the # sign, which browsers never send to a server. An optional passphrase is mixed into the key, so the link alone isn't enough.

What the server can see

Can't see: item titles, usernames, passwords, URLs, notes, tags, passkeys, authenticator secrets, attachments and their names, collection names, your master password, your keys.

Can see: your email address, who you share with and with what access, company membership and group names, item types and sizes, timestamps, and security events such as sign-ins (with IP address and browser). The privacy policy lists everything.

The browser extension sends the address of the site you're on to find matching logins; it matches them against your decrypted items on your device.

Protecting your account

Two-factor sign-in with an authenticator app, and passkeys (Face ID, Touch ID, Windows Hello, security keys), on every plan.

An email when your account signs in from a new device.

Sessions in httpOnly cookies that page scripts can't read, short-lived access tokens, and rate-limited sign-in.

The web app signs you out after 12 hours without use (the browser extension after 7 days; it locks on its own timer). If an old sign-in token is ever used again, that sign-in ends and it shows in your activity log. Signing out in one tab signs out every open tab.

Auto-lock after the idle time you choose, separately for the vault and the extension, and when your screen locks. Locking forgets the open keys.

Copied authenticator codes are cleared from the clipboard after 30 seconds.

An activity log of reveals, copies, downloads, shares and sign-ins, without item titles.

For companies

New companies require two-factor sign-in (an authenticator app or a passkey) by default. A member without it can't open company items and gets no company vault keys until they set it up.

Company policies also set a minimum password length, cap auto-lock, and sign members in again after a set time.

Being an owner or admin doesn't open company vaults. Like everyone, they need access to a vault, and each vault has managers who share it. An admin who gives themselves access is logged, and the vault's managers are told.

Owners and admins see an activity log for company items. Removing a member ends their company access and triggers key replacement.

Companies can turn on vault recovery, so a vault isn't lost when the people who could open it leave. Company vault keys are then also sealed to a recovery key held by at least two people the company names. Using it takes a request, a second person's approval and a waiting period, and everyone involved is told. It never reaches anyone's personal vault, and the server can't use it on its own.

Infrastructure

Everything is served over HTTPS. Nightly backups are encrypted and kept for 30 days.

Password breach checks use Have I Been Pwned's k-anonymity range search: your browser sends only the first 5 characters of a password's hash, and compares the results itself.

Reporting a security issue

Found something? Email security@2keevo.com with the details and give us time to fix it before telling others. We won't take action against good-faith research. Our disclosure policy (2keevo.com/security/disclosure) says what we promise in return and what's in scope.

Create a free vault