Privacy Policy — Kutrion Vault browser extension

Kutrion is a credential vault and access broker. The browser extension lets you autofill and capture website logins, and view one-time codes, using a Kutrion server that you or your organization control. This policy explains what the extension handles and how.

What the extension stores on your device

The extension keeps an encrypted copy of your vault on your device, including credential values, so a fill works instantly and without a network round trip. The copy is sealed with a key Kutrion issues, which carries a lifetime and which your server or your administrator can withdraw at any time; once it is withdrawn or lapses, the copy is erased on the device's next sync. The keys that open it are held in browser session memory only and are destroyed when the browser closes, so the stored copy is inert until you unlock again.

Alongside it the extension stores what it needs to reach your server: the server URL, a device-session reference (a refresh token) so you stay signed in, and your local settings such as auto-lock.

Some credentials are deliberately kept out of the local copy and are fetched from your server each time they are used. Your organization can also switch local copies off entirely, which puts every fill back on that path.

This is not zero-knowledge, and Kutrion does not claim to be: your server can decrypt secrets for an authorized session. What the design gives you is accountability — every reveal is recorded, including one served from the local copy, which is written to a sealed, tamper-evident log on the device and handed to your server on its next sync.

Unlocking, and what the unlock protects

Biometric unlock — fingerprint, face, or a device PIN — is a local gate. It is checked on your device; nothing is registered with or verified by your Kutrion server, and it carries no secret. It stops someone who sits down at your unlocked browser and opens the extension. It is not what protects a stolen browser profile: that is the job of the device session itself, which your server can revoke per device and which is refused if an old token is replayed. Biometric unlock is optional, and signing in with your password always works. Offline, unlock is your account password rather than a biometric — a browser extension has no keychain to hold the copy's key behind a fingerprint.

The extension locks itself after a period of inactivity, which you choose in its settings. Locking destroys the keys held in session memory, so the stored copy cannot be opened again until you unlock.

What data the extension handles, and why

• Authentication information — your Kutrion sign-in, used only to authenticate you to your own server.
• Website content — the URL of the active tab and login form fields, used only to match, fill, or capture a login when you explicitly choose to.
• Login submissions — on sites where you have granted access, the extension observes that a sign-in request was submitted and completed, so it can offer to save or update that credential. It observes only that the submission happened: it does not read the contents of the request, does not modify or block any request, and does not record your browsing history.

Where your data goes

The extension communicates only with the Kutrion server you configure. It does not send your data to any third party, does not sell or share it, and contains no advertising or tracking analytics. Every credential reveal and fill is audited on your Kutrion server.

Site matching

Logins are matched to a site by exact host or subdomain only. The extension does not fill across unrelated domains, which helps resist look-alike phishing pages.

Data retention and deletion

Signing out or removing the extension erases everything it holds on the device: the encrypted vault copy and its keys, the reveal log, the server URL, the session reference and your settings. Your administrator can also erase the copy remotely by withdrawing the device's key, and the device wipes it the next time it reaches your server. Credentials themselves live on your Kutrion server and are governed by that server's retention and your administrator's policies.

Limited use of data

Kutrion's use and transfer of information received from the browser extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Specifically: data is used only to provide the autofill, capture, one-time-code and passkey features described above; it is never sold or transferred to third parties; it is never used for advertising, re-targeting, or to determine creditworthiness or for lending purposes; and it is never read by a human, except with your explicit consent, to resolve a specific support request you have raised, or where required by law.

Contact

Questions about this policy or your data: our contact page.