Effective date: April 11, 2026
This Privacy Policy explains how the Browsery Chrome extension (the “Extension”) handles information when you install or use it. Browsery is an open-source browser automation extension. Some Browsery features rely on a separate Browsery cloud service that works with the Extension.
Browsery is distributed from source code in its public repository. That open-source model improves transparency into how the Extension works and what kinds of data it can access, process, store, and transmit.
Browsery is an intelligent browser automation extension that turns your web browsing into an automated workflow. Instead of manually clicking through websites, filling out forms, or copying data, you can describe what you want in natural language, and the extension automatically handles the rest.
Using Browsery, you can:
The extension’s AI agents perform the decision-making and task execution. Rather than running this logic inside the extension itself, Browsery gathers browser-state information and sends it to a Browsery backend multi-agent service. The backend authenticates your Google identity, runs the multi-agent AI system, and returns browser actions for the extension to perform.
Users must sign in with Google through Chrome’s identity APIs before using Browsery’s cloud-assisted automation features.
Because the Extension is designed to work across many websites, it requests broad site access and browser permissions that allow it to inspect page state, interact with tabs, run scripts, use the side panel, and store your settings locally.
Depending on the features you use, the Extension may access or process the following categories of information.
Browsery uses Google sign-in through Chrome’s identity APIs. When you sign in, the Extension may access:
The Extension stores Google signed-in state locally. OAuth token caching, issuance, and revocation may also be handled by Chrome and Google services.
If you choose to use microphone or speech-to-text features, the Extension may process:
Browsery also stores certain optional provider and model settings for supported optional features such as speech-to-text, rather than for the main cloud-driven automation flow. If you configure those optional features, the Extension may store:
Optional using bring-your-own-key (BYOK) models with the cloud serviced
The information above is used only to operate the Extension and the features you invoke, including to:
Browsery does not include built-in advertising trackers or product analytics collectors.
Some data stays local in your browser. Some data is sent to external services only when the feature you use requires it.
The Extension stores data in Chrome extension storage, including chat history, session metadata, prompt favorites, Google sign-in state, firewall settings, general preferences, and optional speech-to-text or provider configuration if you choose to save it.
Browser login credentials and website cookies remain in your browser session. The Extension does not export browser cookies as a standalone dataset.
When you use the main Browsery automation flow, the Extension sends request payloads to the configured Browsery cloud endpoint. Those payloads can include:
The Browsery cloud service uses the Google bearer token to retrieve Google user information, derive a stable internal customer identifier, run the backend multi-agent system, and return browser actions.
The Browsery cloud service persists session and execution state for continuity and multi-agent coordination. That stored data may include categories such as:
Retention and handling of cloud-stored data depend on the deployment and operational practices of the service operator.
If you use Google sign-in, authentication data is processed through Chrome identity services and Google services. The Browsery cloud service may also call Google’s user information endpoint to validate the bearer token and resolve your Google account identity.
If you use speech transcription, audio may be sent to the configured speech-to-text provider used for that feature. Speech transcription currently depends on a configured Gemini-compatible setup.
The Extension requests the following permissions because they are necessary for its core functionality.
tabs / activeTab: lets the Extension read tab metadata and operate on the active page.scripting: lets the Extension inject and run scripts needed for automation.debugger: supports advanced page inspection and automation control.webNavigation: helps the Extension observe navigation state and page transitions.storage / unlimitedStorage: stores settings, chat history, session metadata, authentication state, and other local extension data.identity / identity.email: supports Google sign-in and access to Google profile email and identity information.sidePanel: displays the Extension’s side-panel experience in supported browsers.The Extension does not sell personal information or Extension data.
Information is shared only in the following situations:
You can:
Reasonable measures should be used to protect the systems that host cloud services, but no method of storage or transmission is completely secure. You should also protect your browser profile, device access, Google account, and any optional provider credentials you configure. If you use external services, you should review the privacy and security terms of those services as well.
If you use Google authentication, hosted cloud deployments, or optional third-party services, your information may be processed in countries other than your own, depending on where those services operate their infrastructure.
The Extension is not directed to children, and it is not intended to be used by children without appropriate supervision.
This Privacy Policy may be updated from time to time. When it is updated, the effective date at the top of this page should also be updated.
Questions or concerns should be directed to the Browsery maintainers through this repository’s support channel.