Privacy Policy for Gemma in Browser

Information we collect and process

When you enable page context or automatic summarization, the extension reads the current webpage's URL, title, visible text, and limited page structure to answer your request. It does not access Chrome's saved browsing history and does not request the Chrome history permission.

The extension stores your settings, optional API configuration, local chat sessions, and local-model cache metadata in Chrome extension storage on your device. Your API key is used only to authenticate requests to the API endpoint you configure.

Settings may include one or more provider profiles, model names, API base URLs, API keys, the optional Brave Search API key, page-context preferences, and token-usage totals. API keys are stored locally in Chrome extension storage and are sent only to the service selected by you for authentication. They are not included in analytics events or saved chat-message text.

If you use the local-model mode, prompts and page context are processed in your browser. If you enable a remote OpenAI-compatible model, your prompts, selected chat history, enabled current-page context, and any images or audio you explicitly attach are sent to the API provider and endpoint you configured. Attachment binary data is not stored in saved chat sessions. That provider's privacy policy governs its handling of the data.

If you enable Brave Search and provide a Brave Search API key, the text of your current question is sent to Brave Search to retrieve web results. The returned result titles, URLs, and descriptions may be included in the request context sent to your selected remote AI provider. Brave Search and the remote AI provider may process this information under their own privacy policies. Brave Search is not contacted when the feature is disabled or no key is present.

The extension records estimated or provider-reported input tokens, output tokens, total tokens, cache-write tokens, cache-read tokens, and request counts locally so that the per-message and settings-page usage displays work. These usage records do not contain the prompt or page text.

If PostHog analytics is configured by the publisher, the extension sends product-usage and diagnostic events to PostHog using a pseudonymous identifier. When a conversation is restored, selected, or updated, it also sends the active conversation history, including user prompts and assistant responses, to PostHog. An assistant response may quote or summarize current-page content. Automatic UI capture and page-view capture are disabled. The implementation does not send API keys, model URLs, raw model-download error text, or current-page URLs, titles, or text as standalone analytics properties.

How we use information

We use information to provide page-aware AI answers and summaries, run the local model, send requests to services you explicitly enable, save and restore your settings and chat sessions, display token usage, maintain reliability, and understand product usage when optional analytics is configured. We do not use the information for advertising, profiling, creditworthiness, lending, housing, employment, insurance, or other eligibility decisions.

How we share information

We do not sell your information. We share data only with: (1) the remote AI provider and endpoint you choose, when remote mode is enabled; (2) Brave Search, when you enable search and provide its key; and (3) PostHog, only in builds where the publisher has configured analytics. These recipients receive only the information needed for the enabled feature. We do not share API keys with PostHog, and we do not share page content with Brave Search unless it is part of the question you submit.

The extension does not access Chrome's saved browsing history, bookmarks, contacts, passwords, payment information, or other tabs. It does not continuously monitor pages. It reads the current page only when you request page context or have enabled automatic summarization.

Storage, retention, and deletion

Settings, provider profiles, API keys, chat sessions, token totals, debug logs, and local-model cache metadata remain in Chrome extension storage on your device until you change or delete them, clear the extension's data, or uninstall the extension. You can delete individual chat sessions in the side panel, clear debug logs in Settings, disable remote models or Brave Search, remove API keys, and disable page context or automatic summarization. Removing the extension or clearing its site/extension data deletes locally stored data, subject to Chrome's storage behavior.

Data already sent to a remote AI provider, Brave Search, or PostHog is retained and deleted according to that recipient's policies and applicable settings. Deleting local data cannot delete data already transmitted to those services. You may contact us at the address below for privacy questions or requests; requests involving a third-party provider may need to be made directly to that provider.

Security

Remote requests use HTTPS, except for explicitly supported localhost development endpoints. API keys are kept in Chrome extension storage and are redacted from local debug logs and analytics. No security method is guaranteed to be perfect, so do not submit information you are not authorized to send or do not want processed by the selected provider.

Children's privacy

The extension is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child provided personal information, contact us so we can review the request.

Changes to this policy

We may update this policy when the extension's data practices or applicable requirements change. Material changes will be reflected by updating the effective date on this page.

Contact

For privacy requests or questions, contact tesssuunmao@gmail.com.