Cookie policy
The official document below is in English.
1. What we use
Webmux sets strictly necessary cookies only — no analytics, tracking or advertising cookie. We count page views on this site and the console with Cloudflare Web Analytics, which sets no cookie (Section 3). The cookies below are required for the service to function and are exempt from prior-consent requirements under the ePrivacy Directive.
2. The cookies
| Name | Purpose | Lifetime | Scope |
|---|---|---|---|
__Host-webmux_access | JWT carrying your authenticated session. Required for every authenticated API call. | 15 minutes (auto-refreshed via the refresh cookie below) | api.webmux.app · HttpOnly · Secure · SameSite=Lax |
__Host-webmux_refresh | Long-lived rotation token used to mint a fresh access token without re-auth. | 30 days | api.webmux.app · HttpOnly · Secure · SameSite=Lax |
__Host-webmux_oauth_csrf | Ties a sign-in (GitHub, Google or Apple) to the browser that started it, against cross-site request forgery. | 3 minutes | api.webmux.app · HttpOnly · Secure · SameSite=Lax |
__Host-webmux_link_binding | Set when a new sign-in uses an address an account already has, while you choose to link it: ties that choice to this browser, so the link it waits on works nowhere else. Holds a random value, nothing about you. | 10 minutes | api.webmux.app · HttpOnly · Secure · SameSite=Lax |
__Host-webmux_finalize_binding | Set when you create an account, while you accept the terms: ties that step to this browser, so the page's address creates nothing anywhere else. Holds a random value, nothing about you. | 10 minutes | api.webmux.app · HttpOnly · Secure · SameSite=Lax |
__Host-webmux_demo_sid | Set on demo.webmux.app when you open the playable demo. Holds 128 random bits naming the temporary container allocated to you, plus the time it was issued, and nothing else — no account, no identifier we can link to a person. The timestamp is what ends the visit; it dates the cookie, never you. | 30 minutes | demo.webmux.app · HttpOnly · Secure · SameSite=Lax |
__Secure-webmux_demo_preview | A signed value derived from the demo cookie above, which lets the pages your demo previews (addresses under demo.webmux.app) reach the same container. No account, nothing linked to a person. | 30 minutes | .demo.webmux.app · HttpOnly · Secure · SameSite=Lax |
__Host-webmux_pass | Set on the address of a page your machine previews, when a device you paired opens that page through our relay. Holds the pass your machine signed for that device and that page — your account, the device's key, the port and an expiry. Your machine checks it on every request; our relay reads it only to send the request to that machine. | The pass's remaining life, 12 hours at most | The preview's own address, <port>-<machine>.iframe.webmux.app · HttpOnly · Secure · SameSite=Lax |
__Host-webmux_browser_session | Local HMAC cookie held by the browser you signed in with on your own Webmux server — on your local network, over Tailscale, or on the machine itself. | 7 days | Your local server only · HttpOnly · SameSite=Lax · Secure and the __Host- prefix over HTTPS (a plain-HTTP server sets webmux_browser_session without them, since a browser would reject the prefixed form) |
Your own Webmux server sets three more cookies on its own address, which never reach us:
__Host-webmux_oauth_stateguards a sign-in from your server against cross-site request forgery, and__Host-webmux_return_toremembers the page to return to: 15 minutes each.__Host-webmux_sidecar_proxylets the pages you preview reach your server, in local mode only: until you close the browser.
Over plain HTTP, your server sets them without the __Host- prefix, which a browser would reject there.
A page you preview inside Webmux may set its own cookies; they belong to that page, not to us.
2A. What the app keeps in your browser
The app also keeps data in your browser's storage on your own server and, when you open a machine from another network, on app.webmux.app: your preferences, the key that proves this browser is a device you paired, a random identifier grouping your open tabs, and which speech vendors you allowed for dictation. On app.webmux.app it also keeps, for each machine you paired, that machine's key, so the page knows it is the same machine at your next visit; the newest version of the app that machine has served, so an older one is refused; and, if you turn on notifications, the background script that delivers them. All of it is strictly necessary, and none of it is sent to us.
3. Analytics — what runs, and what it is not
We use Cloudflare Web Analytics on this site and on the console. It measures page views and load performance in aggregate, and it is worth being precise about what that does and does not involve: it sets no cookie, assigns no persistent identifier, does not fingerprint your browser and does not follow you to any other website. That is why it appears in this section rather than in the table above — there is no cookie to list.
What we do not use:
- No advertising cookies.
- No third-party tracking cookies of ours — see Section 4 for the two third parties that may set their own.
- No marketing pixels.
- No fingerprinting (cookie or otherwise) for cross-site tracking.
- No profiling and no automated decision-making about you.
4. Third-party cookies
If you start a Stripe checkout flow, Stripe may set cookies on its own domain (checkout.stripe.com) to process the transaction. These cookies are governed by Stripe's cookie policy, not this one.
If you press Play in the app's Music band, your browser loads YouTube's player from youtube-nocookie.com; from then on the player may set cookies and store data in your browser, under Google's privacy policy, not this one. Nothing is asked of YouTube until you press Play.
5. How to control cookies
Strictly-necessary cookies cannot be disabled without breaking authentication. To stop them being set, sign out (which clears the session cookies) and refrain from signing back in. You can also clear all cookies for .webmux.app in your browser settings at any time.
6. Changes to this policy
If we ever introduce a non-strictly-necessary cookie, we will (a) update this page, (b) bump the version, and (c) prompt you for consent before setting it.