Overview
The Browser Connector gives Violoop access to Chrome only after you grant Chrome permissions and approve local pairing. Cookie values are sent to the Violoop application running on the same computer so its Preview browser can use your existing web sessions. Browser content is accessed only to perform browser actions you request through Violoop.
The extension does not sell personal data, use it for advertising, create advertising profiles, or send Cookie values directly to a developer-operated cloud server.
Scope
This policy applies to the Violoop Browser Connector Chrome extension. It covers data handled by the extension and its local connection to the Violoop desktop application. Violoop services used after data reaches the desktop application may be governed by additional Violoop product terms and privacy notices.
Data we handle
| Cookies and authentication information | All HTTP/HTTPS Cookies available to the current Chrome profile, including Cookies that may represent signed-in sessions. The extension does not read saved passwords, passkeys, payment cards, or Chrome password manager data. |
|---|---|
| Browser and website content | Active-tab URL, title, visible page structure, text, form state, screenshots, and action results when needed for a user-requested browser task. |
| Interaction data | User-requested actions such as navigation, clicking, typing, scrolling, selecting options, and switching tabs. |
| Local connection data | Extension ID and version, pairing status, a random pairing token, synchronization timestamps, and import result counts. |
How we use data
We use the data described above only to provide the Connector's disclosed functions:
- Import Chrome cookies into the local Violoop Preview browser session.
- Keep locally imported cookies up to date after you enable automatic sync.
- Inspect and operate the active Chrome tab when you ask Violoop to use your current browser.
- Maintain and secure the authenticated local connection between Chrome and Violoop.
- Report local connection and synchronization status to you.
We do not use this data for unrelated analytics, credit decisions, advertising, or tracking your activity across websites for commercial purposes.
Local transfer and AI tasks
Cookie synchronization
Cookie values are transferred over the loopback interface to the Violoop application on the same computer and imported into its dedicated Preview browser session. The extension does not send Cookie values directly to Violoop cloud services or advertising services.
Browser tasks
Browser content, screenshots, and action results are first sent to the local Violoop application. When you ask an AI agent to perform a browser task, relevant task content may be processed by Violoop and the AI model provider configured for that task in order to fulfill your request.
Storage and retention
- The extension stores its pairing token, enabled state, and recent sync status in Chrome extension storage. The storage is restricted to trusted extension contexts and is removed when the extension is uninstalled.
- Violoop stores only a cryptographic hash of the pairing token in its local application data.
- Imported cookies remain in the dedicated local Violoop Preview browser profile until they expire or local Violoop application data is cleared.
- Browser task content may be retained in Violoop session history according to your Violoop settings and the service used for the task.
Sharing and sale
We do not sell personal data or share it with advertisers or data brokers.
Data may be processed by service providers only when necessary to provide a Violoop feature you request, maintain security, comply with law, or protect users and the service. Any AI model provider involved in a browser task is limited to processing the task content needed to fulfill that request.
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Security
Violoop uses technical safeguards designed for this local connection:
- The desktop bridge listens only on the local loopback interface.
- The bridge accepts only the official Violoop Browser Connector extension ID.
- First use requires an explicit pairing confirmation in the Violoop application.
- Cookie import and browser control require a random pairing token.
- The desktop application stores a token hash rather than the original token.
- Browser control uses fixed actions packaged with the extension; Violoop cannot send arbitrary JavaScript for the extension to execute.
No security measure is perfect. Keep Chrome and Violoop updated, and approve pairing only when you initiated it from the extension.
Your controls
- Nothing is read or synchronized until you approve the requested Chrome permissions and local pairing.
- You can disable the Connector and revoke its Cookie and website permissions from the extension popup.
- You can manage or remove the extension from Chrome's extension settings.
- You can clear local Preview and Violoop application data using the controls provided by Violoop or your operating system.
Children
The Browser Connector is not directed to children under 13, or the minimum age required in the user's jurisdiction, and we do not knowingly design the extension to collect children's personal information.
Changes to this policy
We may update this policy when the Connector's data practices or legal requirements change. We will update the effective date on this page and, when required, provide an in-product notice and obtain additional consent.