Verboo Code — Privacy Policy
This privacy policy explains what data the Verboo Code browser extension handles when you use it to control Chrome with a Verboo account session. Plain-English summary first, technical detail below.
Summary
The release OAuth client ID is not configured in this source snapshot, so standalone chat currently fails closed rather than accepting another credential type.
- No data is sold.
- You stay in control of every action: the extension asks before each potentially destructive step, and you can always deny.
- Hard blocks cannot be bypassed. Actions like purchasing, financial trades, mass deletion, and credential exposure are blocked even in the most permissive permission mode.
- Standalone chat is explicit. After extension OAuth, a turn you start sends your prompt, selected browser context, and tool results to the Verboo Router. Browser text is fenced as untrusted data.
- MCP stays local. The Verboo in Chrome MCP transport does not carry CLI tokens into the extension.
What the extension accesses
| Data | Why | Where it goes |
|---|---|---|
| Active tab URL and title | Show context in the side panel and route tool calls | Sent to the Verboo Router only during a standalone chat turn after extension OAuth. |
| Page content you read or click on | Execute tools you approved | Sent to the Verboo Router only for a turn you started; text is fenced as untrusted browser data. |
| Chrome tabs and tab groups | Manage your browsing during a turn (list, switch, close, open new) | Used locally for execution; selected tool results may be included in the active Router turn. |
| Your Verboo account session | Authenticate standalone chat | Stored locally as verbooSession; access tokens are sent only to bundled Verboo OAuth/Router endpoints and are never copied from the CLI. |
| Permission mode (Manual / Auto / Skip) and per-site grants | Enforce your chosen safety level | Stored locally under chromePermissionMode and siteGrants. Never sent anywhere. |
What the extension does NOT do
- It does not read your keystrokes outside of tools you explicitly approve.
- It does not track you across sites that the extension is not active on.
- It does not collect analytics, telemetry, or crash reports.
- It does not read or modify pages on internal Chrome URLs (
chrome://,chrome-extension://,about:) — these are hard-blocked. - It does not read or modify content on
chrome.google.com/webstore. - It does not store your browsing history.
- It does not load executable code from a remote origin. All extension scripts are bundled.
- It does not request the
debuggerpermission. Future full-page screenshots will re-add it with an updated listing.
Storage keys (multi-user accurate)
| Key | Module | Contents | Sent off-device? |
|---|---|---|---|
verbooSession |
src/auth/auth.js |
{ accountId, email?, accessToken, refreshToken?, expiresAt?, source: 'oauth' } |
Bundled Verboo OAuth/Router endpoints used by standalone chat. |
verbooModelsCache / verbooSelectedModelId |
src/auth/auth.js |
Router model catalog, timestamp, and selected model ID | The selected model ID is included in Router requests. |
chromePermissionMode |
src/policy/modesStore.js |
One of 'manual', 'auto', 'skip' |
Never. |
siteGrants |
src/policy/siteGrantsStore.js |
Array of { host, decision, updatedAt } |
Never. |
All persistent state lives in chrome.storage.local, scoped to this extension's profile. Clearing the extension's data removes everything. Nothing is synced to your Google account.
Permissions explained
sidePanel— Opens the Verboo control panel alongside the page you are on.identity— Opens the user-initiated Verboo OAuth PKCE flow and receives its Chrome callback.storage— Persists the extension session, model cache/selection, permission mode, and grants.scripting— Injects small scripts into the active tab to read content, click elements, or fill form fields you approved. Scripts are bundled in the extension; the extension never evaluates strings fetched from a remote origin.tabs— Lists, switches, closes, opens, and updates tabs. Used to manage browser state during a turn.tabGroups— Groups browser tabs when you organize a multi-step task.host_permissions(http://*/*,https://*/*) — Required soscriptingandtabscan work on any HTTP/HTTPS page. Non-HTTP schemes (file://,chrome://,about:) are not reachable.
Future permissions, added only when needed and announced in a Store update:
debugger— For full-page screenshots and sandboxed JavaScript evaluation via the Chrome DevTools Protocol. Not requested in the current build.
When you are not signed in
If you are not signed in, standalone chat does not call the Verboo Router. The side panel still exposes local permission and site-grant controls.
Multi-user
Zero hardcoded paths, users, or tokens. accountId from the
OAuth session distinguishes users. Every account
on the same Chrome profile has an independent verbooSession,
chromePermissionMode, and siteGrants.
Third parties
The extension embeds no third-party scripts, fonts, or trackers. All assets are bundled in the extension package. Standalone inference is requested through the Verboo Router after OAuth.
Children
The extension is not directed at children under 13, and we do not knowingly collect data from children.
Changes to this policy
Material changes will be reflected by updating the date at the top. Continued use after a change indicates acceptance of the updated policy.
Contact
Open an issue at the Verboo Code repository issue tracker (replace before publishing to the Web Store).