Privacy policy

Local LLM Chrome extension. Effective 27 October 2026.

Local LLM provides a language model to websites you approve. This policy describes what the extension handles and where it goes. The same text is linked from the extension's options page.

Who this applies to

The extension is published from the open-source project at github.com/gosienna/Project14_ChromeLLMBackend. The developer does not run a server for this extension. There is no account, no analytics, and no telemetry.

Data that stays on your device

• Settings, the list of sites you have enabled, and your consent choices (always, once, or deny).
• A usage log of site origin, time, backend, and token counts. It does not contain prompt text or model output. You can clear it in the options page.
• Model weights you choose to download. They are stored in the extension's own storage and are not uploaded anywhere.
• API keys you paste. They are stored in the browser's extension storage. You can encrypt them with a passphrase. Websites cannot read them.
• Playground chats, custom tool code, and the tool registry. These stay in the browser.

A local model runs in the browser. Prompts and replies for that model do not leave the device.

Data sent off the device, and only when you turn the feature on

Nothing below is sent to the developer. Each transfer goes to the service you chose, under that service's own terms.

• Cloud model. If you enable a provider (Anthropic, OpenAI, Gemini, xAI, DeepSeek, OpenRouter, or an endpoint you type, including a server on your own computer) and allow a site or the playground to use it, the prompt is sent to that provider with your API key so the provider can answer. The consent dialog says so before the first use.
• Web search. If you allow web search for a site, or enable it in the playground, the search query is sent to Tavily when you have saved a Tavily key. Otherwise the extension opens a Google results page, reads the titles, links, and snippets, and closes it. Image search works the same way. The extension then downloads an image only if it was in those results and you, or a site you allowed, ask for it.
• Model weights. When you download a local model, the weights are fetched from Hugging Face (huggingface.co and its download hosts). That download is the model file, not your prompts.

What websites you approve can do

An approved site can send prompts to the model and receive the text reply. It cannot read your API keys, your other sites, or your tabs. Any script on that site, including third-party scripts, can call the model once you have approved the origin. You can revoke a site at any time.

The playground's browser tools are separate. They are off until you enable them. When you do, they can read tabs you have open and the content of a page you ask them to act on, and that information is given to the model you selected. They are not available to websites.

What we do not collect

• No name, email, address, or other identity information.
• No health, financial, or payment information.
• No browsing history, and no log of your clicks, mouse, scrolling, or keystrokes.
• No advertising profile, and no sale of data.

Limited Use

The use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

• Data is used only to run the language model and the features you turn on (a cloud provider, web search, or playground tools).
• It is not sold, and it is not transferred except to the provider you configured for that feature, or as required by law.
• It is not used for advertising, for creditworthiness, or for lending.
• People do not read your prompts. A prompt stays on your device, or is sent to the provider you configured so that provider can answer it.

Permissions

The extension does not ask for access to your websites at install. It asks for a site only when you enable that site, and for a provider only when you turn that provider on. Page access for playground tools and for saving search images is requested from the button that enables those features.

Changes

If this policy changes, the new date will be shown at the top of this page and in the extension update.

Contact

Questions about this policy: open an issue on the project repository.