Microsoft Edge and Google Chrome extension

Privacy policy

PLwC Chat Bridge connects the ChatGPT web interface to a separately installed PLwC runtime on the same Windows device. The publisher does not operate an extension analytics, advertising, telemetry, or cloud backend.

Effective and last updated: 9 August 2026

Short version: the extension runs only on supported ChatGPT pages, reads the visible content needed for its explicit PLwC workflow, stores limited settings and duplicate-prevention data in browser-local storage, and sends approved tool calls only to the PLwC Bridge at 127.0.0.1. Text inserted or submitted into ChatGPT is processed by OpenAI under your ChatGPT account and settings.

1. Scope and roles

This policy applies to the PLwC Chat Bridge extension distributed through Microsoft Edge Add-ons and the Chrome Web Store. The browser Store installs only the extension. The PLwC Gateway, loopback Bridge, and Native Launcher are separate local companion software installed through PLwC Windows Setup.

PLwC Chat Bridge does not provide a ChatGPT account or an AI model. OpenAI independently processes content in ChatGPT under the terms and privacy controls that apply to your ChatGPT account. Browser vendors independently process Store, installation, update, and browser diagnostic information under their own policies.

2. Data the extension handles

Visible ChatGPT content and personal communications

On chatgpt.com and the retained official compatibility host chat.openai.com, the extension inspects visible message elements for explicit PLwC tool-call and result markers and narrowly defined recovery conditions. Relevant protocol content can include tool names, arguments, results, errors, confirmation state, user-generated content, and personal communications. The extension does not access ChatGPT authentication cookies or passwords and does not scan other websites.

Conversation and call identity

The extension uses the current ChatGPT conversation path, a PLwC call identifier, a timestamp, and a deterministic signature of the tool name and arguments to prevent duplicate execution or conflicting reuse of a call ID. This is a narrow form of website/browsing-activity data limited to supported ChatGPT conversations.

Local settings

The extension stores bridge behavior preferences and optional local PLwC configuration overrides. Overrides may include local workspace and profile paths, a profile fallback name, governance thresholds, and Boolean feature choices. These values are sent only to the PLwC Bridge on the same device.

Local runtime data

The extension exchanges build identity, connection state, tool schemas, launcher status, approved tool arguments, and tool results with the local PLwC runtime. PLwC may create or retain user-requested files, profiles, audit records, and other local data according to PLwC's separate governance and workspace rules.

3. How data is used

Data is used only to provide the visible Chat Bridge purpose: validate the local PLwC tool boundary, show calls and results, apply user-selected safety and automation settings, prevent duplicate tool execution, send approved calls to the local runtime, and insert or submit the resulting text into ChatGPT.

The extension does not use runtime data for advertising, analytics, creditworthiness, lending, unrelated profiling, or model training by the PLwC publisher. It does not sell runtime data.

4. Connections and disclosures

Local PLwC Bridge: the extension's only extension-origin network connection is the fixed IPv4 loopback WebSocket at ws://127.0.0.1:3007/message. It is not a LAN or Internet endpoint.
Local Native Launcher: when requested, the extension contacts only the native messaging host plwc.chat_bridge.launcher installed by PLwC Setup to start and verify the local Bridge.
ChatGPT/OpenAI: when a primer or result is inserted and submitted through the existing ChatGPT page, that content is sent to and processed by OpenAI as part of your ChatGPT conversation. Automatic result submission is a visible setting and can be disabled.
Publisher: no runtime data is automatically transmitted to PLwC or a publisher-operated service.

5. Storage and retention

Bridge preferences and configuration overrides remain in chrome.storage.local until changed, reset, cleared with browser extension-data controls, or the extension is removed. The exactly-once registry is bounded to 5,000 claimed tool-call entries and remains in the same browser-local storage so browser and service-worker restarts cannot repeat accepted work. The extension does not store a separate full chat transcript.

Result cards and current connection/tool state are normally held in page or service-worker memory. Clipboard data is written only when you choose Copy Complete Result; the extension does not read your clipboard. Removing the extension does not delete separately installed PLwC workspace, profile, audit, or native-application data.

6. Your controls

You can disable automatic read-only execution and automatic result submission.
Recognized-write and sandbox automation are separate and off by default. Unknown operations always require confirmation.
You can reset local PLwC configuration overrides from the extension panel.
You can disable or remove the extension through Microsoft Edge or Google Chrome.
You can manage separately installed PLwC data through PLwC and Windows Setup.

7. Limited Use commitment

The use of information received from browser extension APIs and supported website access is limited to providing and improving the extension's single user-facing purpose. The publisher does not transfer that information except as necessary to provide the feature, comply with applicable law, address security or abuse, or complete a merger, acquisition, or sale of assets with the required protections and consent. It is not transferred for personalized advertising.

Humans do not read extension runtime data because the publisher does not receive it. A person may review only the specific diagnostic material you intentionally provide for support, information required to address security or abuse, information required by law, or properly aggregated and anonymized information. Remove private content, credentials, account identifiers, and local paths before sending a support report.

8. Security and data minimization

The extension uses Manifest V3 and packages all executable extension code. It does not download or execute remote JavaScript or WebAssembly. Host access is limited to two ChatGPT hosts and a fixed loopback endpoint. Tool execution remains disabled until the local build identity and exact eight-tool contract are validated.

For the broader local Gateway and workspace security model, see the PLwC security overview. That project overview supplements, but does not replace, this extension-specific privacy policy.

No software can eliminate every risk. Keep PLwC and your browser updated, review confirmation prompts, use synthetic data for testing, and do not put passwords, API keys, payment data, or other secrets into PLwC tool calls or support reports.

9. Changes to this policy

This page will be updated before a new extension behavior materially changes the data handled, its purpose, recipients, or user controls. The effective date above identifies the current version.

10. Contact

Privacy and support questions can be sent to info@plwc.de. For reproducible non-sensitive defects, use GitHub Issues. Do not include credentials, private ChatGPT content, publisher-account data, or confidential workspace files.