Last updated: June 2026
Chromium (“the Extension”) is a browser-side AI assistant that helps users interact with web pages through natural language. This policy explains what data the Extension handles and how.
The Extension does not:
The Extension stores the following data locally in your browser using chrome.storage.sync and chrome.storage.session:
| Data | Purpose |
|---|---|
| AI provider & model selection | Remember your last-used configuration |
| API keys (per provider) | Authenticate requests to AI APIs on your behalf |
| Custom system prompt | Personalize AI behavior |
| Language preference | UI language (English / Chinese) |
| Conversation history | Display previous messages within the current session |
| Custom skills | User-defined task snippets |
| Action delay, step limit, history rounds | Behavior configuration |
chrome.storage.sync data may be synced across your Chrome-signed-in devices by Google. The developer has no access to this data.
When you send a message or click “Add Page”, the Extension reads the current tab’s DOM HTML and sends it as part of your prompt to the AI provider you have configured. This data goes directly from your browser to the AI API — it does not pass through any developer-controlled server.
Depending on your configuration, prompts and page content are sent to one of:
You are responsible for reviewing the privacy policies of the AI provider you choose.
If you use the GitHub Copilot provider, the Extension performs a standard OAuth Device Flow with GitHub to obtain an access token. This token is stored locally in chrome.storage.sync and used solely to authenticate Copilot API requests. No GitHub account data is read or stored beyond the token itself.
<all_urls>): Required to read page DOM and execute AI-directed actions (click, type, scroll, navigate) on pages you are actively using.The Extension is not directed at children under 13. We do not knowingly collect any data from children.
Updates will be reflected in the “Last updated” date above. Continued use of the Extension after changes constitutes acceptance.
For questions about this privacy policy, please open an issue at the Extension’s source repository or contact via the Chrome Web Store developer contact email.