Message Data Retention: What SyncRivo Stores
Message content is not stored on the normal relay path. SyncRivo keeps only message IDs so threads, edits and reactions stay in sync. Here is what is kept.
How message routing works
SyncRivo's routing architecture is designed as a transit layer, not a message store. On the normal relay path, every message follows three steps:
- 1Event received from the platformThe source platform (Slack, Teams, etc.) pushes an event to SyncRivo. The signature is verified and the message is processed in memory.
- 2Message content transformed and routed to destination APISyncRivo translates formatting, mentions and attachments and calls the destination platform's API in real time. Files pass through memory only.
- 3Message IDs recorded — content not storedSyncRivo records the source and destination message IDs so later threads, edits, deletes and reactions can be matched. Message content is not stored on this path.
What is stored vs. not stored
| Data type | Stored | Not stored |
|---|---|---|
| Message content (text) | Only in the optional retry queue, temporarily | Not stored on the normal relay path |
| File attachments | Pass through memory only | |
| Message IDs (source and destination) | Yes — to sync threads, edits and reactions | |
| Synced directory data (names, emails) | Yes — for mentions and people search | |
| Activity log and security events | Yes | |
| Provider OAuth tokens | Yes — encrypted at rest |
Compliance implications
- BAA available for Enterprise customers
- DPA and sub-processor list available
- Hosted in the US (Google Cloud us-central1)
- Activity log and security event history (JSON export)
How message data handling works in SyncRivo
Event ingestion
Every inbound event (Slack Events API, Microsoft Bot Framework, Google Chat app events, Zoom, Webex) arrives over TLS and is signature-verified before it is processed. On the normal relay path, message content is handled in memory and posted to the destination platform without being stored.
What is written
SyncRivo writes the source and destination message IDs for each relayed message so that later replies, edits, deletes and reactions reach the right message on every platform. Connection settings, synced directory data, the activity log and security events are also stored. Provider OAuth tokens are encrypted at rest.
Retries
Retries are off by default. If an admin enables the retry queue for a connection, messages that a destination could not accept are held temporarily (including text and sender email) and delivered on a later attempt. Leave retries off if you do not want message content held at all.
Platform-specific behavior
Here is how message data handling behaves across each messaging platform we support. On the normal relay path, message content from every platform is processed in transit and not stored.
| Platform | Behavior | Known limitation |
|---|---|---|
| Slack | Events API payloads relayed without storing content; message IDs kept for threads, edits and reactions. | Messages from bots and apps are not relayed. |
| Microsoft Teams | Bot Framework payloads relayed without storing content; message IDs kept. | Channel inbound requires the app installed to the team. |
| Google Chat | Chat app events relayed without storing content; message IDs kept. | Inbound edits, deletes and reactions depend on Workspace Events subscriptions. |
| Zoom Team Chat | Webhook payloads relayed without storing content; message IDs kept. | Messages are posted from the app, not as the original sender. |
| Cisco Webex | Webhook payloads relayed without storing content; message IDs kept. | Emoji reactions are not synced on Webex. |
Three-Platform Bridges
Slack + Teams + Google Chat
Bridge all three major enterprise messaging platforms.
Slack + Teams + Webex
Connect Slack and Teams users with Cisco Webex.
Slack + Teams + Zoom
Unify Slack, Teams, and Zoom Team Chat.
Slack + Google Chat + Zoom
Three-way bridge for Slack, Google Chat, and Zoom.
Slack + Google Chat + Webex
Unify Slack, Google Chat, and Cisco Webex.
Slack + Zoom + Webex
Bridge Slack with both Zoom and Webex.
Teams + Google Chat + Zoom
Connect Teams, Google Chat, and Zoom Team Chat.
Teams + Google Chat + Webex
Bridge Teams, Google Chat, and Cisco Webex.
Teams + Zoom + Webex
Unify Teams, Zoom, and Webex in one bridge.
Google Chat + Zoom + Webex
Connect Google Chat with Zoom and Webex.
Ready to connect? Slack ↔ Teams connection setup →
Frequently asked questions
- Does SyncRivo store my messages?
- Message content is not stored on the normal relay path. Messages pass through SyncRivo and are posted to the destination platform; SyncRivo keeps message IDs so threads, edits and reactions stay in sync, and files pass through memory only. If an admin enables the optional retry queue, undelivered messages (text and sender email) are held temporarily until they can be delivered.
- How does SyncRivo's data handling affect HIPAA?
- Not storing message content on the normal relay path reduces how much data SyncRivo holds, but SyncRivo still processes message content in transit, so it acts as a business associate when messages contain PHI. A BAA is available for Enterprise customers.
- Is there an audit log if SyncRivo doesn't store messages?
- SyncRivo keeps an activity log and security event history (JSON export). These record sync activity and security events such as sign-ins and role changes, without message content.
- Can I verify SyncRivo's data handling independently?
- SyncRivo does not currently hold a SOC 2 report; we provide a security questionnaire and architecture review on request. A DPA and sub-processor list are also available.
Related integration guides
Three-Platform Bridges
Connect three enterprise messaging platforms simultaneously with SyncRivo's cross-platform bridges.