Privacy Policy.

Browsevo can store data inside the Chrome profile, including Workspaces, Spaces, Groups, saved-tab URLs and titles, notes and “Why” text, snapshots, Timeline events, Recently Deleted items, snooze state, settings, backup metadata, local search indexes, and Recovery Vault data.

Local backup verification, migration checks, recovery fingerprints, integrity repair, and Recovery Vault operations use local browser storage and local Web Crypto. They are not uploaded merely because those checks run.

Google sign-in is optional. When used, Browsevo can store the connected account's email address, display name, profile-picture URL, Google subject identifier, connection method, and sign-in time in extension storage.

Browsevo does not store the user's Google password. OAuth authorization is handled through Chrome/Google. A custom Browsevo Display Name and avatar can be stored for use in Chat, Tasks, Members, and Collaboration identity.

Browsevo is fully usable without signing in. Google sign-in requests limited Google Drive app-data access and turns on cross-device Workspace sync by default after Google consent, unless sync has been disabled for that account. This initial merge is designed to preserve both local and remote Workspaces. Cross-device sync can be disabled in Settings. Full daily cloud backup remains a separate opt-in setting.

Cloud backup can contain the same categories of data included in a full portable backup. Device sync is narrower and is used to synchronize supported Workspace/Space state. The UI identifies these features separately and they can be disabled independently.

Browsevo does not treat Google Drive backup or sync as required for local use.

Workspace Collaboration is opt-in and can use Google Drive or Browsevo Cloud.

• With Google Drive, the collaboration document is stored through the selected Google Drive flow.
• With Browsevo Cloud, shared Workspace content is transferred through the Prax9 Cloudflare service and stored in Supabase-backed collaboration storage. Chat and profile functions may also send requests directly from Browsevo to a Supabase Edge Function, while profile information may additionally be processed through Cloudflare.
• Only supported content from Workspaces the user explicitly shares is Collaboration data. General browsing activity, browser sessions, and Timeline data are not Collaboration content unless a feature explicitly says otherwise.
• Collaboration can store participant identifiers, email addresses for authorization/management, roles, profile display names/avatars, shared Workspace content, operational metadata, and audit metadata required to run the collaboration service.

For Browsevo Cloud collaborations, group-chat messages and read markers can be stored in private Supabase-backed cloud collaboration tables. Chat and profile requests are sent directly to a Supabase Edge Function; workspace collaboration requests use Cloudflare. Messages can include the sender's authenticated account identifier, current display identity, message text, client idempotency identifier, and timestamps.

Comments, mentions, tasks, and member records can include collaborator identifiers, roles, timestamps, and supported shared content. Email addresses are used where required for authentication, authorization, invitations, and management; normal Chat/Task presentation uses the collaborator-facing display identity where available.

Universal Search can query Chrome browsing history locally when the user searches. Browser-history results are not uploaded to Browsevo Cloud merely because they appear in search.

If the user has already granted the relevant Google Drive permission, Drive metadata search can query file metadata directly from Google as part of that explicit integration.

Browsevo offers Chrome Built-in AI where supported. Chrome Built-in AI processes its supported requests locally. External Gemini AI is an optional, separately authorized feature that uses an API key supplied by the user; Browsevo does not provide or fund a shared Gemini API key.

Before enabling external Gemini AI, the user must enter their own Gemini API key, review the data-transfer disclosure, and explicitly authorize a separate Google Cloud verification step. The optional verification requests the read-only OAuth scopes https://www.googleapis.com/auth/cloud-platform.read-only and https://www.googleapis.com/auth/cloud-billing.readonly from the user who chooses this feature. These scopes are not requested during ordinary Browsevo sign-in or use of local Workspaces.

Browsevo checks the user's Google identity and permissions, resolves the project associated with the exact supplied API key using Google API Keys, and checks that project's billing status using Google Cloud Resource Manager and Cloud Billing. Verification sends the identity, API key, project identifiers and related authorization metadata needed for these checks to Google; it does not send browsing content, saved Workspace content, or AI prompts as part of the verification step. The verifier requires successful authorization, a matching key and project, and active project billing. A user's own statement or checkbox about having a paid account is not treated as proof of billing eligibility; successful verification is required before Browsevo sends content to the external Gemini API.

Before each external Gemini content request, including a retry, Browsevo rechecks eligibility. If verification is unsuccessful, expires, is revoked, or no longer matches the current account or key, the extension blocks the external Gemini content request. Verification state is held temporarily in memory; the user-supplied API key is held in Chrome session storage. A successful check reflects the state at the time it is made and cannot guarantee that Google Cloud billing, access or quota will not change afterward.

When the user invokes an authorized Gemini feature, the selected prompt, relevant page excerpts, titles, URLs, and other content necessary for that specific request may be sent directly from the user's browser to Google's Gemini API using the user's own API key. Chrome Built-in AI remains independent of this external verification. API requests may use store:false where supported, but this setting does not override Google's contractual processing, security, retention or legal requirements.

Google's terms distinguish processing for paid Gemini API services from unpaid services; unpaid input or output may be used to improve Google services, including possible human review, subject to Google's applicable terms. The verification feature is designed to limit external content transfers to billing-enabled projects, but does not independently guarantee Google's processing practices. Users should avoid submitting confidential or third-party private information without authorization. Review the Gemini API terms and Gemini billing information.

Gemini API usage charges, where applicable, are billed by Google to the owner of the user's Google Cloud project under the user's own arrangement with Google. Browsevo does not charge those usage fees on behalf of users.

Browsevo diagnostics are intentionally privacy-reduced. The built-in support snapshot contains build/runtime information, permission state, anonymous counts, and non-content settings needed for troubleshooting. It is designed not to include saved-page URLs, page titles, notes, “Why” text, or user-entered domain lists.

Diagnostics are copied or exported only when the user requests that action.

Browsevo does not sell user data. This build does not include an advertising SDK or a third-party product analytics service. We affirm that Browsevo's use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. We do not use or transfer user data for unrelated advertising or creditworthiness or lending purposes.

Data may be transferred to external providers only for the disclosed, user-enabled features, such as Google sign-in, Google Drive sync and backup, Browsevo Cloud collaboration and chat, or explicitly authorized Gemini verification and requests. Google, Cloudflare and Supabase may process technical request information (including IP addresses and operational logs) under their respective service and security practices; their own retention terms and settings apply. Browsevo does not guarantee that external infrastructure logs contain no IP addresses.

Exports are created only when the user requests them. Exported files remain wherever the user saves or shares them and are outside the extension's local database lifecycle.

Imported backup files are parsed and checked locally before supported data is applied. Import preflight and local recovery safeguards run before destructive replacement or merge actions.

Users can delete supported saved items, clear Recently Deleted items, disable cloud features, disconnect Google sign-in, or remove the extension.

Signing out of Browsevo removes the local sign-in connection but does not automatically delete local Workspaces or remote data already stored in Google Drive or an active Collaboration provider. Removing the extension or clearing its extension storage removes the extension's local storage for that Chrome profile; exported files and remote provider data are separate.

If Browsevo changes the categories of data it processes, the providers it uses, or the purposes for which data leaves the local device, this policy and the corresponding Chrome Web Store disclosures should be updated before release.

For questions about this Privacy Policy, or to request access to, correction of, or deletion of personal data associated with Browsevo's optional cloud services, please use our Contact Form.

Information submitted through this form is processed using Google Forms and will be used to review and respond to your request. We may ask you to verify your identity to protect personal data before acting on a request.

Please do not include passwords, API keys, authentication tokens, or other sensitive credentials in your request.