1.Who we are
Syndeo is operated by VRS (vrsjo.com). In this policy, “VRS”, “we”, “us” and “our” mean the team that runs Syndeo at app.syndeo.cloud.
For any privacy question or request, email [email protected]. We acknowledge requests within 5 working days and complete them within 30 days. If a request is complex we will tell you, within those 30 days, why we need longer and by when we will finish.
2.What Syndeo is
Syndeo is a communication workspace for teams. Depending on what a workspace turns on, it includes:
- Team chat: channels, direct messages, files and reactions.
- Huddles: quick audio and video calls inside chat.
- Meetings: video meetings hosted by Syndeo, or scheduled through Google Meet, Microsoft Teams, Zoom or Zoho Meeting, with a recording library.
- Phone: business phone numbers, calls, voicemail and SMS.
- Booking and calendar: public booking pages, and a calendar of your events, meetings and bookings that can sync both ways with your Google or Microsoft calendar.
- Shared inbox: one place for a team to answer customer email, SMS, WhatsApp, Telegram and website chat.
- Help desk: tickets, optionally synced with Zoho Desk, Freshdesk, Jira Service Management, HubSpot or another help desk you connect.
- AI features: summaries of huddles, meetings, calls and voicemail, reply drafts, translation, search that answers questions about your workspace, daily digests and an AI phone receptionist.
3.Our role: controller and processor
For your account (who you are, how you sign in, how you use the service), VRS decides how that information is used, so we are the controller.
For workspace content (messages, files, recordings, transcripts, customer conversations, contacts and so on), the organisation that owns the workspace decides what goes in and who can see it. For that content we act on the organisation's instructions as its processor. If you are a customer of a Syndeo workspace (for example, you emailed a company that uses our shared inbox, or booked a meeting on its booking page), that company is responsible for your information. We will pass any request we receive about it to them and help them answer it.
4.Information we process
Account information
You sign in to Syndeo with an account provided by VRS's account service (“Login”, or “Partner Login” through the VRS Recruit sign-in page). We receive your name, email address and profile picture if you have one, and we keep a session so you stay signed in. Meeting guests who join without an account give a display name for that meeting.
Workspace content
Everything you and your colleagues put into Syndeo: chat messages, files, statuses, custom emoji, tickets, notes, contacts and companies, and the settings your workspace chooses.
Meetings, huddles, recordings and transcripts
- Audio and video for huddles and Syndeo-hosted meetings is carried by media servers we run ourselves (LiveKit, self-hosted on our own servers). We do not send live media to a third-party video provider for these calls.
- When a Syndeo meeting is recorded, we store the full recording, one audio track per speaker, a speaker-labelled transcript and an AI summary. Recorded video messages you upload are stored the same way.
- When a huddle is summarised, we record each speaker's audio, transcribe it, post a summary to the channel, and then delete the audio. The transcript and summary are kept.
- For meetings held on Google Meet, Microsoft Teams, Zoom or Zoho Meeting, recordings stay with that provider. Syndeo shows a link to them and does not copy them.
Phone calls, voicemail, SMS and WhatsApp
Syndeo's phone service runs on Twilio. For each call we process call details (numbers, direction, time, duration, who answered, outcome). Calls on a number whose recording setting is “always” are recorded after a spoken notice that the call may be recorded; recorded calls and voicemail are transcribed and summarised. SMS and WhatsApp messages you send and receive through Syndeo pass through Twilio or, if your workspace connects its own WhatsApp Business account, through Meta's WhatsApp Business Platform.
Customer contacts and the shared inbox
The shared inbox holds the conversations your team has with its customers: their names, email addresses, phone numbers, message content and attachments, plus anything your team records about them (notes, tags, timeline entries, consent records).
Email for connected shared addresses
When a workspace connects a shared address (for example [email protected]), we process the email sent to and from that address: headers, body, attachments and delivery events such as bounces and complaints.
Calendars and bookings
Syndeo keeps a calendar for each user: the events they create (title, time, place, description, repeat rule, reminders), the people they invite with each person's answer, meetings and bookings, and the working hours they set for booking pages. People invited by email receive an invitation with a private link to answer it; we store their email address and answer.
If you connect your own Google or Microsoft calendar, Syndeo reads your free/busy times so booking pages only offer times you are free and, with the calendar access you grant, syncs events both ways: the events of the calendars you choose to show (title, time, place, description, attendees and whether you are busy) appear in your Syndeo calendar, and Syndeo events, meetings and bookings are added to the one calendar you pick, and kept up to date there. You choose which calendars are shown and which one receives Syndeo events, and you can turn either off at any time. Events imported from your calendars are visible only to you: teammates see those times as busy, without titles or details, unless you choose to share a particular calendar's details with your workspace. Events marked private in your calendar always stay busy-only. When a meeting is scheduled on Google Meet, Microsoft Teams, Zoom or Zoho Meeting, we create (and, if it is cancelled, delete) that meeting in the connected account. People who book through a booking page give their name and email, and may add a phone number and a note.
A booking page can also ask its own questions, including for files such as a CV (PDF, Word DOCX, PNG or JPG, up to 25 MB each; the type is checked from the file itself). Answers and files are visible only to the booking's hosts, the link's owner and workspace administrators; files are stored privately and opened only through links that work for 5 minutes. A file uploaded without completing a booking is deleted after 24 hours (an upload that fails part-way, within an hour). Files attached to a booking are deleted 180 days after the meeting unless the link's owner sets a different period (1 to 3,650 days). A booking's answers, note and files are also deleted when a host deletes that booking's data, when the workspace erases you as a contact, or when the booking is deleted, except while they are under a legal hold placed on the booking by a workspace administrator (or on the meeting's recordings), which keeps them until it is released. When a company sends you a personal booking link, it may already carry details you gave it (for example the CV you applied with, which Syndeo may fetch from the company's own system; only the address it came from is kept, without any query string), so you are not asked again. Those details are kept with that link, shown only to whoever opens it, never put in its address, and deleted when the link expires or is withdrawn if no booking uses them, or when the workspace erases you as a contact.
Your mailbox on contact timelines (optional)
A user can connect their own Gmail or Outlook mailbox with read-only access. Syndeo then reads the sender, recipients, subject, date and a short preview of recent messages, and adds an entry to a contact's timeline only when the message is with an email address that is already a contact in the workspace. Mail with anyone else is not stored. Syndeo never sends, changes or deletes mail in that mailbox.
Your personal mailbox in Syndeo (optional)
A user can also connect their own Gmail as My mailbox to read and answer it inside Syndeo. Syndeo stores the headers (sender, recipients, subject, date), Gmail's short preview and the labels of messages from the recent import window (30 days by default) so it can list them, and keeps them up to date. Full message bodies and attachments are fetched from Gmail when the user opens them and are not stored. Syndeo changes that mailbox only when the user asks it to (mark read or unread, star, archive, move to a label, move to Trash, or send a message the user wrote). This mailbox is visible only to the user who connected it, not to workspace administrators or other members. Disconnecting deletes Syndeo's copy and its access.
Usage and diagnostic information
Our servers and our network provider (Cloudflare) process technical information needed to run the service and keep it secure: IP addresses, browser and device details, the pages and API endpoints requested, timestamps and error details. When the AI assistant takes part in a call or meeting, we also record each participant's connection quality and talk time. When our servers hit an unexpected error, or a page hits one in your browser, an error report (the error message, where in our code it happened, the page path or API route, and basic request details) is sent to our error-monitoring provider, Sentry, in its EU region. Browser errors are passed through our own servers first. In every report, request bodies are never attached, and email addresses, phone numbers and tokens are removed before it leaves our servers. We do not use third-party analytics or advertising trackers in Syndeo.
5.How we use information
- To provide the service your organisation signed up for: delivering messages, calls, meetings, email and bookings, and showing the right content to the right people. (Legal basis: performing our contract with your organisation, and our legitimate interest in providing a working product to its users.)
- To run the features you turn on, such as recordings, transcripts and AI summaries.
- To keep Syndeo secure and reliable: preventing abuse, investigating problems and fixing bugs. (Legitimate interest.)
- To communicate with you about your account, invitations, bookings and important changes to the service.
- To meet legal obligations, such as responding to lawful requests from authorities.
We do not sell personal information, we do not use workspace content for advertising, and we do not use it to build profiles of you for any purpose other than running Syndeo.
6.AI features
Syndeo's AI features use Groq to turn speech into text, write summaries and drafts, translate, answer questions and speak for the AI receptionist. When you use one of these features, the text or audio it needs (for example a meeting's audio, or the conversation you want a reply drafted for) is sent to Groq to produce the result, and the result is stored in your workspace.
The search index behind “ask anything” is built on our own servers: the embeddings are computed in our own process, not by an outside service. Search results only include content from channels the person asking can already see.
We do not train AI models on your workspace content. AI output can be wrong; AI scorecards for calls are saved as drafts that a person must approve.
7.Third-party integrations
Some features work by connecting an account you hold with another provider. You choose whether to connect them. For every connection below:
- We only request the permissions listed, and only use them for the purpose described.
- The access and refresh tokens the provider gives us are encrypted at rest with AES-256-GCM before they are stored, and are only decrypted on our servers when Syndeo needs to call the provider for you.
- Disconnecting in Syndeo deletes the stored tokens straight away. You can also revoke Syndeo's access at any time in your account settings with the provider; after that, Syndeo can no longer reach that account.
What we access and why:
- Google Meet scheduling (workspace connection) — scopes
openid,emailandhttps://www.googleapis.com/auth/calendar.events. Used to create a calendar event with a Google Meet link on the connected account's primary calendar when you schedule a meeting (Google emails the invitation to the attendees), and to delete that event if the meeting is cancelled. Your email address identifies which Google account is connected. - Your calendar in Syndeo (your personal calendar) — scopes
openid,email,https://www.googleapis.com/auth/calendar.freebusy,https://www.googleapis.com/auth/calendar.eventsandhttps://www.googleapis.com/auth/calendar.calendarlist.readonly. The calendar list is read only to show you which of your calendars you can choose from (without it, only your primary calendar is used). Used to read when you are busy so booking pages only offer free times; to show the events of the calendars you choose in your Syndeo calendar (to you; teammates see them as busy unless you share that calendar's details); and to add, update and remove the Syndeo events, meetings and bookings you asked to be put on the calendar you picked. Syndeo only changes events it created, or events you edit in Syndeo yourself. - Gmail on contact timelines (optional, your personal mailbox) — scopes
openid,emailandhttps://www.googleapis.com/auth/gmail.modify. Although this permission would allow changes, this feature only reads: it reads the headers (from, to, cc, subject, date) and the short preview of recent messages, and adds an entry to a contact's timeline only when the other party is already a contact in your workspace. Nothing is sent, changed or deleted by this feature. Connections made before 27 September 2026 were granted the read-onlyhttps://www.googleapis.com/auth/gmail.readonlyscope instead; they keep working with that scope until you reconnect. - My mailbox (optional, your personal Gmail inside Syndeo) — scopes
openid,email,https://www.googleapis.com/auth/gmail.modifyandhttps://www.googleapis.com/auth/gmail.send. Used to list your recent mail (headers, preview and labels are stored; bodies and attachments are opened live from Gmail), to apply the changes you make in Syndeo (read or unread, star, archive, labels, Trash — never a permanent delete) and to send the messages you write, from your own address. Visible only to you.
Syndeo'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.
In particular, information we receive from Google APIs:
- is used only to provide and improve the user-facing features described above;
- is not used for advertising, including retargeting or personalised ads;
- is not sold, and is not transferred to anyone except as needed to provide those features, to comply with law, or as part of a merger or acquisition with notice to you;
- is not used to develop, improve or train generalised AI or machine-learning models;
- is not read by people, except with your explicit consent for specific messages, when needed for security (such as investigating abuse), to comply with applicable law, or when the data has been aggregated and anonymised for internal operations.
Disconnect: Google Meet — Meetings → Providers & settings → Disconnect. Google Calendar — Calendar → Connected calendars → Disconnect. Gmail on timelines — Contacts → Your mailbox on the timeline → Disconnect. My mailbox — Inbox → My mailbox → Mailbox options → Disconnect Gmail. Revoke at Google: myaccount.google.com/connections.
Microsoft
- Microsoft Teams meetings (workspace connection) — permissions
openid,email,offline_access,User.Read,OnlineMeetings.ReadWriteandOnlineMeetingRecording.Read.All. Used to create Teams online meetings when you schedule one, and to list a meeting's recordings so the recording library can link to them. Recordings stay in Microsoft 365.offline_accesslets Syndeo keep the connection working without asking you to sign in again;User.Readidentifies the connected account. - Your calendar in Syndeo (your personal calendar) — permissions
openid,email,offline_access,User.ReadandCalendars.ReadWrite(accounts connected before two-way sync keepCalendars.Read, which only reads busy times, until you allow calendar access). Used in the same way as Google Calendar above: busy times for booking pages, events of the calendars you choose, and the Syndeo events you asked to be put on the calendar you picked. - Outlook on contact timelines (optional, your personal mailbox) — permissions
offline_access,Mail.ReadandUser.Read. Used in the same read-only way as Gmail above.
Disconnect: Teams — Meetings → Providers & settings → Disconnect. Outlook calendar — Calendar → Connected calendars → Disconnect. Outlook mailbox — Contacts → Your mailbox on the timeline → Disconnect. Revoke at Microsoft: myapps.microsoft.com (work or school accounts) or account.live.com/consent/Manage (personal accounts).
Zoom
Used to read the connected Zoom user's profile (to show which account is connected), to create Zoom meetings when you schedule one and delete them if cancelled, and to list a meeting's cloud recording files so the recording library can link to them. Recordings stay in Zoom.
Disconnect: Meetings → Providers & settings → Disconnect. Revoke at Zoom: remove Syndeo from marketplace.zoom.us → Manage → Added Apps.
Zoho Meeting
Scopes ZohoMeeting.meeting.CREATE, ZohoMeeting.meeting.READ, ZohoMeeting.meeting.DELETE, ZohoMeeting.manageOrg.READ and ZohoMeeting.recording.READ. Used to schedule and cancel Zoho meetings, read your Zoho organisation ID (needed by Zoho's API) and link to recordings, which stay in Zoho. Disconnect: Meetings → Providers & settings → Disconnect; revoke in your Zoho account's connected apps settings.
WhatsApp Business, Telegram and help desks
A workspace can connect its own WhatsApp Business account (through Meta), its own Telegram bot, and help desks: Zoho Desk, Freshdesk, Jira Service Management (Atlassian) or HubSpot. Messages and tickets are exchanged with those services as the workspace directs. Their credentials are encrypted at rest in the same way. Workspace admins can disconnect them in Syndeo (for help desks, Help desk → Connected desks → Disconnect).
- Meta (WhatsApp Business Platform): WhatsApp messages to and from the workspace's own WhatsApp Business number, with the sender's phone number and profile name, and any media.
- Telegram: messages and files exchanged with people who write to the workspace's Telegram bot, with their Telegram name and chat ID. Files people send are copied into Syndeo's storage.
- Zoho Desk, Freshdesk, Jira Service Management (Atlassian) and HubSpot: ticket subject, status, priority, assignee, replies and notes, and the requester's name and email address, kept in sync in both directions.
8.Service providers (sub-processors)
We use these providers to run Syndeo. Each receives only what it needs for the purpose shown.
| Provider | Purpose | Location |
|---|---|---|
| GreenCloud | Server hosting: database and the web entry point | EU data centres |
| Contabo | Server hosting: the Syndeo application, background jobs, AI voice agents and our self-hosted media servers | EU data centres |
| Cloudflare | DNS, network edge and routing; storage of recordings, voicemail and uploaded video (R2) | Global network |
| Twilio | Phone numbers, calls, voicemail, SMS, WhatsApp messaging and phone number lookups | United States and global |
| Resend | Sending email (invitations, booking confirmations, shared-inbox replies) and, where configured, receiving it | United States |
| Groq | AI: speech-to-text, summaries, drafts, translation, answers and text-to-speech | United States |
| Sentry (Functional Software, Inc.) | Error monitoring: reports of unexpected server and browser errors (message, stack trace, page path or route); request bodies are never attached, and email addresses, phone numbers and tokens are removed | EU region (Frankfurt, Germany) |
Sign-in is provided by VRS's own account service. Google, Microsoft, Zoom, Zoho, Freshdesk, Atlassian (Jira), HubSpot, Telegram and Meta only receive information when you or your workspace choose to connect them (see Third-party integrations). If you turn on browser notifications, your browser's push service (for example Google, Mozilla or Apple) delivers each notification to you encrypted, so it cannot read it. The full list, with what each provider receives and where, is on our Sub-processors page. We will update this list before adding a new provider that processes personal information. Workspace owners who need a data processing agreement can use our Data Processing Addendum.
9.International transfers
Our servers are in EU data centres. Some providers above process information in the United States or on a global network. Where information leaves the country it was collected in, we rely on the safeguards those providers offer in their data processing terms, such as the European Commission's Standard Contractual Clauses where they apply.
10.Security
- Traffic between your browser and Syndeo is encrypted with TLS, and our servers talk to each other over an encrypted private network.
- OAuth tokens and connected-account credentials are encrypted at rest with AES-256-GCM.
- Each workspace's data is separated in the database by row-level security, so one workspace's queries cannot return another's rows.
- Recordings are served through short-lived signed links rather than public URLs.
- Access to production systems is limited to authorised VRS staff.
No system is perfectly secure. If we become aware of a breach affecting your information, we will notify the affected workspaces and, where the law requires, the relevant authorities and individuals.
11.How long we keep information
- Meeting recordings (Syndeo-hosted): kept for the number of days set by your workspace under Meetings → Providers & settings → “Keep Syndeo recordings for (days)”, which is 90 days unless your workspace changes it (1 to 3,650 days). When that time is up the recording file is deleted automatically, unless the meeting is under a legal hold set by the workspace. Transcripts and summaries stay with the meeting.
- Huddle audio: deleted as soon as the summary has been posted.
- Files attached to bookings: deleted 180 days after the meeting unless the booking link sets another period (1 to 3,650 days), and with the booking's answers when a host deletes that booking's data, when the person is erased as a contact, or when the booking is deleted. Files uploaded without completing a booking are deleted after 24 hours (failed uploads within an hour); files carried by a personal booking link are deleted when the link expires or is withdrawn, unless a booking uses them. A booking under legal hold keeps its answers and files (including one shared with other bookings) until the hold is released.
- Recordings held by Google, Microsoft, Zoom or Zoho: governed by your settings with that provider.
- Workspace content, call recordings and voicemail: kept while the workspace uses Syndeo, unless the workspace deletes it sooner. When a workspace leaves Syndeo, its owner can ask us to delete its data, and we complete that within 30 days.
- Connected-account tokens: deleted when you disconnect.
- Diagnostic logs: kept only as long as needed for security and troubleshooting.
Deleted data can remain in encrypted backups for a short period until those backups are overwritten.
12.Your rights
Depending on where you live, you may have the right to:
- access the personal information we hold about you and get a copy;
- correct information that is wrong or incomplete;
- delete your information;
- portability: receive your information in a structured, machine-readable format;
- object to, or ask us to restrict, how we use your information;
- withdraw consent where we rely on it, for example by disconnecting an integration;
- complain to your local data protection authority.
Email [email protected] to use any of these rights. We acknowledge within 5 working days and complete requests within 30 days. We may need to confirm your identity first. If your request is about content in a workspace, we will involve that workspace's organisation, which controls that content; workspace admins can also export or erase a contact's information directly in Syndeo.
14.Children
Syndeo is a tool for businesses and is not intended for anyone under 16. We do not knowingly collect information from children under 16. If you believe a child has given us personal information, email [email protected] and we will delete it.
15.Changes to this policy
We will update this page when our practices change and change the “Last updated” date at the top. If a change is significant, we will tell workspace owners in Syndeo or by email before it takes effect.
16.Contact
VRS · vrsjo.com · [email protected]. See also our Terms of Service, Sub-processors and Data Processing Addendum.
Questions about this document? Email [email protected].