Keyvalv Get notified at launch

Security

What Keyvalv protects against, what it cannot, and what it writes.

What Keyvalv protects against

What it catches, and what it cannot

A KeePass file already refuses to open if someone without your master password changes it. What it cannot see is a whole, valid copy that is older than yours, or an edit by someone who has your password. So Keyvalv keeps a signed history inside the file, in KDBX custom data that KeePassXC keeps: each of your computers has its own Ed25519 key and signs every change it makes, each record carries the SHA-256 of the one before, and each computer remembers the newest record it accepted.

  • Refused, with your last good copy kept, on a computer that has opened your vault before: a copy older than the newest record it accepted (a restored backup, or a sync conflict that went the wrong way), a forged or removed history, and a change from a device you never approved.
  • Listed for you to accept: a change made outside your Keyvalv computers, in another KeePass app such as KeePassXC or by anyone else with your password. It is listed item by item, without values, and Keyvalv saves nothing more until you accept it. Meanwhile it fills from the file as it now is.
  • Not caught: on a computer that has never opened your vault, or whose browser data was cleared, Keyvalv has nothing to compare with, so it accepts an old copy, or a vault that someone with your master password made in its place. Nor is anything checked in a file made in another app until you choose Protect.
  • Not prevented: the file being deleted; Keyvalv says it is gone, and your browser keeps the last five versions to put back.

What Keyvalv writes into your file

What it does not protect against

What the extension can see

Chrome warns that Keyvalv can read and change data on all websites, because it has to find sign-in fields wherever you sign in. Nothing from a page leaves your computer: the extension makes no network requests.

Check it yourself

Report a vulnerability

Until launch, write to hello@keyvalv.com (also in security.txt). We aim to reply within a few working days, fix confirmed issues first, and credit you if you wish. Please give us reasonable time to fix a problem before publishing it. Before launch, security@keyvalv.com will take these reports.

Before launch

Before launch we will publish a plain-language and a technical write-up of the design, so anyone can check these claims. Keyvalv is built with an AI coding assistant, which is why an independent audit comes before launch; this page will say when it is done.

Back to keyvalv.com