Relay Data Processing Addendum
Last updated: 14 November 2026
This Data Processing Addendum ("DPA") forms part of the Terms of Service, or any other written agreement for the Service, between Relay Technologies Pte. Ltd., a company registered in Singapore (UEN 202652272N) whose address is 20A Tanjong Pagar Road, Singapore 088443 ("Relay"), and the Customer named in that agreement ("Customer"). It applies whenever Relay processes Customer Personal Data on Customer's behalf.
1. Definitions
1.1 Capitalised terms that this DPA does not define have the meanings given in the Terms of Service. In this DPA:
- (a) "Agreement" means the Terms of Service, or other written agreement for the Service between Relay and Customer, together with every Order Form and this DPA.
- (b) "Customer Personal Data" means personal data in Customer Data that Relay processes on Customer's behalf under the Agreement.
- (c) "Data Protection Laws" means all laws on the protection of personal data that apply to a party's processing of Customer Personal Data under the Agreement, including Singapore's Personal Data Protection Act 2012 (the "PDPA").
- (d) "Data Subject" means an identified or identifiable individual to whom Customer Personal Data relates.
- (e) "Data Subject Request" means a request from a Data Subject to exercise a right under Data Protection Laws, such as a request for access to, correction of or deletion of their personal data.
- (f) "Instructions" has the meaning given in Section 4.2.
- (g) "Personnel" means Relay's employees and individual contractors.
- (h) "personal data" has the meaning given in the applicable Data Protection Laws, and "process" and "processing" mean any operation performed on personal data, including collection, use, storage, disclosure, transfer and deletion.
- (i) "Regulator" means a public authority with authority over a party's processing of personal data, or over Customer's business.
- (j) "Security Incident" means a breach of security that leads to the accidental or unlawful destruction, loss or alteration of, or unauthorised access to, disclosure, copying, use or modification of, Customer Personal Data while Relay or its Subprocessors process it.
- (k) "Subprocessor" means a third party that Relay engages to process Customer Personal Data on Relay's behalf.
- (l) "Subprocessors page" means the page at relayos.so that lists Relay's Subprocessors.
2. Scope and roles
2.1 Roles. Customer is the controller of Customer Personal Data, and the organisation responsible for it under the PDPA. Relay is a processor of Customer Personal Data, acting as Customer's data intermediary under the PDPA.
2.2 Description. Annex 1 describes the processing.
2.3 Relay's own data. Relay is responsible on its own account, and not as Customer's processor, for Usage Data and for contact details of Customer's administrators that Relay uses to manage Customer's account. The Privacy Policy governs that processing, and this DPA does not.
3. Customer's obligations
3.1 Customer is responsible for:
- (a) the lawfulness of Customer Personal Data and of its Instructions;
- (b) giving Data Subjects any notice, and obtaining any consent, that Data Protection Laws require for Relay to process Customer Personal Data under the Agreement; and
- (c) the settings it chooses in its Workspace, including which Authorised Users and AI Agents may see which data, and which Connected Services it connects.
3.2 If Customer turns on speaker recognition in its Workspace, Relay will create a Voiceprint of a Data Subject only after that Data Subject has given express consent through the Service. A "Voiceprint" is a set of numbers, derived from recordings of a person's voice, that describes how that person's voice sounds.
4. Processing on Customer's Instructions
4.1 Instructions only. Relay will process Customer Personal Data only on Customer's Instructions, unless the law requires otherwise. Where the law requires other processing, Relay will tell Customer before it processes, unless the law forbids Relay to do so.
4.2 What the Instructions are. Customer's Instructions are:
- (a) the Agreement;
- (b) Customer's use and configuration of the Service, including the settings its administrators choose and the work its Authorised Users and AI Agents ask the Service to do; and
- (c) any other written instruction that Customer gives and Relay accepts in writing.
4.3 Unlawful Instructions. Relay will tell Customer promptly if, in Relay's opinion, an Instruction breaches Data Protection Laws. Relay need not follow that Instruction until Customer confirms or changes it.
4.4 Restrictions. Relay will not:
- (a) sell Customer Personal Data;
- (b) use Customer Personal Data for advertising;
- (c) use Customer Personal Data to train, or to help train, any AI model, whether Relay's own or a third party's; or
- (d) process Customer Personal Data for any purpose other than providing the Service to Customer, keeping it secure, and complying with the law.
5. Confidentiality of Personnel
5.1 Relay will ensure that every person it authorises to process Customer Personal Data is bound by a duty of confidentiality, whether by contract or by law.
5.2 Access to Relay's production systems is limited to Relay's founder and Relay's own automated agents, as Annex 2 describes. They access Customer Personal Data only to:
- (a) provide the Service or support that Customer requests;
- (b) keep the Service secure, including investigating a bug or abuse; or
- (c) comply with the law.
6. Security
6.1 Measures. Relay will implement and maintain the technical and organisational security measures described in Annex 2. They are designed to protect Customer Personal Data against Security Incidents, at a level appropriate to the risk of the processing.
6.2 Updates. Relay may update the measures in Annex 2 from time to time, provided that the updates do not materially reduce the overall protection of Customer Personal Data.
6.3 Customer's part. Customer is responsible for using the Service securely, including managing its Authorised Users and their access, protecting sign-in details, and choosing the permissions it gives its AI Agents.
7. Subprocessors
7.1 Authorisation. Customer authorises Relay to engage Subprocessors. The Subprocessors at the date of this DPA are listed on the Subprocessors page and in Annex 3.
7.2 Subprocessor terms. Before a Subprocessor processes Customer Personal Data, Relay will put in place written terms with it that:
- (a) require it to protect Customer Personal Data to a standard appropriate to the processing it carries out; and
- (b) are consistent with Relay's obligations under this DPA.
7.3 Responsibility. Relay remains responsible to Customer for its Subprocessors' performance of Relay's obligations under this DPA.
7.4 Notice of changes. At least 30 days before a new or replacement Subprocessor starts to process Customer Personal Data, Relay will:
- (a) update the Subprocessors page; and
- (b) notify Customer's administrators by email.
7.5 Objection. Customer may object to a new or replacement Subprocessor on reasonable grounds relating to data protection, by written notice to Relay within the 30-day notice period. The parties will then discuss Customer's concerns in good faith.
7.6 If an objection is not resolved. If the parties cannot resolve Customer's objection within the 30-day notice period, Customer may terminate the affected part of the Service by written notice before the change takes effect. Relay will then refund any Fees that Customer has paid in advance for that part of the Service for the period after termination.
8. Assistance
8.1 Data Subject Requests. If Relay receives a Data Subject Request about Customer Personal Data, Relay will refer the Data Subject to Customer and tell Customer of the request, unless the law forbids it. Relay will not respond to the request itself, except to confirm that it has referred the request to Customer.
8.2 Tools and help. The Service lets Authorised Users see and correct most of their profile, and Customer may obtain a copy of Customer Data under Section 10.1. Where Customer cannot answer a Data Subject Request with those means, Relay will give Customer reasonable assistance to answer it.
8.3 Assessments and Regulators. Relay will give Customer the information it reasonably needs, taking into account the nature of the processing and the information available to Relay, to:
- (a) carry out a data protection impact assessment of its use of the Service; and
- (b) consult a Regulator about it.
8.4 Cost. Relay provides the assistance in this Section 8 without additional charge, except where a request goes beyond what the Service's features and Relay's ordinary support provide. In that case, Relay will agree any charge with Customer in advance.
9. Security Incidents
9.1 Notice. Relay will notify Customer of a Security Incident without undue delay, and in any event within 48 hours after Relay becomes aware of it.
9.2 Content of the notice. Relay's notice will describe, as far as Relay then knows:
- (a) the nature of the Security Incident, including the categories and approximate number of Data Subjects and records concerned;
- (b) the likely consequences of the Security Incident; and
- (c) the measures Relay has taken or proposes to take to address it and reduce its effects.
Where Relay cannot give all of this information at once, it will give it in stages without undue delay.
9.3 Cooperation. Relay will take reasonable steps to contain and investigate the Security Incident, keep Customer informed of material developments, and give Customer reasonable cooperation so that Customer can meet its own obligations, including any obligation to notify a Regulator or affected individuals.
9.4 Notices to others. Customer decides whether to notify a Regulator or affected individuals of a Security Incident. Relay will not notify them on Customer's behalf unless Customer asks it to, or the law requires Relay to do so.
9.5 No admission. Relay's notice of a Security Incident is not an admission of fault or liability.
10. Return and deletion of Customer Personal Data
10.1 Copy of Customer Data. On Customer's request, Relay will provide Customer with a copy of Customer Data, including Customer Personal Data, in a commonly used machine-readable format within 30 days of the request. Customer may make this request during the Agreement and within 30 days after it ends.
10.2 Deletion after the Agreement ends. When the 30-day period in Section 10.1 ends, Relay will delete Customer Personal Data, and ensure that its Subprocessors delete it, 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.
10.3 Security and access logs. After that deletion, Relay keeps only its security and access logs, for as long as the law and the security of the Service need them. Relay continues to apply this DPA to any Customer Personal Data in those logs while it holds them.
10.4 Earlier deletion. Customer may ask Relay to delete Customer Personal Data earlier. Relay will delete it, and ensure that its Subprocessors delete it, within 30 days of the request, except for data that the law requires Relay to keep.
10.5 Data the law requires Relay to keep. Relay will continue to protect any data it is required to keep, and will process it only for the purpose for which the law requires it to be kept.
10.6 Confirmation. On Customer's request, Relay will confirm in writing that it has completed the deletion.
11. Information and audits
11.1 Information. Relay will make available to Customer the information reasonably necessary to show that Relay complies with this DPA, including answers to Customer's reasonable written security questionnaires.
11.2 Reports. At the date of this DPA, Relay does not hold any independent security certification or audit report. Relay is preparing for an independent SOC 2 audit. When Relay obtains an independent audit report, it will make the report available to Customer on request, under a duty of confidentiality.
11.3 Audit. If the information under Sections 11.1 and 11.2 is not enough to show that Relay complies with this DPA, Customer may audit Relay's compliance, itself or through an independent auditor, on the following conditions:
- (a) Customer gives Relay at least 30 days' written notice, and the parties agree the scope, timing and duration of the audit in advance;
- (b) the audit takes place during normal business hours and does not unreasonably disrupt Relay's operations;
- (c) the auditor is bound by a duty of confidentiality and is not a competitor of Relay;
- (d) the audit does not give access to other customers' data, or to Relay information that is unrelated to Customer Personal Data;
- (e) Customer audits no more than once in any 12 months, unless a Security Incident affecting Customer Personal Data has occurred or a Regulator requires the audit; and
- (f) each party bears its own costs of the audit.
11.4 Regulators. Where a Regulator with authority over Customer requires information about, or access to, Relay's processing of Customer Personal Data, Relay will cooperate with the Regulator and with Customer to the extent the law requires.
12. Location and international transfers
12.1 Hosting location. Relay hosts Customer's Workspace, including its AI Agents, on Amazon Web Services in Singapore, unless the Agreement names another region. Relay keeps its backups in Singapore.
12.2 Transfers. Some Subprocessors process Customer Personal Data outside Singapore, as the Subprocessors page shows. Customer authorises those transfers.
12.3 Protection. When Relay or a Subprocessor transfers Customer Personal Data out of Singapore, Relay will ensure that the recipient is bound by legally enforceable obligations to protect the data to a standard comparable to the protection under the PDPA.
12.4 Other laws. Where the Data Protection Laws of another country, such as those of the European Economic Area, the United Kingdom or Switzerland, require a specific transfer mechanism, the parties will on Customer's request put that mechanism in place, such as the European Commission's Standard Contractual Clauses.
13. Liability
Each party's liability arising out of or in connection with this DPA is subject to the limitations and exclusions of liability in the Agreement, including the Data Protection Cap.
14. Term, changes and precedence
14.1 Term. This DPA applies for as long as Relay processes Customer Personal Data, including after the Agreement ends.
14.2 Changes. Relay may change this DPA. If a change is material, Relay will notify Customer's administrators at least 30 days before it takes effect. A change will not reduce the overall protection of Customer Personal Data, unless the law requires it.
14.3 Precedence. If this DPA conflicts with the Terms of Service on the processing of Customer Personal Data, this DPA prevails.
Annex 1: Description of the processing
Subject matter. Relay's provision of the Service to Customer.
Duration. The term of the Agreement and up to 60 days after it ends, followed by the time it takes backups to expire (Section 10.2). Security and access logs are kept for as long as the law and the security of the Service need them (Section 10.3).
Nature of the processing. Hosting, storage, backup, transmission, display, search, generation of Output by AI models, delivery of notifications, copying on request and deletion. Where Customer's Workspace has calls: transcription of calls, spoken replies from AI Agents, reading of shared screens by AI Agents, and generation of minutes.
Purpose. To provide the Service to Customer under the Agreement and Customer's Instructions, to keep the Service secure, and to comply with the law.
Categories of Data Subjects.
- (a) Customer's Authorised Users.
- (b) Individuals whose personal data appears in Customer Data, such as Customer's clients and contacts, other participants in calls, attendees of calendar events, people who send email to an address Customer gives an AI Agent, and people in chats Customer brings in from Connected Services.
Categories of personal data.
- (a) Account and profile data: name, nickname, email address, photo, time zone, role, job title, team, manager and start date and, if added, phone number, pronouns, a short bio and other optional details.
- (b) Content: messages, files, pages, sheets, decisions, records, email received by AI Agents, and content brought in from Connected Services.
- (c) Calls, where Customer's Workspace has them: call audio, images of shared screens, transcripts, recordings and minutes.
- (d) Calendar data: event times, titles, locations, join links, attendees (with names, email addresses and responses), organisers, and busy status.
- (e) Usage, device and security data: sign-in, failed sign-in and sign-out records with IP address and browser; records of file access, searches and changes in the Workspace; and the devices on which notifications are turned on.
- (f) Voiceprints, only where Customer has turned on speaker recognition and the Data Subject has given express consent (Section 3.2). At the date of this DPA, speaker recognition is not offered to Customer Workspaces.
Sensitive data. Customer decides what content it puts in the Service. The Service does not require sensitive personal data, except Voiceprints under Section 3.2, which are biometric data.
Frequency. Continuous, for as long as Customer uses the Service.
Annex 2: Security measures
Relay maintains the following measures at the date of this DPA.
1. Separation of customers. Each Customer's Workspace has its own database, its own file storage and its own configuration.
2. Encryption.
- (a) Data in transit is encrypted with TLS. Connections to the database require TLS.
- (b) Files in Relay's object storage are encrypted at rest with server-side AES-256 encryption.
- (c) Passwords are stored only as hashes.
- (d) Secrets, including the keys and tokens that connect a Workspace to Connected Services, are encrypted by the application before they are stored. The key for a Customer's company-wide Google Calendar connection is also kept out of the Workspace's change record.
3. Access control.
- (a) Access to a Workspace is limited to the Authorised Users and AI Agents that Customer allows, with the roles and permissions Customer's administrators set.
- (b) Authorised Users sign in with a link sent by email, a password, Google sign-in or, where Customer chooses, a code sent through Lark. Google sign-in works only for an existing account and only for an address in Customer's own Google Workspace domain.
- (c) Session cookies are set as HttpOnly and SameSite=Lax.
- (d) AI Agents act only within the permissions Customer gives them.
- (e) Relay's production servers are reachable only over a private network, using ssh keys held on devices Relay controls. Ssh is closed to the public internet.
- (f) Access to Relay's cloud account goes through AWS IAM Identity Center, and activity on the cloud account's programming interfaces is logged.
- (g) Access to production systems is limited to Relay's founder and Relay's own automated agents.
4. Logging and accountability.
- (a) Every sign-in, failed sign-in and sign-out is recorded with its IP address and browser.
- (b) Every change in the Workspace is recorded with who made it, when, and the earlier and new values.
- (c) Each opening of a file is recorded with the IP address used.
- (d) Each time an AI Agent reads a colleague's calendar, Relay records which AI Agent read whose calendar, and for which days.
- (e) Accounts are deactivated rather than deleted, so their history remains accountable.
- (f) An Authorised User's phone number is kept out of the change record.
5. Data minimisation.
- (a) Usage records note which screens are opened and which named controls are pressed, never what a person types.
- (b) The Service does not include third-party analytics or error-tracking software.
- (c) Relay never shows event join links or event descriptions from a person's calendar to colleagues or AI Agents.
6. Components Relay runs itself. The search index and the real-time messaging service run on servers that Relay operates, not on a third-party service.
7. AI Providers. Relay uses AI Providers only under terms that do not allow them to train their models on Customer Data.
8. Backups.
- (a) Snapshots of Relay's servers are taken daily, and the latest 7 are kept.
- (b) The database is backed up automatically, with point-in-time restore over the last 7 days.
- (c) Files are versioned, so earlier versions are kept. A discarded call recording is removed after 7 days.
- (d) All backups are kept in Singapore.
9. Incident response. Relay handles Security Incidents as Section 9 describes.
10. Certification. Relay does not hold any independent security certification at the date of this DPA. It is preparing for an independent SOC 2 audit (Section 11.2).
Annex 3: Subprocessors
The Subprocessors page lists each Subprocessor, what it does for Relay, what data it receives, and its location. At the date of this DPA, Relay's Subprocessors are Anthropic, OpenAI, Tavily, Google, Apple, Amazon Web Services and Resend. Changes follow Section 7.