GO Chat UI — Privacy Policy
Last updated: July 22, 2026
GO Chat UI is a Chrome extension published by BamBam LLC ("we", "us", or "our"). This privacy policy explains what data the extension accesses and how it is handled.
1. No Data Collection by Us
We do not collect, transmit, or store any of your data on our servers. GO Chat UI contains no analytics, no telemetry, no tracking, and no accounts. We operate no backend for this extension — there is no server of ours between you and the AI provider.
2. Your API Keys
GO Chat UI requires your own OpenCode Go API key. The key is stored locally on your device using Chrome's storage API and is sent only to OpenCode's API, as the Authorization header on your chat requests, in order to answer your messages. It is never sent to us or to any third party.
When you first enter your key, it is validated by making a request to OpenCode's models endpoint.
Web search is optional and off unless you add a key for it. If you do, your Firecrawl or Exa API key is likewise stored locally on your device and sent only to that provider, on the searches you trigger. These keys are never sent to us, to OpenCode, or to each other's providers.
3. Your Conversations
The messages you type are sent to OpenCode's API so the model can reply. Your conversation history is stored locally on your device using Chrome's storage API, limited to your most recent 50 chats. Conversations are never transmitted to us.
You can delete your chat history at any time from the extension's settings page.
4. Local Storage
The extension stores the following data locally on your device using Chrome's storage API:
- API keys — your OpenCode Go key, and your Firecrawl or Exa key if you have enabled web search
- Chat history — your most recent 50 conversations, including the model used, the tokens each conversation consumed, and the search queries and result links from any web searches made in them
- Model list cache — the list of models available on your plan, refreshed every 24 hours
- Preferences — your selected model and the position and size of the chat window
- Token usage — a running count of tokens reported by the API
This data stays on your device. Clearing your browser data or removing the extension deletes it.
5. Third-Party Services
OpenCode. Your messages, your selected model, and your API key are sent to OpenCode's API (opencode.ai) to generate replies. Your use of that API is governed by OpenCode's own privacy policy and terms. We are not affiliated with OpenCode and have no control over how they handle your data.
Google favicon service. To show a small brand icon next to each AI model, the extension loads icons from Google's public favicon service (google.com/s2/favicons). This request includes the model provider's domain name (for example deepseek.com) but contains none of your messages, none of your personal data, and none of your API key.
Firecrawl and Exa (web search, optional). Web search is off until you add a key for one of these providers. When it is on and the model decides a question needs current information, the extension sends a search query — written by the model, not your message verbatim — to Firecrawl (api.firecrawl.dev) or Exa (api.exa.ai), along with your key for that provider. The provider returns matching results — titles, links and a short extract from each. If those are not enough to answer, the model may then ask the provider to open one of those pages, or a web address you supplied, and return its text. All of it is passed to the model so it can answer and cite its sources.
Only the search query is sent, not your conversation. If you have keys for both, Firecrawl is used first and Exa is tried only if Firecrawl fails or has run out of credits. Your use of either service is governed by that company's own privacy policy and terms; we have no control over how they handle your data. Removing the key, or switching web search off in the chat window, stops these requests entirely.
The extension loads no other remote resources. It bundles its own fonts and styles rather than fetching them from a CDN.
6. Permissions
The extension requests the following Chrome permissions:
- storage — to save your API key, chat history, and preferences on your device
- activeTab and scripting — to open the chat window on the page you are currently viewing, when you click the toolbar icon
- host permission for opencode.ai — to send your chat requests to the API
- host permissions for api.firecrawl.dev and api.exa.ai — to run web searches, and only if you have added a key for that provider
The extension does not read, collect, or transmit the content of the pages you visit. It injects its own chat window into the page and nothing more.
7. Affiliate Disclosure
The Firecrawl signup link on the extension's settings page is an affiliate link, labelled as one there. If you sign up through it we may earn a commission. This costs you nothing and does not change Firecrawl's pricing or your free allowance. Going to firecrawl.dev directly works identically.
We have a commercial interest in Firecrawl and none in Exa, and Firecrawl is also the provider the extension tries first. You can use either provider on its own, or pin the extension to whichever you prefer in its settings. Firecrawl may tell us a referral led to a signup, so commission can be paid; we receive nothing about your account, your searches, or your usage.
8. Not Affiliated with OpenCode
GO Chat UI is an independent, unofficial client. It is not affiliated with, endorsed by, or sponsored by OpenCode. "OpenCode" is the trademark of its respective owner. You must supply your own OpenCode Go subscription to use this extension.
9. Children's Privacy
GO Chat UI is not directed at children under 13, and we do not knowingly collect information from them. Since we collect no data at all, no such information reaches us.
10. Changes to This Policy
If this policy changes, we will update the date at the top of this page and publish the revised version here.
11. Contact
Questions about this policy can be sent to extensions@bambamhq.com, or via our contact page.