Purpose
ContextPorter lets users intentionally attach browser context — such as selected text, page text, sanitized DOM, screenshots or local files — to a message sent to a supported AI provider from Chrome's Side Panel.
Data stored locally
ContextPorter stores settings and a limited recent-chat list in Chrome local extension storage; active-session task/chat metadata in Chrome session storage; and captured screenshots, selected local files/images, and materialized provider-generated artifacts in extension-owned IndexedDB.
Binary attachment records are referenced by opaque local IDs rather than copied into Chrome storage. Temporary user attachment data and provider output data use bounded retention classes, and the extension enforces a local cache limit. Users can clear local ContextPorter data from Settings.
Data sent to AI providers
When a user sends a turn, ContextPorter may send the message, explicitly attached browser context, page title and URL used by the selected prompt, local files/images the user attached, and the configured reusable prompt to the selected AI provider.
Supported providers currently include OpenAI's ChatGPT, Anthropic's Claude, Google's Gemini, and xAI's Grok. Those providers process the transferred content under the user's provider account, settings, plan, privacy policy and terms.
Authentication and session information
Provider authentication remains in Chromium's normal web-session storage. ContextPorter may read short-lived provider bootstrap, account or session values at request time when a supported web workflow needs them. ContextPorter does not intentionally persist provider passwords, session cookies, access tokens or authentication secrets in its extension storage.
Website access
ContextPorter has no required host permissions. Provider origins are optional and requested provider-by-provider when the user chooses to connect them. A one-time page-context action requests only the active site's origin when required. If the user explicitly enables persistent on-page buttons, Chrome separately requests optional all-sites access so those controls can appear on normal webpages.
Provider file handling
Provider-generated files and images are accepted only from provider-specific allow-listed HTTPS hosts. When possible, artifacts are materialized into local IndexedDB so preview and download do not depend on short-lived remote URLs. ContextPorter does not upload provider-returned artifacts to a ContextPorter server.
Retention and deletion
Users can remove local attachments, clear local ContextPorter data from Settings, disable optional page tools, or remove the extension. Removing the extension causes Chrome to remove extension-owned storage according to Chrome's normal behavior.
Advertising, sale and human access
ContextPorter does not sell user data, does not use user data for personalized advertising, and does not operate a backend where the developer routinely reviews user prompts or browser context.
Limited use
ContextPorter's use of data is limited to providing and improving the user-facing extension workflow requested by the user. ContextPorter does not transfer browser data for advertising, credit, insurance, employment, or unrelated profiling purposes.
Third-party services
ContextPorter is independent and is not affiliated with or endorsed by OpenAI, Anthropic, Google, or xAI. Use of those services remains subject to their own terms and privacy policies.
Contact
For privacy questions or deletion/support requests, use the ContextPorter support page.