Privacy policy
Vault is a password manager for teams: a Chrome extension and an Android app that work with a Vault server run by your organisation. This page explains what they do with your data. Last updated 13 November 2026.
In short
- Your passwords, email accounts, API keys, cards and notes are encrypted on your own device before they are sent anywhere. Nobody else can read them, not even the server that stores them.
- Vault only talks to your organisation's Vault server. It sends nothing to the makers of Vault, to Google, or to anyone else. There are no analytics, no tracking and no advertising.
- Your data is never sold, and never used for anything except being your password manager.
Who is responsible
Your organisation runs the Vault server you set Vault up with, and decides who has an account. Questions about your account or your data go to your organisation's Vault administrator.
What Vault handles, and where it goes
| Data | Where it goes |
|---|---|
| Passwords, email accounts, API keys, cards and notes, with each entry's name, web address, username and description | Encrypted on your device, separately for each person allowed to read them, and stored encrypted on your organisation's server. Only you and the colleagues you share with can decrypt them. |
| Your private key | Created on your device and protected by your passphrase. Your passphrase never leaves your device. If your organisation uses account recovery, an encrypted backup of your key is kept on the server that only your organisation's recovery key can open (an administrator must approve each recovery). |
| Your account: name, email address, role, the groups you are in | Your organisation's server, which needs them to run your account. |
| Activity: sign-ins, and when a password is viewed, copied, filled, changed or shared, with the time, IP address and browser | Your organisation's server, as an activity log that administrators and the owners of each password can see. It records which entry was used, not the password itself. |
| The structure of your vault: how many entries there are, who can access which, password group names, and when entries were created or changed | Your organisation's server (it needs this to decide who gets which encrypted copy). |
What stays on your device
- Chrome: your passphrase-protected key, your account details, and your settings, in the extension's own storage. While Vault is unlocked, the unlocked key is kept in memory only, and is forgotten when Vault locks or Chrome closes.
- Android: an encrypted copy of your vault so you can use it offline, protected by your key. It is excluded from phone backups.
- Clipboard: when you copy a password, Vault clears it from the clipboard again after 30 seconds. To check that the clipboard still holds it, Vault only compares a fingerprint (hash) of the copied value.
Websites and apps
Vault only looks at web pages and apps to fill in your logins and to offer to save new ones:
- In Chrome, Vault has no access to websites until you turn on in-page autofill, which asks Chrome for permission. It then looks for login fields, offers your matching logins, and offers to save a login you typed. It fills a password only into the website it was saved for (same domain, and never into a plain http page for an https login).
- It does not read, store or send the rest of the page, your browsing history, or what you type elsewhere.
- On Android, Vault answers Android's autofill requests in the same way, only with your matching logins and only when you choose one.
Chrome permissions
| Permission | Why |
|---|---|
| Your Vault server's address | Asked for during setup, to talk to your organisation's server. |
| All websites (optional) | Only if you turn on in-page autofill: to show your logins under login fields and offer to save new ones. |
| Storage, alarms | To keep your protected key and settings, and to lock Vault and clear the clipboard on time. |
| Active tab, scripting | To fill a login into the page you are on, when you choose one. |
| Clipboard read and write, offscreen document | To copy a password when you ask, and clear it again after 30 seconds if it is still there. |
Keeping and deleting data
Your data stays on your organisation's server for as long as your account exists. When an administrator deletes your account, your encrypted copies are deleted with it. Removing the extension or the app deletes what it stored on that device. Ask your administrator about anything else, including the activity log.
Security
Encryption uses OpenPGP (Ed25519 and X25519 keys, AES-256). Connections to the server use HTTPS. How Vault protects your data is described in detail in its security design document, which your administrator can share with you.
Changes
If this policy changes, the new version is published on this page with a new date.