Data, permissions, and accounts
Understand who handles chats, files, local records, and optional compatibility permissions.
Content baseline: 2.5.0-dev. Store releases and browser builds may differ.
Where chats and files go
The browser sends chat content and attachments to your selected AI sites without relaying them through a ChatBrawl server. Check the recipients before sending. Each provider processes received data under its own policy.
Local processing does not mean that AI sites receive no content. Models, subscriptions, quotas, conversation storage, and platform data policies still belong to the relevant provider.
Data stored in this browser
The extension stores settings, personal prompts, and local conversation records in the browser. These are separate from the full conversations in provider accounts.
Removing local records and deleting conversations on original sites are different actions with different effects.
What installation permissions do
The current Chromium (Chrome / Edge) source manifest includes broad HTTP/HTTPS host access. Firefox builds can present permissions differently. Review the permissions shown by your actual build and browser.
| Permission group | Purpose |
|---|---|
| storage | Save settings, prompts, and local conversation records |
| Host access and site adapters | Embed original sites and adapt input, tools, and attachments |
| scripting / webNavigation | Load adapters and handle relevant page navigation |
| declarativeNetRequestWithHostAccess | Apply embedding compatibility rules for supported sites |
Optional compatibility permissions
Some sign-in or embedded-page issues may require site cookie compatibility settings or site-specific data operations. The extension requests optional permissions such as contentSettings and browsingData through the browser separately.
Read the stated purpose and scope before granting them. Clearing site data can affect sign-in; compatibility troubleshooting is not merely an appearance change.
Website and extension requests
Opening the website prompt library makes catalog requests. Submitting feedback sends the information entered in that form. These website requests are separate from sending chats and files to AI sites.
You do not need to include passwords, cookies, or full private conversations in feedback. See the privacy policy for the full explanation of data handling and permissions.
Read the full privacy policy ↗Provider accounts stay separate
ChatBrawl does not create or merge AI provider accounts for you. Sign-in, subscriptions, refunds, model access, and security challenges are handled by the original providers.
If a site asks you to sign in again or complete a challenge, complete its normal process on the original site, then return to the workspace.