Privacy
The short version: this site collects nothing unless you type your email into the sign-up box, and that email is used only to tell you when Keyvalv launches. The Keyvalv extension collects nothing at all; its full policy is below.
What we collect
Your email address, only if you enter it in a "Get notified at launch" box. Nothing is collected from anyone who just reads the page.
Why
To tell you when Keyvalv launches. Nothing else: no other news, no offers from anyone else, no tracking of what you open.
How long
Until you ask us to remove it. Every email we send carries a delete link, and one press on the page it opens removes your address at once.
How to delete it now
Write to hello@keyvalv.com from the address you used to sign up, or reply to any of our emails, and we delete it by hand. The delete link at the bottom of every email we send does the same with one press.
Cookies and third parties
This site sets no cookies and loads nothing from anyone else: no analytics, no fonts, no scripts from other companies. The providers that run our sign-up (hosting and database) process your address only on our instructions, and we never share or sell it.
Privacy policy for the Keyvalv extension
What the extension collects: nothing. It has no analytics, no crash reporting, no accounts and no servers of ours. It never sends anything to Keyvalv or Freshlogik IT AB.
Where your data is. Your vault is one encrypted KeePass file in the folder you chose on your computer. If that folder is one your own sync app keeps in step (iCloud Drive, Google Drive for desktop, Dropbox, OneDrive, Syncthing or any other), that app copies the file to your cloud and your other devices under its own terms; Keyvalv has no part in that. The file is encrypted on your device with a key derived from your master password before it is written anywhere. A trial vault ("Just try it") is encrypted the same way and kept only in this browser: its file in the browser's memory, and the versions of it listed below, which open it again after the browser restarts, until you keep it in a folder, or forget it. Keyvalv's own bookkeeping (the signed history of changes, whose records name an item by an id and its kind rather than by its name or site, as they have since 26 September 2026, the list of trusted devices, a new device's request to join with a proof of the one-time code typed on it but never the code, the wrapped recovery data, with the emergency sheet's own signing key locked under its code) is inside that same file. The code a trusted device shows for adding another is kept only in its memory, for ten minutes at most. An item you delete waits in that file, under Recently deleted, until you delete it for good; older copies of the file (the versions this browser keeps, your sync app's file history) may still hold it for a while after that. On your computer the extension keeps: where the vault is, a random per-install value, your device's signing key encrypted under a key that is kept inside your vault file (so it opens only for someone who can open the vault), the last five versions of your encrypted vault file (the newest opens your vault when your storage cannot be reached, and an older one can be restored), the sites you told it never to offer on and those you hid its key on, the payment providers you chose to always fill cards for (their web addresses), when this browser was set up and when your emergency sheet last passed a test here, so it can remind you once to test it (dates only, never the code), which notices that your emergency sheet approved a browser you have answered here (a record's hash, never a name), and the date of an older sheet it asked once to replace, when your vault was last saved to your storage, how many changes wait on this browser for it and since when, and when you last downloaded a backup here and how far into your vault's history it went (times and counts, never what the changes are), what the last check of your vault file found and when (a word such as "same" or "tamper", for the problem report below), and your settings. Only if you turn on unlocking with Touch ID, Windows Hello or a fingerprint security key, it also keeps your master password encrypted under a key that only that check on this computer can give, the id of the key your computer made for Keyvalv, where your computer said that key is kept (on this computer, on a security key, or with a passkey manager that may sync it), and when you last typed your master password (below). After you copy a password or a one-time code (Keyvalv copies a login's code itself when it fills that login on a secure page, unless you turn that off in settings) it also keeps a note of when the clipboard is to be cleared (a time, never what you copied), so the clear still happens if the browser closes first; the note goes once the clipboard is cleared. While your vault is open, an item you were adding or editing in the toolbar popup when it closed, what you typed included, is held in the browser's memory with your open vault for ten minutes, so the popup opens on it again; it is never written to disk, and it goes sooner when Keyvalv locks or when you save, cancel or discard it. The last ten passwords the popup made for you and you copied or used are held the same way, in memory with your open vault, so you can find one again under "Recently made"; they are never written to disk, and they go when Keyvalv locks or when you clear them. A browser that used an earlier test version of Keyvalv with Google Drive also still holds that version's Google sign-in, encrypted under the master password of then, until you choose your vault file again or forget the vault on this browser; removing Keyvalv's access in your Google account ends it at Google too.
Who the extension talks to. Nobody. The extension makes no network requests at all: it reads and writes your vault file where it is on your computer, and asks for no permission to reach any server. Links you follow from Keyvalv, such as a saved login's site or the email address for a problem report, are ordinary links you choose to open.
Sign-in pages. The extension looks at the sign-in forms of pages you visit to place its key control, from field types and names. When you sign in, or choose "Save the login typed here" in Keyvalv's list, it reads the username and password you typed only to ask whether to save them in your vault; they stay on your device, held in memory for at most two minutes, and are dropped if you say no. When you sign up with a password Keyvalv suggested in that form, it saves that login in your vault at once, with the username you typed there, and says so with an Undo; nothing waits in memory. When you change a password to one Keyvalv suggested in that form, and the current password you typed is that of one saved login, it updates that login at once and says so with an Undo; for those two minutes the old password is kept in Keyvalv's memory, with your open vault, so Undo can put it back, and it stays in the login's history either way. You can turn this off in settings, under Advanced. That holds while Keyvalv is locked too: it keeps them for those two minutes without opening your vault, so it can offer to save them once you unlock it, and drops them if your computer locks first. If saving itself has to wait because Keyvalv is not taking changes for now (until you accept changes made in another app, say), they are held two minutes more from then, once. The page says so once per site; to know which sites it has said it on, Keyvalv keeps their names in the browser's memory until the browser closes. When you change a password on a site, it also reads the current password you typed there, only to find which of your saved logins to update; it is compared on your device and not kept. A strong password you ask Keyvalv to suggest on a sign-up or change-password form is saved in your encrypted vault as soon as it is filled in, marked as not confirmed until you save the login or delete it; nothing about the page but its address goes with it. You can turn this off in settings. While a tab shows a page with a sign-in form, the extension remembers that page's address in the browser's memory, so its toolbar button can show that page's logins; it forgets it when the tab loads another page or closes. When the sign-in form sits in a frame of the page's own site, it remembers the frame's address instead, and asks the page around it for its address each time it uses it, only to check both are the same site; it keeps no record of that answer. If you keep Keyvalv open in a window of its own, that window notices when you move to another tab or window, or the page in front finishes loading, only to ask again which of your logins fit the page in front; it learns no address or title from that, and keeps no record of it. When the popup or that window is open while Keyvalv is unlocked, it also asks the page in front whether it has a card or address form, only to list your cards or addresses first; the page says only which kinds of form it has, and Keyvalv keeps no record of it. After it fills a login in a tab, or opens a login's site from its details in Keyvalv, it remembers which login and which site for that tab, also in the browser's memory, for five minutes, so the next page of the same sign-in, or the site's own sign-in page, offers that login first. It forgets it sooner when the tab closes, the vault locks, or the tab shows a sign-in form on another site; a page without one does not tell it the tab has moved on. It is used only on the site where you filled that login. On a sign-in that asks for your username on one page and your password on the next, the username you typed on the first page is held in memory for that tab and site for at most five minutes, so the offer on the next page names it; locking Keyvalv or closing the tab drops it. It sends nothing about any page anywhere. Logins are offered only on the websites saved with them, by the site's own domain, and filled only when you pick one. To list the login you used last first, it counts which saved login you filled or copied most recently; that count is kept in memory only, never written anywhere, and gone when the browser closes. While Keyvalv is unlocked it also keeps, in the browser's memory, how many times each site's pages saved something in your vault and when each site's pages and Keyvalv's own pages last used it (site names, numbers and times, never what was saved), because a site's pages may save only a few times before the save is left to Keyvalv's toolbar button, and cannot keep Keyvalv unlocked on their own; locking Keyvalv forgets both.
Checkout and address forms. The extension looks at the payment and address forms of pages you visit to place its key control, from field types and names. Only on secure (https) pages, and only when you pick a card or an identity in its list or click "Fill in page" in the toolbar, it fills that one item into the form's visible fields: a card's number, name and expiry, its security code only when you press for it too, and never a PIN; an identity's name, company, email, phone and address, never a personal or passport number. When a page's list shows your cards or identities, the extension remembers which ones it listed there (their ids, never what they hold) in the browser's memory for ten minutes, or until the tab loads another page or Keyvalv locks, so a pick can only fill one it listed there, and only one per list. It also remembers, in the browser's memory until Keyvalv locks, which cards and identities each site's lists have filled (their ids and the site's name), since one site's lists fill three different cards and three identities at most while Keyvalv stays unlocked; "Fill in page" in the toolbar fills any other. When the card fields sit in a payment provider's frame from another site, Keyvalv asks first; if you choose "Always", it keeps that provider's web address on this browser until you remove it in settings, and "Allow once" is remembered in memory for that page only. After you pay with a card you typed yourself into the shop's own page (not into a payment provider's frame, which Keyvalv does not offer for saving), the card's number, name and expiry are read only to ask whether to save the card in your vault; they stay on your device, held in memory with your open vault for at most two minutes, and are dropped if you say no, never with its security code. Nothing is offered while Keyvalv is locked, or on sites you told it never to offer saving on. You can turn this off in settings.
Whether your computer is in use. To lock your vault when your computer locks or sleeps, and, if you choose it in settings, when your computer has had no typing or mouse movement for 5, 15 or 30 minutes, the extension asks the browser whether the computer is in use. The browser answers only active, idle or locked, never what you typed, where or in which app, and the extension keeps no record of it.
Unlocking with your fingerprint. Off unless you turn it on in settings. So that Keyvalv can offer it once typing your master password has become a chore, it counts on this browser how many times you typed it to unlock in the last seven days, and keeps when you last answered that offer: numbers and times only, never sent anywhere. Your computer checks your fingerprint, face or security key itself; Keyvalv never sees it, only a key your computer gives it after the check, which it uses to open the encrypted copy of your master password in memory and never stores, and your computer's answer saying whether it checked you. Without that answer, Keyvalv opens nothing. That copy stays in this browser and is never sent anywhere; your vault file is unchanged and still opens only with your master password. The key itself is kept where your computer puts it. On a Mac that may be iCloud Keychain or the password manager the Mac uses for passkeys, which saves it as a passkey for Keyvalv and may copy it to your other devices under its own terms; Keyvalv has no part in that, and settings say where the key is kept. Such a copy opens nothing without the encrypted copy of your master password, which stays in this browser. On this computer, anyone who can pass the check can then open your vault here, and the computer's own password or PIN works in its place, so choose this only if you trust that. Keyvalv asks for your master password every 14 days. Turning it off, changing your master password in Keyvalv's settings or forgetting the vault on this browser deletes the encrypted copy and tells your computer the key is no longer used. Keyvalv also deletes the copy when it stops working: when your master password was changed in another app, say, or you set up another vault here. Your computer is not told then, so the key it made for Keyvalv may stay in its list of passkeys; you can remove it there.
Passkeys. When a site asks your browser to create or use a passkey, Keyvalv asks you first. A request that does not follow a click or key press of yours on the page, such as one a site makes as its sign-in page loads or right after you sign in with a password, Keyvalv answers only while it is unlocked and keeps a passkey for that site, or, to make one, keeps none for it yet; any other such request goes to your browser's own passkey window, as does one you say no to straight away in Keyvalv's window. Past that, the request stays with Keyvalv: the passkey is saved in your vault or used from it, or Keyvalv's window says why not; it goes to your browser only if you choose another device. A passkey you save is kept in your vault, like a password, and is only ever used for the site that made it. When a site asks Keyvalv to check it is you, Keyvalv counts that as done only if you typed your master password, or unlocked Keyvalv with your fingerprint and your computer said it checked you, in the last 15 minutes. Keyvalv keeps that time in memory only, until it locks. After that, Keyvalv's window says so and offers to lock Keyvalv so you can unlock it again; it never asks for your master password on the page. You can always choose another device instead.
Importing. An export from another password manager, or a KeePass file, that you choose in settings is read on your computer and never sent anywhere. An export is read in the settings page's memory, and only the logins in it go into your encrypted vault. A KeePass file is opened only in the extension's own memory, with that file's master password and its key file if it has one: Keyvalv uses them once, to open that file, and does not keep them, and neither the file, its password nor its key file is written anywhere. The items you import become part of your encrypted vault. When the file is a copy of your own vault, Keyvalv imports nothing from it: it holds the opened copy in memory for at most ten minutes, so you can merge it, and drops it sooner when you merge, choose another file or Keyvalv locks.
Your master password is never sent to us or stored in readable form. A copy of it, locked with the code on the emergency sheet you print at setup, travels inside your vault file, so the sheet can open your vault if you forget the password. Nobody, including us, can reset it; the sheet is the only way back in.
Reporting a problem. Nothing is sent to us automatically, so if something goes wrong, "Copy a problem report", under Help in settings, copies a short report for you to email us if you choose. It holds codes and counts only: the versions of Keyvalv and your browser, your computer's operating system, where your vault is kept (a folder, or only this browser for a trial vault), what the last check of your vault file found, the last error your storage gave (which Keyvalv keeps in memory until the browser closes), why changes are off if they are, your vault file's format, and how many items and devices your vault has. It never holds a name, a web address, a username, a password or your file's name. The page shows it exactly as copied; it goes nowhere unless you send it.
Removing everything. Removing the extension, or choosing "Forget the vault on this browser" in its settings, removes everything it kept on this browser: your device's key, which vault you use and its history, the versions of your encrypted vault file, the saved link to your vault file if you keep it in a folder, the sites you told it never to offer on or hid its key on, the payment providers you allowed, when your vault was last saved and when you last downloaded a backup, the result of its last check of your vault file, the encrypted copy of your master password a fingerprint unlock opens, the count of typed unlocks it is offered after, your settings and the per-install value. Either way, your vault file stays where it is, yours, and opens in KeePass apps that read KDBX 4, such as KeePassXC; a trial vault, which has no file anywhere else, is deleted with the rest.
Who is responsible. Freshlogik IT AB, Sweden. Questions to hello@keyvalv.com.
Who is responsible
Freshlogik IT AB, Sweden, is the data controller. You can ask what we hold about you, or ask for it to be deleted, at hello@keyvalv.com. If you are in the EU or EEA you can also complain to your data protection authority.