Relay – Privacy Policy

Privacy Policy — Relay for AI Agents

Effective date: 08 May 2026
Last updated: 08 May 2026

This policy describes how the Relay for AI Agents browser extension and its companion MCP server (collectively, the “Software”) handle data.

This policy is published at https://letssetyouup.com/relay/privacy-policy and applies to v1.0.0 and later.

TL;DR (in plain English)

  • The Software runs entirely on machines you control. It does not transmit any data to the publisher or to any third-party server.
  • The Software lets an AI agent (e.g. Claude Desktop, Cursor, Cline, opencode, OpenAI Codex CLI) read and control tabs in your browser. While doing that, it can see page contents, screenshots, console logs, and network requests in those tabs — and it sends them to the AI agent you have configured.
  • The publisher receives none of that data.
  • There is no analytics, telemetry, advertising, or tracking.
  • No accounts or signups are required.

1. Who we are

The Software is published by:

Lets Set You Up
Address: Redacted
Email: ari.d@letssetyouup.com
Website: https://letssetyouup.com
Repository: https://github.com/letssetyouup/relay-for-ai-agents

In this document, “we” / “us” / “our” refers to the publisher.

2. What the Software does (in privacy terms)

The Software is two pieces:

  1. A browser extension for Chromium-based browsers.
  2. A local MCP server (Node.js process) that an AI agent host you choose spawns on your computer.

The extension connects to the MCP server over a local WebSocket. The MCP server forwards tool calls from the AI agent host to the extension and returns results. Nothing in this loop touches our servers. We do not operate any backend service for the Software.

3. Data the Software processes

When an AI agent invokes one of the Software’s tools, the following data may flow between the browser, the MCP server, and the AI agent host:

  • Page content — HTML, the accessibility tree, visible text, screenshots of the viewport, and console / network output of tabs the agent operates on.
  • Inputs the agent generates — text it types into fields, the coordinates of clicks, file paths it uploads, JavaScript it evaluates, and the values those evaluations return.
  • Configuration values you set — broker URL, authentication token, session label, session-binding state.

This data is processed in-memory on your machines. It is not stored, logged, or transmitted by us.

4. Data the Software does NOT collect

We do not collect any of the following:

  • Your name, email, address, phone number, or any contact information
  • Your browsing history outside the dedicated “Relay” tab group
  • Cookies, login state, or saved credentials
  • Geographic location
  • Device or hardware identifiers
  • Crash reports, analytics events, or telemetry of any kind
  • Advertising identifiers

We do not use third-party analytics, error tracking, A/B testing, or advertising libraries.

5. Where your data goes

Data flow when the agent uses the Software:
Browser tab content → Browser extension → MCP server (your machine) → AI agent host (machine you chose)

Both endpoints are under your control. No data flows to us.

For local-only setups, every link of this chain stays on a single computer, on the loopback interface (127.0.0.1).

For remote setups (the browser is on a different machine than the AI agent host), traffic flows over a network that you have configured. The Software does not enforce encryption on its own — it speaks plain WebSocket. We strongly recommend running both ends on a private overlay network like Tailscale or another encrypted VPN.

6. Local storage

The browser extension stores the following in the browser’s chrome.storage.local area:

Key Purpose
serverUrl The WebSocket URL of your MCP broker
serverToken The bearer token for that broker (plain text)
boundSessionId Which agent session this browser is locked to (if any)
userDisconnected Whether you’ve manually disconnected
status, sessions, lastError Live UI state for the popup

This data stays on your machine and is never transmitted to us. It can be cleared by removing the extension.

7. Permissions used by the extension

Permission Why
tabs, tabGroups Manage the dedicated “Relay” tab group.
scripting, activeTab Read page content on tabs the agent is operating on.
debugger Send real input events, capture screenshots, and read accessibility trees via DevTools Protocol.
storage Persist your configured broker URL and token locally.
alarms Backup keepalive for the WebSocket connection.
<all_urls> Allows the agent to operate on URLs you direct it to.

8. Third parties

The only third party in the data flow is the AI agent host you choose to install and run. We have no relationship with those hosts and receive nothing from them.

9. Children’s privacy

The Software is a developer tool and is not designed for or directed at children under 13. We do not knowingly collect any data from children.

10. Your rights and choices

Because we do not collect personal data, there is nothing for us to delete or export. To remove all data from your machine:

  1. Remove the extension at chrome://extensions.
  2. Stop and uninstall the MCP server.
  3. Run npx relay-for-ai-agents-setup --remove.

11. International users

We do not transfer your data internationally because we do not transmit your data anywhere. All data stays on machines you control.

12. Security

The Software is open source (MIT) and can be audited at GitHub.

If you discover a security vulnerability, please report it privately by email to ari.d@letssetyouup.com.

13. Changes to this policy

Material changes will be reflected in the “Last updated” date, the project’s CHANGELOG.md, and version release notes.

14. Contact

For privacy-related questions:

Lets Set You Up
Email: ari.d@letssetyouup.com
Website: https://letssetyouup.com
Issues: GitHub Issues