No data ever leaves your device. The KinshipVault extension has no servers, no analytics, no telemetry, and makes no network requests. It communicates only with the locally installed KinshipVault app on
the same machine, over the browser's native-messaging channel.

What it does with your data
• Fill: reads the current page's hostname to find matching logins. Your passwords and one-time codes are decrypted inside the KinshipVault app, behind Face ID / Touch ID / device passcode, only when you
pick a login. The extension's JavaScript never receives your master key or the vault.
• Save: when you submit a login the vault didn't fill, it offers to save it. A saved login is staged inside the app for your review (encrypted at rest) and is never added to your vault without your
explicit confirmation.
• Generate: creates a strong password locally on request.

Permissions
• nativeMessaging — the only way to talk to the local KinshipVault app, where all decryption happens.
• activeTab — read the active tab's site (in the popup) to show logins for the page you're on.
• Host access (http/https) — a password manager must detect login fields on any site you choose to fill. The content script runs only to find login fields and offer fill/save; it sends only the page
hostname to the app, never page content. Fill/save UI is suppressed in cross-origin iframes.

The extension requests no tabs, storage, scripting, webRequest, history, cookies, or clipboard-read permissions, and stores nothing itself. All credentials live in the KinshipVault app's encrypted,
device-only vault.