Privacy, in plain language.

Depending on your task, Browser Use may handle:

• Open-tab metadata, including page titles and URLs.
• Web history results when you or your agent explicitly searches Chrome history.
• Website content and resources needed to inspect or interact with a page, including text, images, links, form fields, and page structure.
• Browser actions and task artifacts, such as clicks, typed text, uploads, downloads, dialog responses, screenshots, and download metadata.
• Clipboard content only when a requested task reads from or writes to the clipboard.

Pages, files, history results, or clipboard content you choose to use may contain personal identifiers, communications, authentication information, financial information, health information, location information, or other sensitive content. Codevisor handles that content only as needed for the task you requested.

The extension sends task data over a loopback connection to the Codevisor application on the same computer. Codevisor uses it to show browser state to the agent you selected and carry out the actions you requested.

To provide an agent response, Codevisor may send relevant task instructions, page content, screenshots, and tool results to the AI model or agent provider you selected. The provider processes that information under its own terms and privacy policy. Codevisor may store conversations and tool results in its local database so you can return to your work.

If you enable usage analytics, Codevisor sends a small, fixed set of product events to PostHog, such as opening the app, creating a chat, sending a message, selecting a model or coding agent, and whether a turn completed. These events may include the Codevisor version, macOS version, processor architecture, and coarse usage ranges.

Analytics events do not include prompts, responses, code, file or project names, paths, browser content, terminal commands, or a user profile. IP-based geolocation is disabled.

If you enable crash and error reporting, Codevisor uses Sentry to receive native crash stack traces and a fixed allowlist of internal error identifiers. Reports may include the Codevisor version and build, macOS name and version, processor architecture, loaded binary identifiers needed for symbolication, and technical stack frames.

Codevisor disables Sentry’s session recording, screenshots, view hierarchy capture, network breadcrumbs, failed-request capture, performance tracing, file-I/O tracing, application-hang tracking, logs, metrics, and user identification. Before a report leaves the Mac, Codevisor removes exception messages, user and request fields, breadcrumbs, arbitrary context, and directory components from binary and stack-frame paths.

Reports are designed not to include prompts, responses, code, file paths, project names, browser content, terminal commands, or account identifiers.

We do not sell browser data, use it for advertising, or use it to determine creditworthiness or for lending. We use and transfer browser data only to provide the Browser Use feature, comply with applicable law, protect users and the service, or complete a corporate transaction permitted by applicable policy.

Browser data may be shared with the AI model or agent provider you selected, and with a website or service when your requested task requires interacting with it. We do not permit employees or contractors to read browser content except with your explicit consent for support, when necessary for security, or when required by law.

Codevisor’s use and transfer of information received from Google APIs complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.

When you enable the corresponding privacy choices, PostHog processes product analytics and Sentry processes crash and error reports on Codevisor’s behalf. They may not use this information for advertising or sell it.

The extension does not maintain a developer-operated cloud database. It keeps only the temporary connection and tab state needed for an active Browser Use session.

Codevisor stores chat history and associated tool results locally until you remove them. AI model providers and websites involved in a task may retain information according to their own policies.

Optional analytics and diagnostic events are retained only as long as reasonably needed to understand product usage, investigate reliability problems, and improve Codevisor.

The extension accepts connections only from the Codevisor application through a loopback address on your computer. Chrome displays its debugging indicator while Codevisor controls a tab. Codevisor limits extension data handling to the functionality exposed by Browser Use and the permissions disclosed in the Chrome Web Store.

You can stop or limit Browser Use at any time:

• Turn usage analytics or crash and error reporting on or off independently in Codevisor Settings → General → Privacy.
• Stop Browser Use from Codevisor.
• Choose Codevisor’s separate managed browser instead of your Chrome session.
• Disable or uninstall the Codevisor extension in Chrome.
• Remove local conversations and tool results from Codevisor.
• Manage Chrome history and operating-system clipboard content using their controls.

We may update this policy as Codevisor changes. The effective date above identifies the current version.

Questions or privacy requests can be sent to hello@codevisor.dev.