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.
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:
- Website content and browsing activity in this browser. During a session the agent can control every tab in every normal window, including tabs opened later;
chrome://pages, other extensions' pages and the Chrome Web Store are excluded. Through the Chrome DevTools Protocol, the agent can read page content (DOM, accessibility snapshots, screenshots), URLs, and the results of actions it performs, such as clicks and typed text. This data is sent through the relay to our session gateway, which decrypts it and passes it to the agent holding the session link (see session gateway). Nothing is sent when no session is active. - Session and connection data. This is the session token (from which the session keys and routing id are derived) and the relay URL. The token is kept only in
chrome.storage.session, which Chrome clears when the browser closes; the relay URL setting is kept inchrome.storage.localon your computer.
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 IP addresses of the two connecting devices;
- connection times, durations and close reasons;
- the number and size of forwarded messages (byte counts);
- the random routing id that pairs two connections, and the short-lived pairing nameplate (a 4–5 digit number).
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
debugger: drives the browser's tabs during a session, using the Chrome DevTools Protocol. Chrome shows its “rly started debugging this browser” banner whenever an agent is attached.tabs: opens, closes and lists the agent's tabs.tabGroups: keeps agent tabs in a labelled “rly agent” group so you can see them.storage: keeps the session token inchrome.storage.session(cleared when the browser closes) and the relay setting inchrome.storage.local.alarms: keeps the relay connection alive and reconnects.
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
- No analytics, telemetry, advertising or third-party trackers, in the extension or on this website.
- We do not sell, rent or share user data with third parties. We do not use it for advertising, creditworthiness or lending decisions, or for any purpose unrelated to the extension's single purpose.
- We do not transfer data to anyone except the agent holding your session link (extension) or the device you paired (
rly-host, always end-to-end encrypted). - We do not keep, log or inspect page content passing through the session gateway. Temporary files the browser tools create (such as screenshots) are deleted when the session closes.
Storage, retention and deletion
- Extension data lives only on your computer: the session token in
chrome.storage.session, deleted by End session or closing the browser, and the relay setting inchrome.storage.local. Removing the extension deletes all of its data. - The desktop programs store their identity key and paired devices in your user configuration directory (
identity.json,peers.json).rly unpair/rly-host unpair, or deleting that directory, removes it. - The relay and gateway hold no stored user data. Pairing nameplates expire after 10 minutes, channel state disappears when both sides disconnect, and gateway session state is discarded when the session ends or after it is idle.
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.