Ollama Bridge Extension — Privacy Policy

Effective May 19, 2026 · Updated June 11, 2026 (v1.1.0)
TL;DR. This extension does not collect, store, or transmit any user data to Get Causality or any third party. It exists solely to relay HTTP requests from the get-causality.com tab in your browser to your locally-installed Ollama server on your own machine. No telemetry. No analytics. No external network calls.

1. What the extension does

When you visit get-causality.com (or staging.get-causality.com, or localhost:5173 during local development), a content script injects into that page. It listens for postMessage events from the page and relays them to a background service worker, which forwards the requests to http://localhost:11434 (Ollama's default port on your machine). For long-running model generations the relay streams the response inside the extension and reports progress back to the page; the content of that stream never leaves your machine.

That's it. The extension is a one-purpose bridge — without it, modern Chrome blocks public HTTPS sites from talking to local services under its Private Network Access policy. The extension's permissions allow this single, scoped traffic flow.

2. What data the extension handles

Data typeWhere it goesWhy
Document text you paste into the LLM tabget-causality.com page → extension → your local Ollama → response back to the pageThis is the core function — sending paper text to Ollama for extraction. Stays on your machine.
LLM responses (extracted concepts and edges)Ollama → extension → pageReturned to the page for display in the reviewer panel. Stays on your machine.
List of installed Ollama modelsOllama → extension → pageSurfaced in the LLM tab's backend picker. Stays on your machine.

3. What the extension does NOT collect

4. Permission justification

Manifest permissionWhy we need it
host_permissions: http://localhost:11434/*The single endpoint the extension fetches. Chrome enforces this scope — the extension cannot reach any other URL.
host_permissions: http://127.0.0.1:11434/*Same endpoint, different address form (some Ollama configurations bind to 127.0.0.1 instead of localhost).
content_scripts.matches: get-causality.comThe only sites the bridge content script injects into. Chrome enforces this — the extension cannot intercept other sites' pages.
content_scripts.matches: localhost:5173The Get Causality development server, used by developers contributing to the project.

The extension declares ZERO entries in the permissions array (no tabs, no storage, no cookies, no <all_urls>, no webRequest, no activeTab).

5. Third-party services

None. The extension is a single-purpose proxy to your local machine. It does not communicate with Get Causality servers, Google, OpenAI, Anthropic, or any third party.

6. Data retention

The extension does not retain any data. Each request is forwarded to Ollama and the response is returned to the page. The extension has no chrome.storage usage and no IndexedDB usage.

7. Source code transparency

The extension is open source. The complete source is reviewable at github.com/eprasky/Get-causality-website/tree/main/extension.

Manifest version: 3 (current standard). No remote code execution. All logic is contained within the packaged extension files.

8. Changes to this policy

If the extension's behavior changes in a way that affects what data is handled, this policy will be updated, the version bumped, and the change disclosed in the extension's listing on the Chrome Web Store and the published changelog at the repository above.

9. Contact

For privacy questions about the get-causality.com website (which is a separate product), see the website privacy policy.

10. Compliance notes