Privacy Policy
Last updated November 20, 2026
Relay is operated by Trey Hulse LLC (“we”, “us”). Relay lets people in an organization work with AI agents their organization has set up, on the web at relayagents.co, in the Relay app for iPhone, in the Relay extension for Chrome, and through Relay's connector for Claude. This policy explains what information Relay handles and why.
Who Relay is for
Relay is a business tool. You can only use it as a member of an organization that has invited you, and your organization decides which agents, integrations and data those agents can use. For information your organization controls, your organization's own policies also apply.
What we collect
- Account information: your name, email address and profile picture from the Microsoft or Google account you sign in with, or your email address if you sign in with an emailed code.
- Your conversations and files: the messages you send to agents, their replies, and files you attach, so conversations can continue and agents can work with your documents.
- Connections you authorize: when you connect a service (for example your mailbox or calendar), the access tokens needed to act for you. These are encrypted and are never shown in the app.
- Device information (iPhone app):a push notification token, the app version, your device's name and time zone, and whether the app is open, so we can send approvals and updates at the right time and not while you are already looking at them. Apple receives the push token and the text of each notification in order to deliver it.
- Usage records: which agents ran, when, the tools they used and how much they cost, so your organization can review activity and spending.
- Billing information: for organizations that pay for Relay, the billing contact and payment details. Card details are collected by our payment provider and never reach Relay.
How we use it
- To run the agents you and your organization ask for, and to show you their results.
- To send notifications you need, such as an approval waiting on you, by email and push notification.
- To keep Relay secure, to troubleshoot problems, and to account for usage.
We do not sell your information, use it for advertising, or track you across other companies' apps or websites. We do not use your conversations, files or connected data to train AI models.
Who processes it
We use service providers to run Relay, and share information with them only as needed to provide it. The full list, with what each one does and what it handles, is on our Subprocessors page. In short:
- Vercel (hosting and running agents, including the isolated sandbox where agents run code) and Neon (database).
- Microsoft Azure (file storage) and Resend (delivery of Relay's own email).
- OpenRouter, which routes each conversation to the AI model its agent uses, from Anthropic, OpenAI or Google. OpenAI also produces the embeddings behind memory and file search.
- AssemblyAI (turning your voice into text when you dictate a message).
- ClickHouse (usage analytics), Apple (push notifications) and Stripe (billing).
- Brave Search (web searches an agent runs) and Browserbase (web browsing an agent does for you).
- Microsoft and Google, when you sign in with them.
Messages sent to an AI model are used to produce the agent's response. On every request, Relay instructs OpenRouter to use only providers that do not train on what they are sent; beyond that, the model's provider handles them under its own terms. If your organization adds an AI model provider of its own, conversations with agents that use it go to that provider under the terms your organization has with it, and Relay's no-training routing does not apply to them. Agents only act on external services you or your organization have connected; those services are yours, and what an agent sends them is sent at your direction. The same applies when you connect Relay to another app such as Claude.
Relay is hosted in the United States, and our providers store and process your information there. When we add a provider, we list it on the Subprocessors page before it starts handling your information.
Google user data
When you connect your Google account in Relay (under Connections), you choose what it may access. Relay only asks for the access a feature needs, and you can add or remove access at any time.
- Gmail: reading the messages and threads an agent looks up for you, and sending the email you ask for.
- Google Calendar: creating and changing the events you ask for.
- Google Drive, Docs, Sheets and Slides: finding and reading the files an agent works with for you, and creating or editing the documents, spreadsheets and presentations you ask for.
How it is used.Relay uses Google user data only to do what you ask of an agent and to show you the result in your conversation. The data an agent reads is sent to the AI model that produces its reply, and is kept in that conversation's history and activity log so you and your organization can see what the agent did. Relay does not use Google user data for advertising, does not sell it, and does not use it to develop, improve or train generalized AI or machine learning models.
Who sees it. Google user data is shared only with the service providers listed above, and only to provide the feature you are using. People at Relay do not read it, except with your permission, when needed for security or to investigate abuse, to comply with the law, or when it has been aggregated and anonymized for internal operations.
Stopping and deleting.Switching Google off under Connections stops agents from using it immediately. Disconnecting it deletes the stored access tokens. You can also remove Relay's access at myaccount.google.com/permissions. To have Google data removed from your conversation history and activity logs, email us and we will delete it within 30 days.
Relay's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Relay for Chrome
The Relay extension for Chrome puts your Relay chat in Chrome's side panel and lets your agent work in your browser when you ask it to. It uses the Relay account you are signed in to in that Chrome profile.
- Tabs:when you send a message, the extension includes the title and address of your active tab and how many tabs you have open, so the agent knows what “this page” means. The agent can list, open, group, move and close tabs when you ask.
- Page content:the agent reads the text and controls of a page, or clicks and types on it, only after you allow that site in the side panel. You can allow a site once or always, and remove sites in the extension's settings. Password fields are never read.
- Browsing history: searched only when you ask the agent to find something you visited, and only the matching entries are sent.
- Chrome profile email:shown in the extension's settings and given to the agent so it knows which browser profile it is working in.
What the extension reads is sent to Relay only as part of your conversation, is handled like the rest of your conversation as described above, and is kept in that conversation's history. The extension does not collect anything in the background. Its use of this data is limited to the features described here: it is not sold, used for advertising or credit decisions, or used to train AI models, and people at Relay do not read it except as described under Google user data above.
Keeping and deleting your information
We keep your information while your account or organization is active. You can delete any conversation yourself in Relay. To delete your account, or to ask what we hold about you, email trey@treyhulse.com. Your organization may keep its own records of work done for it.
An organization can ask us for a copy of its information, or to delete it, at any time, including when it stops using Relay. We complete a deletion request within 30 days. Copies held in our providers' backups are removed as those backups expire.
Security
Information is encrypted in transit. Credentials for connected services are additionally encrypted by Relay before they are stored, and are never shown in the app or sent to an AI model. Our database and file storage providers encrypt what they hold at rest. Each organization's information is logically separated from every other organization's. Decisions made from the iPhone app require Face ID or your passcode.
Children
Relay is not intended for children and we do not knowingly collect information from anyone under 16.
Changes
If we change this policy we will update the date above, and tell you in the app for significant changes.
Contact
Trey Hulse LLC · trey@treyhulse.com