Effective July 15, 2026
We do not collect analytics, advertising data, terminal contents, commands, or workspace names. Your app connects directly to the relay you run. If you enable remote notifications, a narrow vmux push service processes a device push token and opaque event identifiers only to deliver those notifications.
Scope
This policy covers the vmux command-line application and daemon, the optional vmux relay, the vmux Remote iPhone and iPad app, and this website.
vmux on your computer
vmux stores its configuration and runtime state locally on your computer so it can keep sessions, workspaces, panes, and paired devices working. That data is not sent to us.
vmux may check the public GitHub Releases API no more than once per day to see whether an update is available. This ordinary network request does not include your terminal contents, commands, workspaces, or session data.
vmux relay and Remote
The relay is optional and runs on your own host. vmux Remote connects directly to that relay over your Tailscale network or a local network. vmux does not proxy, store, or inspect those terminal sessions through a vmux-operated service.
The app stores the host details and pairing credentials needed for your connections in the device Keychain or Keystore. It does not include advertising SDKs, third-party analytics, or behavioral trackers. We do not receive terminal contents, hostnames, commands, workspace names, relay bearer credentials, or usage history from the app.
Remote notifications
If you allow notifications and pair with a compatible vmux relay, the app uses the vmux push gateway at push.vmux.sh to receive an alert while the app is suspended. Registration sends an Expo push token and a random per-device secret to the gateway over HTTPS, then proves control of that token with a short-lived challenge delivered to the device. The paired relay later sends the same token and secret with an opaque event ID and, when available, opaque workspace and pane IDs. It never sends terminal output, notification text, commands, hostnames, workspace names, or agent messages to the gateway.
The gateway stores only one-way SHA-256 hashes of the push token and per-device secret. Those hashes remain until the device unregisters or the service removes them. Short-lived challenges, rate-limit records, and duplicate-delivery records are held temporarily. Notification title and body are fixed by the gateway and cannot be supplied by a relay or agent.
Cloudflare processes gateway network traffic for secure delivery and abuse protection. Expo, Apple Push Notification service, and Google Firebase Cloud Messaging process the device token and notification payload to deliver the alert under their own privacy terms. Remote notifications are app functionality, not advertising or tracking.
Files, photos, and clipboard content
If you choose to paste or upload an image through the relay, the selected content is sent to the paired host you control and saved there for the command or agent you chose. vmux does not receive a copy. The feature acts only after you initiate it.
This website
This website does not set analytics or advertising cookies and does not embed tracking scripts. Like most hosting providers, the platform serving the site may process basic request information such as an IP address for delivery, reliability, and security under its own privacy terms.
Third-party services
You may choose to use services such as GitHub, Apple, Google, Expo, Cloudflare, or Tailscale with vmux. Those services are independent and governed by their own terms and privacy policies. vmux does not control their practices.
Children’s privacy
vmux is a developer tool and is not directed to children. We do not knowingly collect personal information from children.
Changes
If these practices change, this page will be updated with a new effective date. Material changes will be described clearly before a release that depends on them.
Contact
Questions about privacy can be sent to [email protected].