Privacy Policy – Streebo AI Operator Extension

Effective Date: March 9, 2026 · Last Updated: March 9, 2026 · Version 2.0.0

        Summary: This extension does NOT collect, store, or transmit any personal user data. It
        communicates solely with your organization’s self-hosted AI Operator server.
    

1. Extension Purpose

Streebo AI Operator is an enterprise browser automation extension that enables attended-mode automation workflows. It connects to your organization’s AI Operator server and executes browser automation commands using Chrome DevTools Protocol (CDP).

2. Data Collection

We do NOT collect any personal data. Specifically:

Data Type	Collected?	Details
Personal Information	❌ No	No names, emails, or identifiers are collected
Browsing History	❌ No	URLs visited are not stored or transmitted to us
Page Content	❌ No	Page data is processed locally and never sent to third parties
Cookies	❌ No	Not collected; cookie APIs used only for automation tasks
Authentication Tokens	❌ No	Not collected or stored by the extension
Screenshots	⚠️ Contextual	Captured only during automation tasks and sent only to your organization’s server

3. Permissions Justification

This extension requests the following permissions, each with a specific technical reason:

Permission	Why Required
`debugger`	Core functionality: Uses Chrome DevTools Protocol (CDP) to perform browser automation (navigation, form filling, clicking, screenshot capture). This is the same protocol used by Puppeteer and Playwright.
`activeTab`	Access to the currently active tab for automation commands.
`tabs`	Create and manage browser tabs during automation workflows (e.g., opening a URL in a new tab).
`storage`	Store the server connection URL and connection ID locally on the user’s machine. No data is synced externally.
`alarms`	Keep the service worker alive during long-running automation sessions (MV3 terminates idle service workers after ~30 seconds).
`<all_urls>`	Automation workflows may target any website (e.g., internal enterprise portals, CRM systems). The extension must be able to attach CDP to any URL the user navigates to.

4. Data Flow

All communication occurs between the extension and your organization’s self-hosted server:

The extension connects to the server via WebSocket (wss://) – TLS encrypted.
The server sends automation commands (navigate, click, type, etc.).
The extension executes commands locally in the browser via CDP.
Execution results are sent back to the server.
No data is sent to Streebo or any third party.

5. Third-Party Services

This extension does NOT use any third-party analytics, tracking, advertising, or data collection services. The extension communicates exclusively with the server URL configured by the user or their organization’s IT administrator.

6. Data Storage

The only data stored locally (via chrome.storage.local) is:

Server URL – the address of your organization’s AI Operator server.
Connection ID – a random UUID for the WebSocket session, regenerated on each connection.

No browsing data, credentials, or personal information is ever stored.

7. Enterprise Use

This extension is designed for enterprise deployment. When deployed via organizational policy:

The server URL is pre-configured by IT administrators.
All automation is initiated by authorized enterprise systems.
The extension operates within your organization’s security perimeter.

8. User Control

Users can disconnect from the server at any time via the popup.
Users can change the server URL to connect to a different server.
Users can uninstall the extension at any time, which removes all stored data.
The Chrome debugger banner is visible whenever automation is active – full transparency.

9. Security

All server communication uses TLS encryption (wss://).
The extension uses Manifest V3 – Chrome’s latest and most secure extension platform.
No remote code execution – all JavaScript payloads come from your trusted server only.
CDP sessions are attached to one tab at a time and clearly indicated by Chrome’s debugger banner.

10. Changes to This Policy

We may update this privacy policy from time to time. Changes will be reflected in the extension’s listing on the Chrome Web Store and on this page. The “Last Updated” date at the top will be revised accordingly.