Subprocessors
Last updated November 20, 2026
Relay is operated by Trey Hulse LLC. To provide Relay we use the service providers below to process information on our customers' behalf. Each one receives only what it needs to do the job described. Relay is hosted in the United States, and these providers store and process customer information there. The Privacy Policy explains what Relay collects and why.
Used for every organization
| Provider | What it does for Relay | Information it handles |
|---|---|---|
| Vercel | Hosts the Relay application and runs agents, including the isolated sandbox where agents run code. | Everything Relay processes passes through it. |
| Neon | Database. | Accounts, conversations, agent configurations, activity and usage records, and encrypted connection credentials. |
| Microsoft Azure | File storage (Azure Blob Storage). | Files you attach and files agents create. |
| Resend | Delivers Relay's own email, such as sign-in codes, invitations and notifications. | Your email address and the content of the emails Relay sends you. |
| OpenRouter | Routes requests to the AI model an agent uses. | The messages, files and tool results in a conversation, sent to produce the agent's reply. |
| ClickHouse | Usage analytics. | A copy of activity and usage records: which agents ran, when, the tools they used, their cost, and the details recorded for each step. |
AI model providers
Each agent runs on one AI model, chosen when the agent is set up. A conversation is sent only to the provider of the model that agent uses, through OpenRouter. Relay instructs OpenRouter, on every request, to use only providers that do not train on what they are sent. Your organization can see and change the model for each agent. It can also add a model provider of its own; conversations with agents that use it go to that provider directly, under the terms your organization has with it, and Relay's no-training routing does not apply to them.
| Provider | What it does for Relay | Information it handles |
|---|---|---|
| Anthropic | AI models (Claude). | The conversation content sent to the model. |
| OpenAI | AI models, and the embeddings behind memory and file search. | The conversation content or text sent to the model. |
| AssemblyAI | Speech-to-text, when you dictate a message. | The audio you record. |
| AI models. | The conversation content sent to the model. |
Used only with certain features
| Provider | What it does for Relay | Information it handles |
|---|---|---|
| Brave Search | Web searches an agent runs. | The search query. |
| Browserbase | Web browsing an agent does for you. | The pages visited and what the agent enters on them. |
| Apple | Push notifications to the Relay app for iPhone. | Your device's push token and the text of each notification. |
| Stripe | Billing. | The billing contact, organization name and payment details of organizations that pay by card. Stripe collects card details directly; Relay never sees them. |
| Microsoft and Google (sign-in) | Signing in with a Microsoft or Google account. | Your name, email address and profile picture, received from them. |
Services your organization connects
When you or your organization connect a service to Relay, such as a mailbox, a CRM or an accounting system, agents read from and write to it at your direction. Those services are yours, not subprocessors of Relay, and your agreement with each of them applies. The same is true when you connect Relay to another app such as Claude: what you ask for is sent to that app because you asked.
Deletion
When an organization asks us to delete its information, including when it stops using Relay, we complete the deletion within 30 days. Copies held in our providers' backups are removed as those backups expire.
Changes to this list
We update this page before a new subprocessor starts handling customer information. If your organization has a separate agreement with us that sets out a notice period, that agreement applies.
Contact
Trey Hulse LLC · trey@treyhulse.com