Privacy Policy
Privacy built into the product boundary.
This policy describes the information handled by the Solvin Vault application, browser extension, and this website.
Last updated: August 9, 2026
Website
This static website does not include an account system, advertising, analytics, or a contact form. When you follow an external link, that service's privacy policy applies.
Vault data
Solvin Vault is designed to store encrypted vault data locally and synchronize an encrypted vault bundle through one provider you select: Google Drive, OneDrive, Dropbox, or WebDAV. The selected provider is responsible for processing data under its own terms and policies.
Browser extension
Before pairing, the extension presents a prominent data disclosure and requires your affirmative consent. Until a current consent record exists, it does not activate page or form listeners or process page and form data. After consent, on supported HTTPS and local-loopback pages, it may process authentication information; personally identifiable information such as a name, email address, phone number, address, identity document type or number, and birth date; financial and payment information; one-time codes; website content; form data; and web browsing activity. During matching and filling, the page URL is reduced to the current site origin. The request also includes form action origins and methods, an observed username when present, and an ephemeral form snapshot identifier. Submitted-form capture additionally sends the captured values and may include field locators, while its saved recipe start URL remains the site origin. When you actively choose Record this page, the saved recipe may also include the URL path. Query parameters and fragments are never sent. With a current consent record, an unlocked desktop Vault, and exact-origin checks, one unambiguous login match may fill automatically; otherwise you choose the matching item. Submitted-form data travels through Native Messaging as a pending proposal and is not saved to your encrypted Vault unless you approve it in the desktop app. Chrome storage holds the consent version and acceptance time, a non-secret random client ID, pairing ID, profile label, and up to 20 recent capture-status records containing proposal or item identifiers, state, a status message, and expiration time; it does not hold credential values. Unpairing immediately removes the extension's consent, pairing, profile, and capture-status records and asks the desktop app to revoke its operating-system pairing credential. If the desktop app is unavailable, you can revoke that browser profile later from the desktop app. Approved saved data may synchronize inside the encrypted Vault bundle through the provider you selected.
Chrome Web Store Limited Use
Solvin Vault's use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. Extension data is used only to provide or improve its disclosed password-manager features. It is not sold, used for personalized advertising, or used to determine creditworthiness or for lending. Humans do not read extension data except with your explicit consent for a specific support case or when required for security or by law. Data is transferred only as needed for these user-facing features: through Chrome Native Messaging to your local desktop app and, after you approve saving it, inside the encrypted Vault bundle through the sync provider you selected.
AI-assisted import
AI-assisted import analyzes only the text you explicitly paste. A local model may be used through a loopback endpoint. When you choose a supported remote AI provider, the application asks for separate confirmation before each remote analysis. Review the relevant provider's policy before you confirm.
Local integrations
The CLI and MCP server communicate with the unlocked desktop app through local channels and require explicit approval for secret reads or effects. The browser extension communicates through Chrome Native Messaging: current consent, an unlocked Vault, and exact-origin checks gate filling, while captured saves and updates require desktop approval. The app's approval history is designed to record request metadata, decisions, and time without storing secret values.
Your choices
You control your Vault, selected sync provider, and connected integrations. You can lock the Vault, revoke a paired browser profile, remove configured integrations, or uninstall the extension. For privacy questions, contact the privacy address below.
This policy may change as the product changes. Material updates will be reflected by the date above.