Privacy that matches how the extension works.

The website is static and only serves public product information. The extension stores preferences locally and sends user-requested content to the provider the user selects.

What the extension stores

Settings are kept in Chrome storage so the extension can remember your setup.

The extension stores configuration such as provider choice, API keys, model names, timeout values, and prompt templates. Those settings remain inside the browser profile unless Chrome sync is enabled by the user.

Local storage behavior

Provider settingsSaved in Chrome storage so the options page can restore them.
Prompt templatesStored locally to preserve the user's preferred explanation style.
API keysEntered by the user and retained only for the extension to send requests on their behalf.
No separate accountThe extension does not require a dedicated Read Code Helper login.

Network requests

Selected contentWhen the user asks for an explanation, selected text or page context is sent to the chosen AI provider.
Provider endpointsRequests go only to the services the user configured, such as Gemini or OpenRouter.
Page fetch helpersPage summarization can use user-configured helper services when the user triggers it.
Website trafficThe static site itself does not need browser permissions or access to extension storage.

Data use

Data is used only to run the extension and present the product site.

There is no site-side form, no account system on the website, and no embedded extension-to-site data bridge. The public website is a static deployment used to explain the extension and how to install it.

Website

Serves public documentation, the release split, and this privacy page. It does not need browser storage or extension permissions.

Extension

Uses the user's selected provider configuration to explain selections or summarize pages inside the browser.

Local control

The user can change or clear settings from the extension options page at any time.

Distribution split

The website is deployed separately from the extension package, so public site files are not bundled into the Chrome release.

Questions

If you want support or a correction, open the repository issue tracker.

This privacy policy is meant to be readable by humans and compatible with the extension release flow. If the implementation changes, the policy should be updated alongside the build split.

Return home Review build split