Privacy Policy
Ollama Client is designed as a local-first extension. This policy explains what data is processed, where it is stored, and when it leaves your device.
Effective date: February 7, 2026.
This policy applies to the Ollama Client browser extension and the documentation pages on this site.
Data we collect
Section titled “Data we collect”The extension does not run first-party analytics, ad trackers, or telemetry pipelines. The data that exists on your device while using the extension is:
- Chat prompts and model responses generated during use.
- Session metadata (titles, timestamps, branch state).
- Optional uploaded file content for local retrieval workflows.
- Optional images attached to chat messages.
- Optional page content, tab titles/URLs, and selected text when you use browser-context features or when a tool-capable model calls a browser-context tool.
- Settings and provider configuration values.
- A bounded local diagnostic event buffer containing technical status codes, request IDs, and timing data, but no prompt or response content.
Where data is stored
Section titled “Where data is stored”- Local browser storage backed by SQL WASM (
sql.js). - Optional ZIP backups stored locally when you export.
- No default cloud sync from the extension itself.
Network communication
Section titled “Network communication”The extension sends prompts to whichever provider endpoint you configure. Typical local endpoints:
- Ollama (
localhost:11434) - LM Studio (
localhost:1234) - llama.cpp server (
localhost:8000)
LAN endpoints are supported when configured by the user. If you point the extension to a remote endpoint, your prompt data will be sent to that endpoint.
The OpenRouter preset sends two static application-attribution headers: the Ollama Client website and application name. It never substitutes the page you are viewing, a chat URL, or another user-specific value into those headers. Your API key remains device-local, but prompts and selected context are processed according to OpenRouter and its routed model provider’s policies.
When browser-context tools or image input are used, the extracted context or image data becomes part of the provider request for that chat turn. Local providers receive it locally; remote providers receive it over the configured remote endpoint.
Permissions
Section titled “Permissions”The extension requests browser permissions for chat UX, optional page extraction, and provider connectivity:
storage— settings and local state.tabsand content-extraction-related permissions.- Network / host permissions to reach configured provider endpoints.
Retention and user control
Section titled “Retention and user control”- You can delete chats and associated local artifacts from the UI.
- You can disable RAG and related indexing features.
- You can disable browser tab access from settings or the composer context controls.
- You can reset storage and configuration from the settings page.
- Diagnostic events expire after seven days, are capped at 200 records, and can be cleared from Help → Diagnostics & support.
Diagnostic support bundles are generated and previewed locally. They exclude chats, prompts, responses, uploaded files, page content, embeddings, API keys, headers, cookies, browser history, and full provider endpoints. The extension never uploads a support bundle automatically; you choose whether to copy, download, or share it.
Security notes
Section titled “Security notes”- Do not expose provider APIs publicly without access controls.
- Treat LAN endpoints as sensitive infrastructure.
- Review provider privacy policies for any non-local endpoints.
Policy changes
Section titled “Policy changes”This policy may be updated as the architecture evolves. The latest version is always published at this URL.
Contact
Section titled “Contact”Questions: shishirchaurasiya435@gmail.com
© 2026 Ollama Client. Local-first by design, with endpoint behavior controlled by the user.