Privacy Policy

The short version: the relay can’t read your terminal, keeps sessions in memory only, and logs almost nothing.

What we cannot see

Terminal input and output are end-to-end encrypted under keys derived from a secret that lives only in the link’s fragment — which browsers never send to the server. The relay forwards opaque ciphertext; it cannot read or reconstruct your session.

What exists, and only in memory

While a session is live the relay holds its id, a runner token, and an expiry — in RAM only. Nothing session-related is written to a database or disk, and it is discarded when the session ends or expires.

What we log

Operational logs carry metadata only: an 8-character session-id prefix, the role (runner or viewer), and a timestamp. We do not log IP addresses or any terminal content.

Analytics — on the marketing site only

These public marketing pages load Mixpanel for product analytics: which pages are viewed, the referring link, and coarse device and usage data, kept in your browser’s local storage. Like any web request, Mixpanel receives your IP address (used for approximate location). There is no advertising and no ad-network tracking, and it honors your browser’s “Do Not Track” setting.

Never in the viewer

The terminal viewer (the /s/… pages) loads no analytics and no third-party scripts at all. A tracker there could leak the link’s #fragment secret, so the viewer’s Content-Security-Policy forbids any off-origin script or connection — by design.

Contact

Privacy questions: andrew@dryga.com.