Relay Subprocessors
Last updated: 14 November 2026
1. About this page
1.1 Relay Technologies Pte. Ltd. ("Relay") engages the third parties below to process Customer Data on its behalf in providing the Relay service (the "Service"). Each of them is a "Subprocessor". Each Subprocessor receives only the data it needs for its task.
1.2 Capitalised terms not defined here have the meanings given in Relay's Terms of Service and Data Processing Addendum (the "DPA"), both published at relayos.so.
1.3 Relay puts written terms in place with each Subprocessor before it processes Customer Data, and remains responsible for each Subprocessor's performance of Relay's obligations under the DPA.
2. Current Subprocessors
| Subprocessor | What it does for Relay | What it receives | Location |
|---|---|---|---|
| Anthropic | Powers AI Agents and ranks search results. Where a Workspace has calls, also writes call minutes, answers questions during calls and, in one of the two voice modes, looks at shared screens | The messages, emails, files, transcripts and calendar details an AI Agent is given; search words, with excerpts of the files being ranked; in that voice mode, an image of a shared screen with each request | United States |
| OpenAI | Where a Workspace has calls: transcribes calls, produces spoken replies and, in the default voice mode, looks at shared screens | Call audio; the text that is spoken back; in the default voice mode, an image of a shared screen when the AI Agent looks at it | United States |
| Tavily | Runs web searches that an AI Agent makes during a call | The search words only | United States |
| Google sign-in, Google Calendar connections, and notifications to Android phones | Google sign-in details; calendar data, if a calendar is connected; notification text | Global (Google data centres) | |
| Apple | Notifications and call alerts to iPhones | Notification text | Global (Apple data centres) |
| Amazon Web Services | Hosting and file storage | Workspace data | Singapore, unless the Customer's agreement names another region |
| Resend | Sends sign-in links and notices by email | The recipient's email address and the message | United States |
3. Notes on particular Subprocessors
3.1 AI Providers. Anthropic and OpenAI provide their services to Relay under terms that do not allow them to train their models on Customer Data. OpenAI may keep data it receives in abuse monitoring logs for up to 30 days, or longer where the law requires it or where it is reasonably necessary to protect OpenAI's services or others from harm.
3.2 Tavily. Tavily may use the search words it receives to improve its search.
3.3 Google. Relay's handling of data it receives from Google APIs is described in Section 10 of the Privacy Policy, including Relay's commitment to Google's Limited Use requirements.
4. Services that are not Relay's Subprocessors
4.1 Connected Services. A Customer may connect other services to its Workspace, such as Lark, WhatsApp, GitHub or Xero. The Customer chooses those services, and they process data under their own terms with the Customer. They are not Relay's Subprocessors.
4.2 Browser notifications. If an Authorised User turns on notifications in a web browser, the notifications pass through the push service run by the maker of that browser, which the user's browser chooses.
4.3 Public content delivery networks. A page built in a Workspace may load code or fonts from public content delivery networks, such as cdnjs, jsDelivr or unpkg. The viewer's browser connects to them directly.
4.4 Components Relay runs itself. The search index and the real-time messaging service run on servers Relay operates. They are not third-party services.
5. Changes to this list
5.1 At least 30 days before a new or replacement Subprocessor starts to process Customer Data, Relay will update this page and notify each Customer's administrators by email.
5.2 A Customer may object to a new or replacement Subprocessor on reasonable grounds relating to data protection, within that 30-day period, as Section 7 of the DPA describes.
5.3 Questions about this list go to privacy@relayos.so.
6. Change history
| Date | Change |
|---|---|
| 14 November 2026 | First published as a separate page. |