Relay Privacy Policy
Last updated: 14 November 2026
1. Introduction
1.1 This Privacy Policy explains how Relay Technologies Pte. Ltd. collects, uses, discloses and protects Personal Data in connection with the Services.
1.2 Relay Technologies Pte. Ltd. is a company registered in Singapore (UEN 202652272N), whose address is 20A Tanjong Pagar Road, Singapore 088443.
1.3 Relay provides the Services to companies and other organisations. Individuals use Relay at work, in the Workspace of the organisation they work for or with.
1.4 This Policy should be read together with Relay's Terms of Service, Data Processing Addendum and Subprocessors page, all published at relayos.so.
2. Definitions
2.1 In this Policy:
- (a) "AI Agent" means an automated assistant in a Workspace that is powered by an AI model and acts within the permissions its Customer gives it.
- (b) "AI Provider" means a third party whose AI models Relay uses to provide the Services. At the date of this Policy, the AI Providers are Anthropic and OpenAI.
- (c) "Authorised User" means an individual whom a Customer allows to use its Workspace, such as an employee or contractor.
- (d) "Customer" means a company or other organisation that has an agreement with Relay to use the Services.
- (e) "Customer Data" means all data that a Customer, its Authorised Users and its AI Agents put into or create in the Customer's Workspace, including the records the Workspace keeps of activity in it.
- (f) "Google User Data" means data that Relay receives from Google APIs about a person's Google account.
- (g) "PDPA" means Singapore's Personal Data Protection Act 2012.
- (h) "Personal Data" means data, whether true or not, about an individual who can be identified from that data, or from that data and other information to which the holder of the data has or is likely to have access.
- (i) "Relay", "we", "us" and "our" mean Relay Technologies Pte. Ltd.
- (j) "Security Incident" means a breach of security that leads to the accidental or unlawful destruction, loss, alteration, or unauthorised access to, disclosure, copying or use of, Personal Data that Relay holds.
- (k) "Services" means:
- (i) Relay's website at relayos.so;
- (ii) the Relay web application, which each Customer reaches at its own address, such as acme.relayos.so; and
- (iii) Relay's phone and desktop applications.
- (l) "Subprocessor" means a third party that Relay engages to process Customer Data on Relay's behalf.
- (m) "Usage Data" means information about how the Services are used, as described in Section 5.6. Usage Data does not include the content of Customer Data.
- (n) "Voiceprint" means a set of numbers, derived from recordings of a person's voice, that describes how that person's voice sounds.
- (o) "Workspace" means a Customer's own instance of Relay.
- (p) "You" and "your" mean the individual whose Personal Data this Policy concerns.
3. Scope
3.1 This Policy applies to Personal Data that Relay processes in connection with the Services.
3.2 This Policy does not apply to:
- (a) third-party services that a Customer connects to its Workspace, which are governed by their own terms and policies (see Section 9.5); or
- (b) how a Customer uses Personal Data outside the Services.
3.3 If you use Relay through your employer or another organisation, that organisation's own policies also apply to its use of your Personal Data.
4. Relay's two roles
4.1 Relay as data intermediary for Customer Data. Customer Data belongs to the Customer. The Customer decides what goes into its Workspace, who may see it and what its AI Agents may do. Relay processes Customer Data on the Customer's behalf and on its instructions, under Relay's agreement with the Customer, which includes the Data Processing Addendum. For Customer Data, Relay acts as a data intermediary under the PDPA, which other laws call a processor. Requests and questions about Customer Data should go to the Customer first (see Section 14.4).
4.2 Relay as the organisation responsible for its own records. Relay decides how Personal Data is used, and this Policy is Relay's commitment about that use, for:
- (a) Relay's website and waiting list;
- (b) information about Customers' administrators and contacts that Relay uses to manage each Customer's account and to communicate with it; and
- (c) Usage Data that Relay uses to secure, fix and improve the Services.
5. Personal Data we collect
5.1 Account and profile data. When a Customer gives you access to its Workspace, Relay holds:
- (a) your name, nickname, email address, photo, time zone and role;
- (b) the profile details the Customer adds, namely your job title, team, manager and start date and, if added, your phone number, pronouns, a short bio and other optional details you choose to add;
- (c) your password, if you set one, which Relay stores only as a hash; and
- (d) if you sign in with Google, your name, email address, profile photo and the identifier Google assigns to your Google account. Relay never receives or keeps your Google password.
5.2 Profile data from a connected directory. If the Customer connects its Lark account to its Workspace, Relay may import names, photos and profile details from the Customer's Lark directory.
5.3 Content. Customer Data includes the messages, files, pages, sheets, decisions and other records that Authorised Users and AI Agents create or share in the Workspace. It also includes emails sent to an email address the Customer gives an AI Agent, and content that the Customer brings in from services it connects. Content may contain Personal Data about you and about other people, such as the Customer's own clients or contacts.
5.4 Calls and voice. Calls, spoken conversations with AI Agents and call transcription are features that a Workspace may have. Where a Workspace has them:
- (a) call audio is sent to OpenAI to transcribe the call and to produce an AI Agent's spoken replies;
- (b) when an AI Agent looks at a screen that someone shares, an image of that screen is sent to OpenAI or to Anthropic, depending on the voice mode in use;
- (c) when a call is transcribed or recorded, Relay keeps the transcript and the recording, and an AI model writes minutes of the call from the transcript; and
- (d) anyone on the call can discard the transcript while the call is in progress, and the transcript can be removed after the call. Discarding or removing a transcript deletes the transcript and the recording. Where a recording is discarded, its stored copy is fully removed after 7 days. Relay keeps a record of who discarded or removed it and when.
5.5 Voiceprints.
- (a) Relay includes a speaker recognition feature. It creates a Voiceprint of a person from that person's own call audio, so that Relay can tell which person is speaking when several people share one microphone. A Voiceprint is biometric data.
- (b) At the date of this Policy, this feature is not offered to Customer Workspaces.
- (c) If Relay offers the feature to Customers:
- (i) it is used only in a Workspace whose Customer has turned it on;
- (ii) Relay creates a Voiceprint of a person only after that person has given express consent;
- (iii) Relay uses a Voiceprint only to identify who is speaking on calls in that Workspace;
- (iv) Voiceprints are created, matched and stored on servers that Relay operates, and Relay does not send them to any AI Provider; and
- (v) a person may withdraw consent at any time, after which Relay stops using that person's Voiceprint and deletes it.
5.6 Usage, device and security data. When you use the Services, Relay records:
- (a) each sign-in, failed sign-in and sign-out, with the IP address and browser it came from;
- (b) which screens you open and which named buttons and controls you press, but never what you type;
- (c) errors the Services encounter, with the page, IP address and browser involved;
- (d) who opened which file, with the IP address used;
- (e) the searches you run in Relay;
- (f) the devices and browsers on which you turn on notifications, and the information needed to deliver notifications to them;
- (g) when you were last active on the web, desktop and phone applications, and any availability you set; and
- (h) a record of changes in the Workspace: who created, changed or deleted what, and when, with the earlier values. When someone edits or removes a message, this record keeps the earlier version.
5.7 Calendar data. If you connect your calendar, or your Customer connects the calendars of everyone in its organisation, Relay reads your calendar events as described in Section 10.
5.8 Website and waiting list. If you join Relay's waiting list, Relay collects your name, email address and the IP address you signed up from. Relay also records visits to pages of the Services, with the page address, IP address and browser.
6. How we use Personal Data
6.1 Relay uses Personal Data for the following purposes:
- (a) To provide the Services: delivering messages, ringing you when a meeting starts, showing your calendar in Relay, transcribing calls and writing minutes where a Workspace has calls, providing search, and enabling the Customer's AI Agents to do the work they are given.
- (b) To keep the Services secure: detecting sign-ins that should not happen, investigating misuse, and keeping a record of who did what.
- (c) To fix and improve the Services: using error reports and counts of which features are used.
- (d) To communicate with you about your account and about Relay.
- (e) To comply with the law.
6.2 Relay uses Customer Data only to provide the Services to the Customer under its agreement with Relay and its instructions, to keep the Services secure, and to comply with the law.
6.3 Relay does not sell Personal Data and does not show advertising.
6.4 Relay does not use Customer Data or Google User Data to train, or to help train, any AI model, whether Relay's own or a third party's.
6.5 Where the applicable law requires a legal ground for processing Personal Data, Relay relies on the ground that fits the purpose: performing its agreement with the Customer, its legitimate interests in operating and securing the Services, your consent (for example, for a Voiceprint), or a legal obligation. Where the PDPA applies, Relay relies on consent, deemed consent, or an exception the PDPA provides.
7. AI Agents and AI Providers
7.1 AI Agents are part of the Customer's Workspace. An AI Agent can read:
- (a) the content of the rooms and threads it has been added to; and
- (b) content that the people using it ask it to read.
7.2 An AI Agent acts only within the permissions the Customer gives it, and Relay records what it does.
7.3 To produce an answer, summary, transcript, minutes or spoken reply, Relay sends the relevant parts of Customer Data to an AI Provider. Relay sends this data only to produce the output requested.
7.4 The AI Providers' terms for business customers do not allow them to train their models on this data:
- (a) Anthropic's commercial terms state that Anthropic "may not train models on Customer Content from Services".
- (b) OpenAI does not use data sent to its API to train its models unless the customer opts in, and Relay does not opt in. 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.
7.5 When an AI Agent searches the web during a call, Relay sends the search words to Tavily, its web search provider. Tavily may use search words to improve its search.
7.6 Applications you connect yourself. You may connect an AI application of your own, such as Claude Code, to your Relay account. That application can then read and act in Relay with your permissions. What it receives is governed by your arrangement with its provider, not by Relay's agreements with its AI Providers.
8. Pages that load outside content
8.1 A page that someone in a Workspace builds and publishes in Relay may load code or fonts from public content delivery networks, such as cdnjs, jsDelivr or unpkg.
8.2 When you open such a page, your browser connects to those networks directly, and they receive your IP address and browser details.
9. How we disclose Personal Data
9.1 Within the Customer. The Customer's administrators, Authorised Users and AI Agents can see Personal Data in the Workspace to the extent the Customer's settings allow. You control what colleagues see of your calendar, up to the Customer's limit (see Section 10.3).
9.2 Subprocessors. Relay uses Subprocessors to provide the Services. At the date of this Policy they are Anthropic, OpenAI, Tavily, Google, Apple, Amazon Web Services and Resend. Each receives only the data it needs for its task. The Subprocessors page lists what each one does, what it receives and where it is located. Relay gives Customers at least 30 days' notice before adding or replacing a Subprocessor.
9.3 Notifications. Phone notifications pass through Apple's service for iPhones and Google's service for Android phones, which receive the notification text. If you turn on notifications in a web browser, Relay sends them through the push service run by the maker of your browser.
9.4 Email. Relay sends sign-in links and notices by email through its email provider, which receives your email address and the message.
9.5 Connected services. A Customer may connect other services to its Workspace, such as Lark, WhatsApp, GitHub or Xero. Data then moves between Relay and that service as the Customer has set up, under that service's own terms. The Customer, not Relay, decides to make that connection.
9.6 Legal and safety reasons. Relay may disclose Personal Data where the law requires it, or where disclosure is necessary to protect the safety of any person.
9.7 Change of ownership. If Relay Technologies Pte. Ltd. is sold or merged, Personal Data may pass to the new owner, and this Policy will keep applying to it. Google User Data passes only with your explicit prior consent (see Section 10.5).
10. Google User Data
10.1 Google sign-in.
- (a) If you sign in with Google, Relay asks Google for your name, email address and profile photo.
- (b) Where a Workspace has Google calendars turned on, and the Customer has not connected the calendars of everyone in its organisation, the Google sign-in screen also asks for permission to read the events on calendars you own. You can untick that permission and still sign in. If you allow it, your calendar is connected just as if you had connected it from your You page, and Section 10.2 applies.
- (c) Google sign-in works only for a person who already has an account in a Workspace, and only for an address in the Customer's own Google Workspace domain.
10.2 Google Calendar. You can connect your Google calendar from your You page or when you sign in with Google (Section 10.1(b)), or the Customer's Google Workspace administrator can connect the calendars of everyone in its organisation. In each case:
- (a) Relay reads the events on calendars you own: their times, titles, locations and join links, their attendees (with names, email addresses and responses), their organiser, and whether each event shows you as busy;
- (b) Relay can add Relay's own meetings, with their titles, times, attendees' email addresses, locations and notes, to a separate calendar that Relay creates and manages; and
- (c) Relay stores copies of the events it reads. When an upcoming event is removed from your calendar, Relay removes its copy of that event, and when you disconnect your calendar, Relay deletes the events it stored from it.
10.3 How Relay uses Google User Data. Relay uses Google User Data only to:
- (a) sign you in;
- (b) ring you when a meeting starts;
- (c) show your week in Relay; and
- (d) show your colleagues and the Customer's AI Agents when you are busy, or, if you allow it, your events' titles and locations. You choose this level on your You page, up to the limit the Customer sets.
Relay never shows event join links or event descriptions to colleagues or AI Agents. Each time an AI Agent reads a colleague's calendar, Relay records which AI Agent read whose calendar, and for which days.
10.4 Limited Use. 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. The use of information received from Google Workspace scopes will also adhere to the Google Workspace API User Data and Developer Policy, including the Limited Use requirements.
10.5 In particular:
- (a) Relay uses Google User Data only to provide the user-facing features described in Section 10.3, which are prominent in Relay's interface.
- (b) Relay transfers Google User Data only:
- (i) to provide those features, with your consent, including to an AI Provider to answer what you or the Customer's AI Agents ask about your calendar;
- (ii) for security purposes, such as investigating abuse;
- (iii) to comply with applicable law; or
- (iv) as part of a merger, acquisition or sale of Relay's assets, after obtaining your explicit prior consent.
- (c) Relay does not sell Google User Data or transfer it to advertising platforms, data brokers or information resellers. Relay does not use it for advertising, to determine creditworthiness or for lending purposes, or to create, train or improve any AI model.
- (d) No person at Relay reads Google User Data unless:
- (i) Relay has first obtained and documented your explicit consent to view specific data, for example to help you with a support request;
- (ii) it is necessary for security purposes, such as investigating a bug or abuse;
- (iii) it is necessary to comply with applicable law or regulation; or
- (iv) the data, including data derived from it, is aggregated and anonymized and used for internal operations in accordance with applicable privacy and other legal requirements.
10.6 Disconnecting. You can disconnect your Google calendar on your You page at any time. When you do, Relay stops reading your calendar and deletes the events it stored from it. You can also remove Relay's access in the security settings of your Google account, after which Relay can no longer read your calendar.
11. Where data is stored and international transfers
11.1 Customer Workspaces, including their AI Agents, are hosted on Amazon Web Services in Singapore, unless the Customer's agreement names another region. Requests from AI Agents to their AI model go to Anthropic.
11.2 Relay's central systems, which receive Usage Data from each Workspace, pass phone notifications to Apple and Google, and handle sign-up to Relay, also run on Amazon Web Services in Singapore.
11.3 Relay keeps its backups in Singapore.
11.4 Some Subprocessors process data outside Singapore. In particular, the AI Providers process data in the United States. The Subprocessors page lists each Subprocessor's location.
11.5 When Relay transfers Personal Data out of Singapore, it ensures that the recipient is bound to protect the data to a standard comparable to the protection under the PDPA.
12. How long we keep Personal Data
12.1 Customer Data while the Customer uses Relay. Relay keeps Customer Data, including the Workspace's record of who did what and who signed in from where and earlier versions of files, for as long as the Customer's subscription lasts.
12.2 When the subscription ends. For 30 days after the Customer's subscription ends, the Customer may ask Relay for a copy of its Customer Data. Relay then deletes the Customer Data within a further 30 days, including earlier versions of files. Copies in Relay's server snapshots and database backups expire within 7 days after the deletion.
12.3 Security and access logs. After that deletion, Relay keeps only its security and access logs, such as records of sign-ins and of who accessed what, for as long as the law and the security of the Services need them.
12.4 Earlier deletion. A Customer may ask Relay to delete its Customer Data earlier. Relay completes the deletion within 30 days of the request, except for data that the law requires Relay to keep.
12.5 Usage Data. Relay keeps Usage Data, including error reports and records of visits to the Services, as a security record, which protects Customers and Relay if an incident ever has to be investigated.
12.6 Transcripts and recordings. These are kept until someone removes them (see Section 5.4), or until the Customer Data is deleted under this Section 12.
12.7 Waiting list. Relay keeps your waiting list entry until you join Relay or ask Relay to remove you from the list.
13. How we protect Personal Data
13.1 Relay protects Personal Data with security measures that include:
- (a) a separate database for each Customer's Workspace;
- (b) encryption of data in transit, and of files in storage;
- (c) storing passwords only as hashes;
- (d) encrypting the keys that connect a Workspace to other services;
- (e) limiting access to the people and AI Agents the Customer allows;
- (f) recording changes made in each Workspace; and
- (g) daily backups, kept in Singapore.
13.2 No system is perfectly secure. If a Security Incident affects your Personal Data, Relay will notify the Customer as its agreement requires, and will notify you and the relevant authorities where the law requires.
14. Your rights and choices
14.1 In the Services. On your You page you can see and correct most of your profile, turn off meeting rings, disconnect a calendar, and choose what colleagues see of it.
14.2 Requests to Relay. You may ask Relay:
- (a) for a copy of the Personal Data Relay holds about you, and information about how it has been used or disclosed;
- (b) to correct Personal Data about you that is inaccurate or incomplete;
- (c) to stop using Personal Data for a purpose to which you consented, by withdrawing that consent, in which case some features may stop working; and
- (d) to delete Personal Data about you, where Relay is not required to keep it.
14.3 More rights where the law provides them. If you live in a place whose law gives you further rights over your Personal Data, such as some US states, you have those rights too.
14.4 Customer Data. For Personal Data in a Customer's Workspace, contact the Customer first, because the Customer decides how that data is used. If you contact Relay about Customer Data, Relay will refer your request to the Customer and help the Customer respond.
14.5 How to make a request. Write to privacy@relayos.so. Relay responds within 30 days. Relay may need to confirm your identity before it acts on a request.
15. Cookies and similar technologies
15.1 Relay uses only the cookies the Services need to work:
| Cookie | Purpose | How long it lasts |
|---|---|---|
| Session cookie | Keeps you signed in | Until you sign out or the session expires |
| Form protection cookie | Protects your forms against cross-site request forgery | For the session |
Google sign-in cookie (__Host-relay-google-sign-ins) | Holds a Google sign-in while it completes | 15 minutes |
Workspace list cookie (relay_workspaces), on relayos.so | Remembers which Workspaces you use on this browser, so relayos.so can take you back to them | 400 days |
15.2 Relay uses no advertising or tracking cookies, and sets no third-party cookies.
15.3 The Relay application also stores some information in your browser's local storage: drafts, display settings, your microphone and camera choices, frequently used emoji, and a random identifier that groups the usage records of one visit.
16. Children
The Services are for work. They are not intended for anyone under 18, and Relay does not knowingly collect Personal Data from children.
17. Changes to this Policy
17.1 If Relay changes this Policy, it will publish the new version on relayos.so with its date.
17.2 If a change is material, Relay will notify the Customer's administrators before the change takes effect.
18. Contact
18.1 Relay Technologies Pte. Ltd., 20A Tanjong Pagar Road, Singapore 088443.
18.2 Data Protection Officer: privacy@relayos.so.