This policy is provided in English, Korean, Japanese, and Simplified Chinese for Chrome Web Store users.
Chromex Privacy Policy
Effective date: April 28, 2026
Chromex is a Chrome side-panel assistant that helps users work with webpages, selected tabs, uploaded files, voice input, images, and browser workflows through a local Codex bridge.
This Privacy Policy explains what data Chromex may process, why it is processed, and how the extension is designed to limit access to user-requested tasks.
What Chromex Does
Chromex can summarize webpages, compare selected tabs, answer questions about page content, draft text, process uploaded files, work with images, use voice input, search browser history when requested, and help with browser workflows.
Chromex is designed around user-controlled context. Page content, tab data, screenshots, history, files, images, audio, and browser actions are used only when a user requests a feature that needs that information.
Data Chromex May Process
Website content, including page text, selected text, DOM-derived content, images, videos, links, screenshots, and visible or readable content from the current page.
Tab information, including titles, URLs, favicons, and user-selected open tabs.
Uploaded files and images selected by the user.
Voice audio and transcripts when the user uses voice input or live voice features.
Browser history only when the user asks history-based questions and grants the required Chrome permission.
User activity needed for requested browser workflows, such as clicks, scrolling, DOM-assisted actions, and visible page interaction planning.
Personal communications or personally identifiable information only when such data appears in user-selected content, uploaded files, communications, or browser history.
Chromex does not intentionally collect health information, financial or payment information, precise location data, or authentication secrets as part of its single purpose.
Authentication and Local Bridge
Chromex uses a local native bridge to communicate with the user's configured Codex/OpenAI runtime.
The Chrome extension does not store raw OpenAI API keys, OAuth tokens, or ChatGPT session tokens in Chrome extension storage. Authentication handoff, API-key fallback, generated-image files, diagnostics, and runtime-heavy operations are handled by the local bridge installed on the user's computer.
Use, Sharing, and Storage
Chromex uses data only to provide the feature requested by the user. Data may be sent through the local bridge to the user's configured Codex/OpenAI service when needed to complete that task.
Chromex does not sell user data.
Chromex does not use user data for advertising and does not use user data to determine creditworthiness or for lending purposes.
Chromex may store local extension preferences such as theme, language, selected model, profile templates, enabled skills, onboarding state, and lightweight conversation metadata. Large generated assets, temporary files, and diagnostics are handled by the local bridge rather than Chrome extension storage.
Permissions and User Control
Chromex requests baseline permissions for the side-panel assistant and requests optional permissions only when a feature needs them. Users control when Chromex receives page context, selected tabs, uploaded files, images, voice input, browser history, and browser action permissions. Users can disable optional features, revoke Chrome permissions, clear local settings, and remove generated files.
Remote Code
Chromex does not execute remotely hosted JavaScript or remotely supplied extension code. Extension code is packaged with the MV3 extension.