Synth Workspace Bridge — Privacy Policy

Last updated: 4 November 2026

The Synth Workspace Bridge extension (“the extension”) connects your browser to a Synth Workspace deployment that you choose. This policy covers the extension only. The Workspace deployment you pair with has its own data handling, set by whoever operates it.

Contact: syntithenai@gmail.com

Summary

• The extension has no servers of its own. It does not send data to the developer.
• There is no analytics, telemetry, advertising, or crash reporting.
• Three kinds of data can move through the extension, and each goes only to a destination you chose.

1. Pairing

The extension stores a random pairing token and the list of Workspace origins you approved in chrome.storage.local. A pairing request that is still waiting for your Allow/Deny answer is kept in chrome.storage.session for two minutes, then discarded. The Workspace stores the token encrypted on your device and presents it with every request. The token identifies the connection, not you. There is no account, email address, or identity in the extension.

To offer one-click pairing, a small content script on the Synth Workspace origins announces the extension's id and version to the page. It reads no page content and modifies nothing. A workspace page then asks to pair, and the extension shows a Chrome notification naming that exact origin. Nothing is shared until you click Allow.

Revoking the pairing or uninstalling the extension deletes the token, the approved origin list and any pending request.

2. Browser control

When you, or an assistant acting on your request, ask the Workspace to act in a tab, the extension may read:

• the tab's URL and title;
• the page's visible text, links, and form-field labels;
• a PNG screenshot of the visible tab.

It may also click an element, type into a non-password field, press Enter, navigate to a URL, open, close, or activate a tab.

That data goes only to a Workspace origin you approved when pairing — the public deployment, a localhost development origin, or your own self-hosted https deployment. The extension does not store page content, and does not send it to the developer or to any third party.

Limits built into the extension:

• password fields are never read or filled;
• the debugger is attached for one action and detached immediately afterwards;
• browser-internal pages (chrome://), the Chrome Web Store, and other extensions cannot be controlled;
• a click can be pinned to the text and link you approved, so a page that changed underneath is reported rather than clicked;
• page text is treated as untrusted input by the Workspace.

3. Model requests (bring your own key)

If you use the extension to route model calls, it handles:

• the request body and model name produced by your Workspace;
• the provider API key you configured in the Workspace.

They go only to the model-provider endpoint you selected. The key exists in memory for the duration of one request; the extension never writes it to storage and never logs it. The extension does not otherwise receive your chat history — it relays exactly the request the Workspace sends.

Providers process those requests under their own privacy policies. The extension's provider allowlist is published in its manifest.json and shown on the Options page.

4. Gmail research (optional native helper)

The extension can read Gmail only when you ask the Workspace to research a contact and you have installed a separate helper program on your own computer. The helper is not part of the extension package and is not installed or updated by it.

For one research request, the extension passes to the helper:

• the Gmail address and app password you saved in the Workspace;
• the email addresses of the contact being researched.

The helper opens Gmail over IMAP/TLS in read-only mode, collects messages to and from those addresses from the inbox and sent mail, and returns them to the extension. The extension relays them to the Workspace origin you paired. The helper does not send, move, delete or label mail, and does not read any mailbox other than the folders the request names.

The app password exists in memory for the duration of one request. The extension does not write it to chrome.storage, a log, a notification, or anywhere else, and the helper does not persist it. The helper is reachable only by this extension: Chrome starts a native host only when the host's manifest lists this extension's id in allowed_origins.

The Workspace, not the extension, decides what is kept from a research run. It stores the resulting profile notes on your device and, if you enabled Google Drive backup, in the backup you own. Nothing from this path is sent to the developer.

5. What the extension does not do

• It does not sell or share data for advertising or credit.
• It does not use analytics, telemetry, or crash reporting.
• It does not read tabs in the background. Nothing happens until an action is requested.
• It does not download or execute remote code. Every expression it evaluates is a constant in its own bundle; the paired page cannot supply a script.
• It does not read cookies, saved passwords, or browsing history.
• It does not read Gmail unless you ask for a contact research run and have installed the optional helper.
• It does not read Gmail unless you ask for a contact research run and have installed the optional helper.

6. Limited Use

The extension's use of data complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is used only to provide the extension's single purpose: connecting your browser to your own Workspace so the Workspace can act through your signed-in tabs, route model requests through your connection, and, when you ask, read mail for a contact through the helper you installed.

7. Retention

The extension retains the pairing token and the approved origin list until you revoke them or uninstall the extension. A pending pairing request is discarded after two minutes. It retains no page content, model requests, provider keys, app passwords, or email.

8. Your controls

• Revoke pairing: Options page → Revoke all. Every page is refused immediately. Rotate token issues a new token and clears the approved origins; Remove next to an origin withdraws just that deployment.
• Unpair in the workspace: also asks the extension to drop that origin.
• Revoke provider access: chrome://extensions → Details → Site access, or uninstall the extension.
• Remove everything: uninstalling the extension deletes its storage.

9. Children

The extension is not directed to children under 13 and does not knowingly collect data from them.

10. Changes

Material changes will be noted in the release notes and reflected in the date above.

11. Contact

Questions: syntithenai@gmail.com