Legal

Privacy policy

Effective date: 19 November 2026

This policy covers the rly — remote browser for AI agents Chrome extension (“the extension”), the rly, rly-host and rly-relay programs, and the public relay and session gateway at rly.ems.works operated by EMS Works (“we”). It explains what data is handled and where it goes.

Summary. Extension sessions are not end-to-end encrypted. While an extension session is active, page content and DevTools (CDP) traffic of the controlled browser pass through our gateway server at rly.ems.works, which decrypts them to run the agent's browser tools. We do not store or log that content. With rly-host and rly pair, browser content is sent only to the device you paired and is end-to-end encrypted; our relay forwards that ciphertext and cannot read it. We have no analytics or tracking, we do not sell data, and the extension stores its data only on your computer.

What the extension handles

The extension exists to let an AI agent you choose control this browser during a session you start. To do that, it handles:

While a session is active, page content handled by the agent passes through our gateway server in decrypted form. We do not store or log it, and we never receive your browsing history, cookies or credentials outside what the agent requests during a session.

Extension session gateway

The session link the extension creates (https://rly.ems.works/mcp/rly_…) is served by our gateway. The gateway derives the session keys from the token in the link, completes an encrypted Noise handshake with your browser through the relay, and runs the agent's browser tools (@playwright/mcp) on our server. It therefore sees page content and CDP traffic in plaintext while the session is active. It processes that data only to answer the agent and does not log it. Files the browser tools produce, such as screenshots, are written to a temporary directory for that session, which is deleted when the session closes. Its logs contain only the first 6 characters of the routing id, never the token, and the web server keeps no access log. The session stops when you click End session, close the browser, or click Cancel on Chrome's debugging banner; the gateway closes its side when the browser stays disconnected for 2 minutes or the session is idle for 30 minutes.

End-to-end encryption (rly-host and rly CLI)

When you pair rly-host with rly, the two devices run a SPAKE2 password-authenticated key exchange with the one-time pairing code, and each pins the other's public key. Every later session uses the Noise protocol (Noise_KK_25519_ChaChaPoly_BLAKE2s) between those two devices only. Private keys never leave the device that generated them. The relay never has them, so it cannot decrypt the traffic it forwards. This does not apply to extension sessions, which end at our gateway.

What the relay operator can see

If you use our public relay at rly.ems.works, EMS Works can technically observe the following, and nothing more:

The relay process never sees plaintext: no URLs, page content, screenshots, keystrokes or pairing words. (For extension sessions, the separate gateway described above does.) It keeps connection state in memory only. Its operational logs record client IP, route, a truncated routing id (first 6 characters), byte counts and close reasons. We use them only to operate the service, prevent abuse and debug, and they are kept in size-capped rotating files (at most 50 MB in total), so older entries are deleted automatically. The web server keeps no access log for relay traffic.

You can avoid our relay entirely by running your own rly-relay with rly-host and pointing both devices at it.

Extension permissions

The extension has no content scripts and requests no host permissions. It connects only to the relay you choose (by default https://rly.ems.works) over a WebSocket. End session in the popup stops all agent access at once.

What we don't do

Storage, retention and deletion

This website

rly.ems.works serves static pages and downloads without cookies, analytics, external fonts or scripts.

Children

rly is a developer tool and is not directed at children under 16.

Changes

If this policy changes, we will update this page and its effective date. If we make a material change to how data is handled, we will also note it in the extension's release notes.

Contact

Send questions or requests about this policy to privacy@ems.works.