Privacy, in plain language.

What Vicaro is

Vicaro has two parts: a Chrome extension that reads the page you are on and performs the click or keystroke an assistant asks for, and a helper program you install and run yourself. The helper decides what to do, talks to the model you configure, and stores its data locally. They talk over a loopback connection.

Vicaro is closed-source software. The helper is self-hosted, and its local data directory can be deleted by you.

What the extension can see

Only what it needs to carry out a request you make:

• The list of open tabs, including titles and addresses.
• The visible content and interactive elements of a tab after you grant page access to that site.
• The action it is asked to perform, and the page state afterwards.
• An optional Google email, only if you choose to link an account.

Depending on the pages you open, this can include website content, browsing history in the form of open tabs, personal communications such as email or chat pages, and account identifiers. It does not read pages in the background, and it does not run on sites you have not granted. Outside the optional Google sign-in, nothing is sent anywhere except to your own helper and the model endpoint it is configured to use.

Permissions and optional capabilities

The extension asks for page access per site, the first time a task needs it. There is no broad host permission at install. Two capabilities are off until you enable them in Settings, Access:

• Deep control (debugger) uses Chrome's debugger attachment for trusted input, screenshots, DevTools inspection and file upload. Chrome does not allow this permission to be optional, so it is declared at install and attached only while a task needs it.
• History and closed tabs lets the assistant search your browsing history and reopen a closed tab, only when you ask it to.

Both can be removed at any time from Chrome's extension settings.

Google sign-in (optional)

You can link one Google account to the helper from the side panel. The extension gets a Google access token from Chrome, exchanges it for a Firebase ID token, and sends that token to your helper over loopback. The helper checks the token against Google's public signing keys and stores the account's name, email and Firebase user id in its local account.json. The ID token itself is not stored.

While an account is linked, its name and email are included in the assistant context sent to your model endpoint, so the assistant can answer questions about the signed-in account. Google receives the sign-in request, as it would for any Google sign-in. No chats, pages or memories are sent to Google or Firebase. You can switch accounts in Settings, General, Account; only one account is linked at a time. Signing out removes the local link and stops the account details from being added to future turns.

Where your data goes

• Your model endpoint. Messages, page text and tool results are sent to the model server you configure: a local server, your LAN, or a hosted provider. That server's privacy policy applies to it. Vicaro has no default provider and no fallback.
• Google sign-in (optional). Only if you choose it: Google and Firebase receive the authentication request, as described above. No page or chat content is included.
• Nowhere else. No analytics, no crash reporting, no usage statistics, no advertising identifiers, and no sale or sharing of data with third parties.

What is stored, and where

• On your machine: conversation history and task state live in an encrypted SQLite store owned by the helper. Memories and settings live in the same owner-only data directory.
• In Chrome: the panel stores your helper address, device credential, theme and model preference in chrome.storage.local.
• Linked Google account: the helper stores the account's name, email and Firebase user id in its local account.json. Signing out clears it.
• Model API keys are stored by the helper and are never returned to the panel.

This website

This site is a static site served by GitHub Pages. It does not set cookies, run analytics, or load third-party scripts. GitHub may keep standard web-server logs under its own privacy policy. The installer and extension downloads are served by GitHub Releases.

Your controls

• Revoke page access or the optional permissions in chrome://extensions, or in Settings, Access.
• Delete the helper's data directory to erase history, tasks and memories. The menu bar uninstall keeps it on purpose.
• Sign out in Settings, General, Account to remove the linked Google account.
• Uninstall the extension and the helper to remove everything.

Children

Vicaro is a developer tool and is not directed at children under 13.

Changes

If this policy changes, the updated version ships with the next release and is dated above. The latest version is always at vicaro.creativeducks.com/privacy.html.

Contact

Questions about this policy: hello@creativeducks.com. For setup help, read Support.