Fill Passwords in Your Browser, Without Sending Them to the Cloud

Most of us live in the browser. That is where the logins pile up, where the "your password was found in a breach" banners appear, and where, if we are honest, a lot of us still let the browser itself remember everything. The trouble is that convenience on the web has usually meant a copy of your vault sitting on someone else's server, decrypted in the browser where any extension flaw can reach it.

The Kinship Vault browser extension takes the opposite path. It brings autofill to the web without moving your passwords off your device. The extension is a thin piece of interface; the vault, the keys, and the decryption all stay in the Kinship Vault app on the same machine.

How on-device autofill works

When you land on a sign-in page, the extension notices the login fields and asks one question: are there saved logins for this site? To answer it, the only thing that leaves the page is the site's hostname, for example bank.example.com. The page's contents, what you type, and the vault itself are never handed to the extension.

That hostname goes to the Kinship Vault app through the browser's built-in native-messaging channel, a private pipe between the extension and a companion app on the same computer, not the internet. The app finds matching logins and sends back only what is needed to show you a list: the site, the username, a label. Your password is not in that list.

When you pick a login, the app asks for Face ID or Touch ID, decrypts that one entry, and fills it. The secret is unlocked for a single fill, at the moment you asked for it, and never sits decrypted in the browser.

The extension knows which site you are on. It does not know your passwords. Only the app, behind your face or fingerprint, ever sees those.

Saving a new login, on your terms

When you sign up somewhere or change a password, the extension offers to save it. Rather than silently writing to your vault, a saved login is staged in the app for review, encrypted at rest. The next time you open Kinship Vault, you confirm or discard it. Nothing enters your real vault without a deliberate yes.

Where it works

On your Mac, the extension runs in Chrome, Edge, Brave, Firefox, and Safari, adding one-click fill and save to each.

On iPhone and iPad you may not even need it. Once Kinship Vault is your AutoFill provider, it already fills your logins in every browser and app, Chrome included, unlocked with Face ID or Touch ID. That is the system-wide AutoFill doing the work, so it has always just worked wherever you sign in. The browser extension is the desktop counterpart to that, and on iOS it also comes as a Safari extension. Either way it pairs with the Kinship Vault app on the same device, where your vault already lives, so there is no separate account and no second master password.

Built to ask for as little as possible

A password manager has to be able to see login fields on the sites you visit, so the extension does request access to web pages. What matters is what it does with that access, and what it deliberately does not take. It sends only the page's hostname, never the page content; it suppresses its fill and save prompts inside cross-origin iframes; and it asks for none of the usual heavy permissions, no browsing history, no cookies, no clipboard, no general storage. We wrote more about how to judge that in are browser password extensions safe.

Set it up

You turn the extension on from the Kinship Vault app under Passwords, then add it to your browser. For Chrome, Brave, and Edge you can install it straight from the Chrome Web Store; in Safari it is built into the app. Because everything routes to the app on your device, the same Face ID or Touch ID that unlocks your vault is the only key that fills a password. Full steps are in the browser extension documentation.