Legal
Privacy Policy
Last updated 2 September 2026
The short version. KeeperPass has no server and no database. There is no KeeperPass account. Your vault is encrypted inside your browser and stored as a single file in your own Google Drive. We cannot read your passwords, because we never receive them and have nowhere to put them. Three third parties do receive something while you use the app — Google, DuckDuckGo, and Have I Been Pwned — and section 6 sets out exactly what each one gets.
1. Who we are
KeeperPass is operated by Vironautics, registered at Sousse, Tunisia. Where this policy says "we" or "us", it means that company. You can reach us about anything in this policy at contact@keeperpass.com.
2. What this policy covers
This policy applies to three things:
- The marketing website at keeperpass.com — the page you are reading now.
- The web app at vault.keeperpass.com.
- The KeeperPass browser extension.
These are not the same in privacy terms, and the differences matter. The marketing website uses analytics. The web app and the extension do not — they contain no analytics, no telemetry, no crash reporting, and no advertising or tracking code of any kind.
3. What we never receive
There is no KeeperPass server that your data passes through, and no KeeperPass database in which anything about you is recorded. In particular, the following never reach us, in any form, encrypted or otherwise:
- Your master secret, or anything derived from it.
- Your vault — its items, names, usernames, passwords, notes, custom fields, tags, TOTP secrets, or attachments.
- The websites you store credentials for, or the sites you visit while the extension is installed.
- Any page content from the sites you browse.
This is a structural property, not a promise about our intentions. We have not built the infrastructure that would let us collect these things, and the source code that runs in your browser can be inspected to confirm it.
4. Signing in with Google
KeeperPass has no password of its own and no registration form. You sign in through Google's own OAuth flow, using Google Identity Services. Two consequences follow.
The permissions we request
KeeperPass asks Google for exactly these scopes, and no others:
| Scope | What it allows |
|---|---|
openid, email, profile | Reads your basic profile — your name, email address, and profile picture — so the app can show who is signed in. |
drive.file | Access limited strictly to files KeeperPass itself creates. It cannot see, list, open, or search any other file in your Drive. This is the narrowest Drive scope Google offers. |
Your profile information is fetched from Google directly by your browser and used only within that browser session, to display your name and to open your own vault file. It is not logged, stored, or transmitted to any KeeperPass-operated system, because none exists.
Your Google access token
The access token Google issues is held in your browser's sessionStorage so that a page refresh does not force you to sign in again. It is deliberately never written to localStorage, which means it is discarded when you close the tab. It is never transmitted to us.
What Google itself learns
Signing in requires your browser to load Google's script from accounts.google.com and to call Google's APIs. Google therefore sees your IP address, your device and browser, and the fact that you are using KeeperPass, and it handles that under its own policies. See Google's Privacy Policy.
5. Your vault in your Google Drive
KeeperPass creates one folder in your Drive, named keeperpass, containing one file, vault.json.enc. That file is your entire vault.
Before it is ever written to Drive, the vault is compressed and then encrypted in your browser:
- Your master secret is put through Argon2id — a memory-hard key derivation function — with a 16-byte random salt, 64 MiB of memory, 3 iterations, and a parallelism of 4. These are the same parameters Bitwarden uses in production.
- The resulting 256-bit key encrypts the vault with AES-256-GCM, using a fresh 12-byte random nonce for every save, so encrypting the same vault twice never produces the same ciphertext.
- The derivation parameters travel alongside the ciphertext, so vaults written under older settings stay readable when those settings are strengthened.
Google stores the encrypted bytes and cannot decrypt them. Neither can we. Your master secret never leaves your device, and no copy of it exists anywhere else.
The vault file lives in your Drive, under your Google account. It counts against your Google storage, it is subject to Google's terms, and you can delete it yourself at any time without involving us.
6. Third parties your browser contacts
While the app has no back end of its own, it does make requests from your browser to three external services. This is the complete list.
| Service | What is sent | When |
|---|---|---|
| Google (sign-in and Drive) |
Your OAuth credentials, your IP address, and the encrypted vault file. | At sign-in, and on every load and save of your vault. |
| DuckDuckGo (website icons) |
The hostname from an item's URL field — for example github.com — so an icon can be fetched for it. The item, its username, and its password are never sent. |
Whenever an item with a URL field is displayed. |
| Have I Been Pwned (breach checking) |
The first five hexadecimal characters of the SHA-1 hash of a password. Never the password, and never the full hash. | Automatically after each unlock, and when an item is created, edited, or restored. |
About the website icons
To show a recognisable icon next to each entry, KeeperPass asks icons.duckduckgo.com for the icon belonging to that entry's web address. The app cannot reach those sites itself, so the alternative is no icons at all.
We want to be direct about the trade-off: this reveals to DuckDuckGo the hostnames of services you hold accounts with — not which account, not your username, and not your password, but the list of sites itself. Requests carry no identifier of you beyond your IP address, and there is currently no setting to turn this off. If that trade-off is not one you want to make, the honest answer today is to run your own build of the app.
About the breach check
KeeperPass checks your stored passwords against the Have I Been Pwned breach corpus. The check runs automatically each time you unlock your vault, and again whenever you add or change an item — it is not something you switch on.
The query is k-anonymous. Your browser computes the SHA-1 hash of a password locally, sends only its first five characters, and receives back every breached hash sharing that prefix — several hundred of them. The comparison happens on your device. Have I Been Pwned therefore cannot tell which password was being asked about, and never sees the password or its full hash. Results are held in memory only and are never written into your vault file.
7. What is stored in your browser
KeeperPass keeps a small amount of state on your device. None of it is transmitted anywhere.
| Key | Where | What it holds |
|---|---|---|
keeperpass:accessToken | Session storage | Your Google access token. Cleared when the tab closes. |
keeperpass:accessTokenExpiry | Session storage | When that token expires. Cleared when the tab closes. |
keeperpass:recentItemIds | Local storage | The identifiers of up to 50 recently opened items, so this device can show a "recently used" list. Identifiers only — no names, no passwords. Kept out of the vault deliberately, so that what you looked at on a shared computer does not follow you to your phone. |
keeperpass:locale | Local storage | Your language choice. |
keeperpass.theme | Local storage | Your light or dark theme choice. |
Clearing your browser's site data removes all of it. Your vault is unaffected, because it lives in your Drive.
8. The browser extension
The extension needs broad permissions to do its job, and you should understand what they mean.
It requests access to all websites and runs a small script on the pages you visit. That script exists to find login forms so that it can fill your credentials into them. It reads the structure of forms on the page — where the username and password fields are — and it communicates only with the extension itself.
The page script makes no network requests whatsoever. It has no ability to transmit anything to us or to anyone else, and page content, form values, and your browsing history are never sent off your device. The only outbound connections the extension makes are to Google, for sign-in and for your vault file.
Removing the extension removes its access immediately. Your vault is unaffected.
9. The marketing website and analytics
This website (keeperpass.com) uses Google Analytics (measurement ID G-G2HHD6E3VL) to understand aggregate traffic — which pages are visited, roughly which country visitors come from, and what kind of device they use. Google Analytics sets cookies in your browser and processes your IP address.
This runs on the marketing site only. It does not run on the web app or in the browser extension, and it has no access to anything vault-related: no vault contents, no items, no passwords, no Google account data. See Google's Privacy Policy for how Google handles what it collects.
10. Where this data goes
The third-party services described above — Google, DuckDuckGo, and Have I Been Pwned — are operated principally from the United States, and handle what they receive under their own privacy policies.
11. How long anything is kept
- Your vault is kept in your Google Drive until you delete it. We hold no copy and cannot delete it for you.
- Browser storage is kept until you clear it, or — for your access token — until you close the tab.
- Analytics data is retained according to the Google Analytics retention setting on our property.
- Emails you send us are kept for as long as needed to deal with the matter, and then deleted.
We hold no user database, so there is nothing else to retain or to purge.
12. Your control over your data, and your responsibility for it
Because we operate no user database, we hold no personal data about you beyond what is described above. Your vault is not ours to produce, correct, or delete — it lives in your own Google Drive, under your own Google account, and you already have full control of it. To export it, use the export feature in the app; to erase it, delete the keeperpass folder from your Drive and revoke KeeperPass's access in your Google account permissions.
Your Google Drive account is yours to secure and maintain. We have no visibility into it, no access to it beyond the narrow drive.file scope described in section 4, and no ability to back it up, recover it, or restore anything from it. If your Google account is lost, suspended, or compromised, if you delete the vault file yourself, or if data is lost through your own action or through Google's handling of your account, that loss is not something we can prevent, reverse, or be held responsible for. See the Terms of Service for how this limits our liability.
To reach us about anything in this policy, write to contact@keeperpass.com.
13. Children
KeeperPass is not directed at children, and we do not knowingly process the data of anyone under 16. Because there is no account system, we hold no age information.
14. Security
The protection of your vault rests on the encryption described in section 5 and on your own master secret. We cannot reset that secret, recover it, or help you regain access if you lose it — see the Terms of Service for what that means in practice.
If you believe you have found a security vulnerability in KeeperPass, please report it to contact@keeperpass.com rather than disclosing it publicly, and we will respond as quickly as we can.
15. Changes to this policy
If this policy changes, the "last updated" date above changes with it. Where a change materially affects how your data is handled, we will make that clear on this page rather than revising it silently.
16. Contact
Questions about this policy, or about anything described in it, can be sent to contact@keeperpass.com.