1.About this list
Syndeo is operated by VRS (vrsjo.com). When VRS processes personal information in a workspace on the customer's behalf, the providers below process some of it for us as sub-processors. Each receives only what it needs for the purpose shown. How we handle personal information overall is in our Privacy Policy; the contractual terms are in our Data Processing Addendum.
Sign-in (“Login” and “Partner Login”) is VRS's own account service, not a third party.
2.Core sub-processors (always)
These providers are used for every workspace.
| Provider | Purpose | Personal data | Location |
|---|---|---|---|
| GreenCloud | Server hosting: the database and the web entry point | All service data stored in the database: account details, workspace content, contacts, call and message records | EU data centres |
| Contabo | Server hosting: the Syndeo application, background jobs, AI voice agents and our self-hosted media servers (LiveKit) | All service data while it is processed, including live audio and video of huddles and Syndeo-hosted meetings | EU data centres |
| Cloudflare Cloudflare, Inc. | DNS, network edge and routing (Workers); object storage (R2) for recordings, voicemail, uploaded video, files received on messaging channels and files attached to bookings; encrypted database backups | IP addresses and request details for all traffic; stored recordings, voicemail, video and files; encrypted backups | Global network |
| Twilio Twilio Inc. | Phone numbers, calls, voicemail, SMS, WhatsApp messaging and phone number lookups | Phone numbers, call details (time, duration, direction, outcome), call audio, SMS and WhatsApp message content | United States and global |
| Resend | Sending email (invitations, booking confirmations, shared-inbox replies) and, where configured, receiving it | Names and email addresses of senders and recipients, email content and attachments, delivery events | United States |
| Groq Groq, Inc. | AI: speech-to-text, summaries, drafts, translation, answers and text-to-speech | The audio or text a feature needs, only when it is used: meeting, huddle, call and voicemail audio, and conversation text | United States |
| Sentry Functional Software, Inc. (Sentry) | Error monitoring: reports of unexpected server and browser errors | Error message, stack trace, the page path or API route and basic request details (status, server, browser). Request bodies are never attached, and email addresses, phone numbers and tokens are removed | EU region (Frankfurt, Germany) |
3.Only when you connect them
These providers receive information only when a user or the workspace chooses to connect an account with them, and only for that connection. Disconnecting stops the exchange and deletes the stored credentials. What each connection can access is described in the privacy policy's Third-party integrations section.
| Provider | Purpose | Personal data | Location |
|---|---|---|---|
| Google Google LLC | Google Meet scheduling, two-way Google Calendar sync, Gmail on contact timelines and the personal Gmail mailbox | Connected account email; calendar events and free/busy times; meeting invitations; Gmail headers, previews and labels (bodies opened live) | Global, under Google's terms |
| Microsoft Microsoft Corporation | Microsoft Teams meetings and recordings links, two-way Outlook calendar sync, Outlook on contact timelines | Connected account profile; calendar events and free/busy times; Teams meeting details; Outlook headers and previews | Global, under Microsoft's terms |
| Zoom Zoom Communications, Inc. | Scheduling Zoom meetings and linking to their cloud recordings | Connected Zoom user profile, meeting title, time and attendees, recording links | Under Zoom's terms |
| Zoho Zoho Corporation | Zoho Meeting scheduling and recordings links; Zoho Desk ticket sync | Meeting title, time and attendees; ticket subject, status, replies and notes, requester name and email | The Zoho data centre the workspace chooses (for example US, EU or India) |
| Freshdesk Freshworks Inc. (Freshdesk) | Help desk ticket sync | Ticket subject, status, priority, assignee, replies and notes, requester name and email | The region of the workspace's Freshdesk account |
| Atlassian (Jira) Atlassian (Jira Service Management) | Help desk ticket sync with Jira Service Management | Ticket subject, status, priority, assignee, public and internal comments, requester name and email | The region of the workspace's Atlassian cloud site |
| HubSpot HubSpot, Inc. | Help desk ticket sync with HubSpot Service Hub | Ticket subject, stage, priority, owner, notes and logged replies, requester contact name and email | The region of the workspace's HubSpot account |
| Telegram | The shared inbox's Telegram channel, through the workspace's own Telegram bot | Messages and files exchanged with people who write to the bot, their Telegram name and chat ID | Global, under Telegram's terms |
| Browser push services The push service of your browser (for example Google for Chrome and Edge, Mozilla for Firefox, Apple for Safari) | Delivering browser notifications to a member who turns them on in that browser | An encrypted notification the push service cannot read (sender name, a short message preview and a link), the browser's push address and the time it was sent | Under the browser maker's terms |
| Meta (WhatsApp) Meta Platforms, Inc. (WhatsApp Business Platform) | WhatsApp messaging through the workspace's own WhatsApp Business account | WhatsApp messages and media, sender phone number and profile name, message templates | United States and global |
4.Software we run ourselves
- LiveKit: the audio and video for huddles and Syndeo-hosted meetings runs on LiveKit, open-source media server software that we host on our own servers (listed above under Contabo). It is software we run, not a third party: no call audio, video or recordings are sent to LiveKit the company.
- Search embeddings: the index behind “ask anything” is computed in our own process with an open-source model; workspace content is not sent to an outside service for it.
- Database, queues and caches run on our own servers (listed above).
5.Changes to this list
We update this page, and the “Last updated” date above, before a new sub-processor starts processing personal information. As our Terms of Service set out for significant changes, we tell workspace owners in Syndeo or by email before the change takes effect; customers who have signed our Data Processing Addendum get at least 30 days' notice and can object as described there. Questions about a provider: email [email protected].
Questions about this document? Email [email protected].