Syndeo
Privacy PolicyTerms of ServiceSub-processorsDPA

Template pending legal review. This addendum is a template and has not yet been reviewed by counsel. For a signed DPA contact [email protected].

Data Processing Addendum

Last updated 2 October 2026

This addendum sets out how VRS processes personal data on behalf of customers who use Syndeo, as required by Article 28 of the GDPR. Read it together with our Terms of Service, Privacy Policy and Sub-processors list.

Contents

  1. Parties and roles
  2. Subject matter and duration
  3. Nature and purpose of processing
  4. Types of personal data and data subjects
  5. Documented instructions (Art. 28(3)(a))
  6. Confidentiality (Art. 28(3)(b))
  7. Security of processing (Art. 28(3)(c) and Art. 32)
  8. Sub-processors (Art. 28(2) and 28(3)(d))
  9. Assistance with data subject rights (Art. 28(3)(e))
  10. Assistance with security, breaches, DPIAs and consultation (Art. 28(3)(f), Arts. 32 to 36)
  11. Personal data breach notification
  12. Deletion or return at the end of the service (Art. 28(3)(g))
  13. Information and audits (Art. 28(3)(h))
  14. International transfers
  15. Liability
  16. General
  17. Annex I: Details of processing
  18. Annex II: Technical and organisational measures

1.Parties and roles

This Data Processing Addendum (“Addendum”) forms part of the agreement between VRS (vrsjo.com), which operates Syndeo at app.syndeo.cloud (“VRS”, the “processor”), and the organisation that owns a Syndeo workspace (the “Customer”, the “controller”) under our Terms of Service or a separate written agreement (together, the “Agreement”).

For personal data in workspace content (messages, files, recordings, transcripts, customer conversations, contacts and so on) the Customer is the controller and VRS processes it on the Customer's behalf as processor. For account information about the people who use Syndeo (who they are, how they sign in, how they use the service) VRS is a controller, as described in our Privacy Policy, and this Addendum does not apply to it.

Terms such as “personal data”, “processing”, “data subject” and “personal data breach” have the meaning given in the EU General Data Protection Regulation 2016/679 (“GDPR”) and, where it applies, the UK GDPR. If this Addendum conflicts with the Agreement on the processing of personal data, this Addendum wins.

2.Subject matter and duration

VRS processes Customer personal data to provide Syndeo to the Customer under the Agreement. This Addendum lasts as long as VRS processes Customer personal data under the Agreement, and ends when that processing ends and the data has been deleted or returned under section 12.

3.Nature and purpose of processing

VRS hosts, stores, transmits, displays, records, transcribes, summarises, indexes for search, backs up and deletes Customer personal data, only as needed to provide, secure and support the Syndeo features the Customer turns on: team chat, huddles, meetings and recordings, phone, booking and calendar, the shared inbox, the help desk, AI features and the integrations the Customer connects. VRS does not sell Customer personal data, use it for advertising, or use it to train AI models.

4.Types of personal data and data subjects

Data subjects: the Customer's users and guests; the Customer's own customers, contacts and leads; people who email, call, text or message the Customer through Syndeo; meeting participants; people who book through the Customer's booking pages; people invited to the Customer's events.

Personal data: names, email addresses, phone numbers and other contact details; the content of messages, emails, files, tickets and notes; audio and video recordings, transcripts and AI summaries; call, message and meeting metadata; calendar entries and bookings; anything else the Customer chooses to put into Syndeo. Annex I gives the full detail.

Syndeo is not designed for special categories of personal data (GDPR Art. 9) or data about criminal convictions. The Customer decides whether to put such data into Syndeo and is responsible for having a lawful basis to do so.

5.Documented instructions (Art. 28(3)(a))

VRS processes Customer personal data only on the Customer's documented instructions, including for transfers to third countries, unless the law VRS is subject to requires otherwise; in that case VRS will tell the Customer before processing, unless that law forbids it. The Agreement, this Addendum and the Customer's configuration and use of Syndeo (including the settings chosen by its workspace admins) are the Customer's complete instructions. Other instructions must be agreed in writing.

VRS will tell the Customer straight away if it believes an instruction breaks data protection law.

6.Confidentiality (Art. 28(3)(b))

VRS makes sure that everyone it authorises to process Customer personal data is bound by a duty of confidentiality, by contract or by law, and has access only to what they need for their role.

7.Security of processing (Art. 28(3)(c) and Art. 32)

VRS implements and maintains appropriate technical and organisational measures to protect Customer personal data against accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access, taking into account the state of the art, the cost of implementation and the nature, scope, context and purposes of processing. The measures in place are listed in Annex II. VRS may update them as long as the overall level of protection is not reduced.

8.Sub-processors (Art. 28(2) and 28(3)(d))

The Customer gives VRS prior general authorisation to engage sub-processors. The sub-processors in use are listed on our Sub-processors page, which the Customer accepts by entering into this Addendum.

  • Notice. VRS will update the Sub-processors page and tell the Customer's workspace owners in Syndeo or by email at least 30 days before a new sub-processor starts processing Customer personal data.
  • Right to object. The Customer may object on reasonable data protection grounds by emailing [email protected] within that notice period. VRS will then work with the Customer in good faith to find a solution, such as not using that sub-processor for the Customer's data. If none is found, the Customer may end the affected part of the service without penalty.
  • Same obligations. VRS imposes on each sub-processor, by written contract, data protection obligations that give at least the same protection as this Addendum, and remains responsible to the Customer for each sub-processor's performance of those obligations.

Providers the Customer or its users choose to connect (for example Google, Microsoft, Zoom, Zoho, Freshdesk, Atlassian, HubSpot, Telegram or Meta) receive data on the Customer's instruction when the connection is made; the Customer's own agreement with that provider also applies.

9.Assistance with data subject rights (Art. 28(3)(e))

Taking into account the nature of processing, VRS helps the Customer, by appropriate technical and organisational measures and as far as possible, to answer requests from data subjects exercising their rights under Chapter III GDPR. Workspace admins can export or erase a contact's information directly in Syndeo. If VRS receives a request about Customer personal data, it will pass it to the Customer without undue delay and will not answer it except on the Customer's instruction.

10.Assistance with security, breaches, DPIAs and consultation (Art. 28(3)(f), Arts. 32 to 36)

Taking into account the nature of processing and the information available to it, VRS helps the Customer meet its obligations under Articles 32 to 36 GDPR: security of processing, notifying personal data breaches to supervisory authorities and data subjects, data protection impact assessments and prior consultation with supervisory authorities.

11.Personal data breach notification

VRS will notify the Customer without undue delay after becoming aware of a personal data breach affecting Customer personal data. The notice goes to the workspace owners by email and will describe, as far as then known, the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, and the measures taken or proposed to address it and reduce its effects. Where not all of this is known at once, VRS will provide it in phases as it becomes available.

VRS will take reasonable steps to contain and investigate the breach. A notice from VRS is not an admission of fault or liability.

12.Deletion or return at the end of the service (Art. 28(3)(g))

When the Agreement ends, the Customer can ask VRS to export its data or delete it. At the Customer's choice, VRS will return Customer personal data in a structured, machine-readable format and/or delete it, completing deletion within 30 days, unless the law requires VRS to keep it. Deleted data can remain in encrypted backups for a short period until those backups are overwritten, and stays protected by this Addendum until then.

13.Information and audits (Art. 28(3)(h))

VRS makes available to the Customer the information needed to demonstrate compliance with Article 28 GDPR, and allows for and contributes to audits, including inspections, by the Customer or an auditor it mandates. Audits are carried out on reasonable written notice (at least 30 days unless a supervisory authority requires otherwise), during business hours, no more than once a year unless required by a supervisory authority or following a personal data breach, and under a duty of confidentiality. VRS may first answer with written information, such as responses to a security questionnaire, where that reasonably meets the purpose of the audit. Each party bears its own costs.

14.International transfers

VRS's servers are in EU data centres. Some sub-processors process data in the United States or on a global network, as shown on the Sub-processors page. Where Customer personal data is transferred to a country without an adequacy decision, VRS makes sure the transfer is covered by an appropriate safeguard, in particular the European Commission's Standard Contractual Clauses (Decision 2021/914), with the UK International Data Transfer Addendum where UK data is concerned, or the provider's certification under an applicable adequacy framework such as the EU-US Data Privacy Framework. Where VRS itself receives Customer personal data from the EEA in a country without an adequacy decision, the Standard Contractual Clauses (Module Two, controller to processor) are incorporated into this Addendum by reference, with Annexes I and II below completing their appendix.

15.Liability

Each party's liability arising from this Addendum is subject to the exclusions and limits in the Limitation of liability section of the Terms of Service (or the Customer's separate agreement with VRS), except where the law does not allow liability to be limited.

16.General

This Addendum is governed by the law that governs the Agreement, except where data protection law or the Standard Contractual Clauses require otherwise. A signed copy of this Addendum is available on request from [email protected].

17.Annex I: Details of processing

ControllerThe Customer (the organisation that owns the Syndeo workspace); contact: its workspace owners.
ProcessorVRS (vrsjo.com), operator of Syndeo at app.syndeo.cloud; contact: [email protected].
Data subjectsThe Customer's users and guests; its customers, contacts and leads; people who email, call, text or message it through Syndeo; meeting participants; people who use its booking pages or are invited to its events.
Categories of personal dataIdentification and contact details (name, email, phone number, profile picture, messaging handles); communication content (chat messages, emails, SMS, WhatsApp and Telegram messages, files, tickets, notes); audio and video recordings, voicemail, transcripts and AI summaries; call, message and meeting metadata (numbers, times, duration, participants, delivery events); calendar events, availability and bookings; consent and opt-out records; technical data (IP address, device and browser details).
Special categoriesNone intended. The Customer decides whether to put any into Syndeo.
FrequencyContinuous, for as long as the Customer uses Syndeo.
Nature and purposeProviding, securing and supporting Syndeo under the Agreement, as described in section 3.
RetentionFor the term of the Agreement, subject to the Customer's own settings and deletions: Syndeo meeting recordings are kept for the number of days the workspace sets (90 days by default); huddle audio is deleted once its summary is posted. On termination, deletion within 30 days as in section 12.
Sub-processorsAs listed on the Sub-processors page.

18.Annex II: Technical and organisational measures

  • Encryption in transit: traffic between browsers or apps and Syndeo is encrypted with TLS; our servers talk to each other over an encrypted private network.
  • Encryption at rest for credentials: OAuth tokens and connected-account credentials are encrypted with AES-256-GCM and decrypted only on our servers when needed.
  • Tenant isolation: each workspace's data is separated in the database by row-level security, so one workspace's queries cannot return another workspace's rows.
  • Access control: inside Syndeo, workspace admins control who can join and what each member can see; recordings are served through short-lived signed links, not public URLs. Access to production systems is limited to authorised VRS staff.
  • Backups and recovery: the database is backed up regularly to encrypted, off-server storage, and restores are tested.
  • Logging and monitoring: administrative changes such as API keys, webhook endpoints and channel connections are recorded in an insert-only audit log; unexpected server and browser errors are reported to an error-monitoring service without request bodies, and with email addresses, phone numbers and tokens removed.
  • Data minimisation: connected mailboxes store only what features need (for example headers and previews, with bodies fetched live), huddle audio is deleted once summarised, and recordings are deleted automatically when their retention period ends.
  • Abuse protection: public endpoints are rate limited and webhook deliveries from providers are verified by signature or secret.

Questions about this document? Email [email protected].