'%20d='M%2040%2040%20L%20120%2040%20A%2060%2060%200%200%201%20120%20160%20L%2040%20160%20L%2070%20120%20L%20110%20120%20A%2020%2020%200%200%200%20110%2080%20L%2070%2080%20Z'/%3e%3c/svg%3e)
Overview
Polymux is a desktop workspace that can connect to your browser, files, messages, email, and AI providers when you ask it to. This policy explains how the Polymux desktop app, mobile app, Personal Host, Polymux Connect relay, and browser extension handle information.
Information Polymux handles
Browser tab information
The browser extension makes a local inventory of open-tab metadata, including tab titles, URLs, window identifiers, active or pinned state, audible state, and last-accessed time. This inventory does not include page contents.
Assigned-tab content and activity
When you ask Polymux to work in a specific browser tab, it may read page content and perform or observe interactions needed for that task. This can include accessibility information, screenshots, navigation, clicks, typing, scrolling, console or network information, dialogs, and task results. Polymux limits this access to the tab assigned to the task.
Connected services
If you connect a service or AI provider through the desktop app, Polymux handles the information required to complete the actions you request. The connected provider's own privacy policy also applies to information sent to that provider.
Personal Host relay traffic
When you connect Polymux Phone or a remote Desktop to a Personal Host, Polymux Connect relays the requests and responses needed for pairing, conversations, Team actions, and run updates. The relay stores the Host's opaque identifier and a hash of its relay authentication secret. Request and response bodies are forwarded in memory and are not stored by Polymux Connect.
How information is used
Polymux uses information only to:
- identify the app, window, file, conversation, or browser tab you mean;
- complete tasks you request and return their results;
- maintain secure local connections between the extension and desktop app; and
- diagnose errors and protect the reliability and security of the product.
Local browser-extension communication
The extension communicates with the locally installed Polymux desktop app through a native-messaging host and a loopback-only service on your computer. Open-tab metadata, assigned-tab commands, cursor status, and task results stay on your device through these channels. The extension does not send browsing data to a hosted Polymux service.
Polymux Connect
A Personal Host keeps its service on the local computer and opens an authenticated outbound connection to Polymux Connect. Remote traffic is encrypted with HTTPS and secure WebSockets on the phone-to-relay and Host-to-relay connections. Cloudflare provides the relay infrastructure and processes this traffic to deliver the service; Cloudflare's privacy terms also apply to that processing.
Browser permissions
The extension uses browser permissions to:
- list tabs and identify the exact tab assigned to Polymux;
- communicate with the locally installed desktop app;
- refresh its local connection after the browser suspends it;
- read and interact with an assigned tab through browser debugging tools; and
- display the Polymux badge and cursor on ordinary HTTP and HTTPS pages.
Sharing and sale of data
Polymux does not sell user data. It does not use or transfer user data for advertising, creditworthiness, lending, or purposes unrelated to the product's disclosed function. Information is shared with Cloudflare to operate Polymux Connect, or with another service provider only when needed to use a connection you configured or complete an action you requested.
Storage, retention, and control
Browser-tab inventory and connection state are stored locally for the desktop app to use. Access to an assigned tab ends when the task releases it, the tab closes, the desktop app disconnects, or you disable the extension. You can also remove locally stored Polymux data by uninstalling the extension or desktop app and deleting its application data.
Polymux Connect retains a Personal Host's opaque identifier and relay secret hash so it can reject impersonated Host connections. It does not retain relayed request or response bodies.
Security
Polymux limits browser control to an identified assigned tab and uses local-only communication for the extension-to-desktop connection, authenticated Host relay connections, short-lived pairing codes, and encrypted network transport. No system can guarantee absolute security, but Polymux is designed to minimise access and keep you in control of connected services.
Changes to this policy
This policy may change as Polymux develops. The effective date above will be updated when material changes are published.
Contact
For privacy questions, email carlvince@polymux.com.