DeepSeek Harness Connector — Privacy Policy
Last reviewed: 2026-11-05. Applies to DeepSeek Harness Connector 0.1.0 (Chrome extension) and its local companion.
DeepSeek Harness Connector lets a DeepSeek Harness agent running on your computer read and act in the Chrome tabs that you explicitly attach to one of its sessions. This policy says what the extension collects, where it goes, and what it does not do — in the terms the Chrome Web Store data-use form asks for, and accurately.
Publisher: Corsen AI. Contact: [email protected].
The short version
DeepSeek Harness Connector works only on your computer. Corsen AI does not operate a relay, an analytics service, an account system or a telemetry endpoint for the extension, and receives none of the data described below.
The extension talks only to the local connector on 127.0.0.1, which is part of your own DeepSeek Harness installation. What DeepSeek Harness then does with page content depends on your DeepSeek Harness configuration, as explained under "Where data goes".
Data the extension handles
Page content from attached tabs
What. The visible text, title, URL, and a list of interactive controls of a tab you explicitly attached to a DeepSeek Harness session — but only when that session requests it.
Where it goes. From the tab, to the extension, to the local connector on 127.0.0.1, to your own locally running DeepSeek Harness. From there it goes wherever your DeepSeek Harness is configured to send it — typically a model provider's API. That is your DeepSeek Harness doing that, under your configuration. The extension adds no destination of its own.
Before it leaves the page, the following are masked and never transmitted:
- password fields;
- hidden form fields;
- one-time codes and fields the page declares as such;
- payment card numbers, security codes, expiry dates, and cardholder names, as declared by the page;
- fields whose name or label indicates a password, secret, token, API key, one-time code, card number, IBAN, SSN, or PIN;
- credential-bearing parameters in URLs, and any username or password embedded in a URL.
Honest limitation. Detection is by the signals a page gives. A field with no telling type, attribute, name, or label cannot be distinguished from an ordinary one. We do not claim complete secret detection.
Screenshots of attached tabs
What. A picture of the visible part of a tab you explicitly attached, taken only when that tab's session requests one, as a JPEG of the viewport. Chrome can only capture the tab at the front of its window, so a covered attached tab is brought to the front first, and the result says that it was.
Where it goes. The same path as page content: to the local connector, to your own DeepSeek Harness, which keeps a copy in its own attachment store on your computer and sends it to the model provider you configured — only if that model accepts images; for a text-only model DeepSeek Harness substitutes a text placeholder that names the stored file.
Honest limitation. The masking above applies to text. A screenshot is pixels, and nothing in it is masked: whatever the page shows on screen — a displayed code, an account number, a message — is in the picture, exactly as you see it. The tool's description tells the model to read pages with the text snapshot and to use a screenshot for layout, and you decide which tabs a session may see at all.
Tab titles and URLs
What. The title and URL of open tabs, shown to you in the panel so you can choose what to attach; and of attached tabs, so you always see what a session controls.
Where it goes. To the panel. For attached tabs only, the current URL (scrubbed of credentials) is also reported to your own DeepSeek Harness when it asks.
Settings and identity
What. A random identifier for this installation, the connector's local address, the pairing code you typed, and which session is attached to which tabs.
Where it goes. Nowhere. Stored in this browser profile's extension storage. The pairing code is used to compute a proof for the local connector and is never itself transmitted.
What the extension does not do
- Does not send anything to Corsen AI. No analytics, telemetry, crash reports, usage statistics, or any other transmission. There is no Corsen server in the loop.
- Does not read cookies. The
cookiespermission is not requested. - Does not read history, bookmarks, passwords, or other extensions' data.
- Does not read page content from, or perform any action in, a tab you have not attached. When you open the tab chooser in the panel, the extension reads the titles and URLs of the open tabs locally, so you can decide which tab to attach; that list stays in the panel and is not sent to DeepSeek Harness.
- Does not act without a DeepSeek Harness request. The extension is passive until a session you attached asks for something.
- Does not sell, share, or transfer data to third parties. It has no third parties.
- Does not use data for advertising, profiling, or creditworthiness.
- Does not persist page content. Snapshots and screenshots are produced on request and forwarded; the extension keeps none. (Your own DeepSeek Harness keeps screenshots in its attachment store, on your computer, as it keeps every image a tool gives it.)
Storage and retention
The extension stores its random installation identifier, the connector's local address, the pairing proof and the session-to-tab bindings in Chrome local storage until you clear the extension's data or remove the extension. It does not persist page snapshots, page text, screenshots or form content.
Publisher access and Limited Use
Corsen AI does not receive, sell, rent, monetize or use this data for advertising, profiling, creditworthiness or any purpose unrelated to the extension's single browser-control function. Corsen AI personnel cannot access locally processed data. There is no telemetry.
DeepSeek Harness Connector's use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Security
The local connector listens only on 127.0.0.1. The extension and the connector authenticate each other with a proof derived from the pairing code; the code itself is never sent. Each DeepSeek Harness session is routed only to the tabs explicitly attached to that exact session. A session with no attached tab is refused instead of falling back to another tab.
Permissions
| Permission | Why it is needed |
|---|---|
<all_urls>, scripting | Read and act on the page in a tab you attach, which can be on any website. Chrome also requires broad host access for a screenshot you request. |
storage | Keep the installation identifier, the connector's local address, the pairing proof and the tab bindings on your device. |
sidePanel | Show the connector controls and the session status beside the page. |
alarms | Keep the local connection to the connector alive while the extension is paired. |
The extension does not request the cookies, debugger, history, bookmarks or webRequest permissions.
Chrome Web Store data-use form answers
| Question | Answer |
|---|---|
| Does the extension collect or use personal or sensitive user data? | Yes: website content (text, and screenshots on request) and web history (URLs) of tabs you explicitly attach, forwarded to your own local software. |
| Is it sold to third parties? | No. |
| Is it used for purposes unrelated to the single purpose? | No. |
| Is it used to determine creditworthiness or for lending? | No. |
| Is it transferred to third parties? | Not by the extension. Your own DeepSeek Harness may send it to the model provider you configured. |
In one paragraph
This extension lets your own locally running DeepSeek Harness read and act in the browser tabs you explicitly choose. Page content from those tabs — text, and a screenshot when the session asks for one — goes to your DeepSeek Harness on your computer, and from there to whatever model provider you configured it to use. Passwords, one-time codes, and payment fields are masked in the text before anything leaves the page; a screenshot shows the page as you see it. The extension never reads your cookies, never reads or acts in a tab you did not attach (it lists open tabs' titles and URLs only when you open the tab chooser, so you can pick one), and never sends anything to Corsen AI.
Your control
Tabs are inaccessible to DeepSeek Harness Connector until you attach them to a specific DeepSeek Harness session. You can detach a tab, forget the pairing, clear the extension's storage, remove the companion plugin from your DeepSeek Harness profile or uninstall the extension at any time.
Changes
This policy changes only when the extension's handling of data changes, and the review date at the top is updated. Previous versions are available on request to [email protected].
Contact
Questions about this policy: [email protected].
DeepSeek Harness Connector is an unofficial community project by Corsen AI. It is not affiliated with, endorsed by, or certified by DeepSeek or Google.