Skip to content
mtmux

privacy

Privacy policy

Plain language; no dark patterns.

The short version

Your terminal contents are encrypted end-to-end between your machine and your browser. We cannot read them and we do not store them. Everything below is detail on the small amount of metadata that makes the service work — and if you run mtmux in local mode, none of it exists, because your machine never contacts us at all.

What we collect

Account data — only if you create an account: your email, and a customer identifier from our payment processor if you subscribe. Card details never touch our servers.
Broker metadata — connection timestamps, device identifiers, byte counts and outcome codes — enough to enforce plan limits and debug a failed pairing. Not the contents of anything.
Website analytics — aggregate page counts with no cookies, no cross-site identifiers and no ad networks.

What we never collect

Terminal output, keystrokes, file contents, paths or environment variables.
Your source code, in any form, at any time.
The secret half of a pairing code — it is never transmitted, not even as a hash.
SSH keys. mtmux never asks for one and has nowhere to put one.
Anything at all from a machine running in local mode.

Retention

Session frames are never written to disk by the broker — they are relayed and discarded. Connection metadata is kept only as long as it is useful for abuse prevention and debugging, and account data for as long as you have an account. Delete the account and it goes with it.

Third parties

Dodo Payments handles subscriptions and is the merchant of record; card details go to them and never to us. Beyond that, a hosting provider runs the broker. There is no analytics vendor, no ad network, no notification provider and no chat widget.

mtmux does not send notifications, so nothing is routed to Slack, Apple, Google or any other messaging service on your behalf.

Your rights

Email [email protected] to export or delete everything associated with your account; we complete requests within 30 days. Self-hosted installs hold their own data, and we never see it.

Changes

Material changes are announced in the changelog and by email to account holders before taking effect.