Privacy Policy
Last updated: November 12, 2026
The current Android app stores the accepted terms version, confirmation of age 18+ and acceptance time, not a date of birth. Reports contain a target identifier, reason, status and time; private communication is not attached. Synapse account deletion is separate from your Tessera identity. Account deletion
AI agent conversations
If your account has an enabled connected AI agent and you send it a message, the Synapse backend processes its content and forwards it to that agent. The content is available to Synapse and the operator of the agent. This flow does not use the Signal end-to-end encryption of private conversations; HTTPS protects network transport. Processing and retention by the connected agent also depend on the policies of its operator. AI availability follows your account settings.
1. Introduction
Synapse ("we", "us", or "our"), operated by Cabakorp, is committed to protecting your privacy. This Privacy Policy explains how we collect, use, and safeguard information when you use our end-to-end encrypted messaging platform.
Synapse is a private communication platform for personal and team conversations. Message content is end-to-end encrypted; the service stores the account, device and delivery information described below.
2. Information We Collect
To operate the service, we collect the following information:
Account Information
- Email address (required for account identification)
- Display name (optional, set by you or your administrator)
- Phone number (optional)
- Organization membership and role
Device Information
- Device name (user-provided identifier)
- Device type and platform (for example Android or a web browser)
- Device identifiers and public authentication information
- Last connection timestamp
- IP address of the last connection
Push Notification Tokens
- Apple Push Notification service (APNs) tokens for message delivery notifications
- VoIP push tokens for incoming call notifications
- Firebase Cloud Messaging (FCM) tokens for Android and Web Push subscription details for browsers
3. What We Cannot Access
By design, the following data is inaccessible to us and our servers:
- Message content — All messages are encrypted end-to-end using the Signal Protocol. Only you and your intended recipients can read your messages.
- Voice and video call audio/video — Calls use DTLS-SRTP encryption between the devices. Encrypted media may pass through a TURN relay when a direct connection is unavailable; the relay cannot decrypt it. Because call setup passes through our servers, your devices compare each other’s DTLS fingerprints over the end-to-end encrypted Signal session: a mismatch ends the connection, and a connection that cannot be confirmed within 10 seconds is shown as unverified.
- Your private encryption keys — Private encryption keys are generated on your devices and protected in local secure storage. Device linking and history transfer use encrypted exchanges between authorized devices; the server does not receive plaintext private keys.
4. Voice and Video Calling
Synapse supports encrypted voice and video calls with the following privacy characteristics:
- Calls are established peer-to-peer using WebRTC technology
- All call media is encrypted with DTLS-SRTP. After each call setup exchange, your devices compare the DTLS fingerprints over the end-to-end encrypted Signal session. A mismatch ends the connection; a connection not confirmed within 10 seconds is shown as unverified and continues, unless the service is set to end such calls
- Call signaling (connection setup) passes through our servers. It contains the devices’ DTLS fingerprints and network addresses, but no call content
- Call metadata is stored by the service and synchronized to your devices. This includes participants, timestamps, duration and call status. Call records include IP addresses, which are removed after 30 days; call audio and video are not recorded
- We use TURN/STUN servers to help establish connections when direct peer-to-peer is not possible due to network restrictions
5. Message Handling and Retention
Messages in Synapse are handled with privacy as the primary concern:
- Encrypted storage — Messages are stored as encrypted ciphertext. Without the decryption keys (which exist only on recipient devices), the content is unreadable.
- Disappearing messages — A conversation can have a disappearing-messages timer; in a group, only its owner and admins can change it. A message expires when the set time has passed after it was read. Expired messages are hidden by the apps and removed from the server by periodic cleanup. For an image, this removes the message that carries the image key; the encrypted image file itself stays in storage.
- Metadata — We store the metadata needed for message delivery: timestamps, delivery status, and sender/recipient device identifiers.
- Message reactions — Reaction emoji, the reacting user and the associated message identifier are stored by the service. Reactions are not end-to-end encrypted.
6. Third-Party Services
We use a limited number of third-party services to operate Synapse:
- Apple Push Notification service (APNs) — To deliver message and call notifications to iOS devices. Notifications carry a generic text and identifiers only — no names, e-mail addresses, group names or message text.
- Firebase Cloud Messaging and browser push services — To deliver notifications on Android and in browsers, with the same content limits.
- Tessera — Cabakorp’s identity service for account registration and sign-in.
- Formspree — Processes details you submit through this website’s contact form.
- Resend — For sending invitation and account-related emails only.
- TURN/STUN servers — To facilitate WebRTC call connections. These servers relay encrypted call data when direct peer-to-peer connections cannot be established.
- Microsoft Azure — Hosts the Synapse backend service.
- Supabase — Hosts the PostgreSQL database (EU, Ireland), which holds the encrypted messages and the account, device and call data described in this policy.
7. Data Security
We implement multiple layers of security to protect your data:
- Signal Protocol — End-to-end encryption through libsignal with the Double Ratchet algorithm, which provides forward secrecy and post-compromise security
- Post-quantum cryptography — Key agreement uses libsignal’s PQXDH with Kyber1024
- Device authentication — Account authentication and device authorization control access to the service
- Access controls — Organizations share one service and database. The service separates them by checking user authorization, conversation participation and organization permissions in the application on every request
- Local storage — Android and iOS keep messages in a SQLCipher-encrypted local database. Android keeps its encryption keys in that database and protects the database key with Android Keystore; iOS keeps its encryption keys and the database key in the Keychain. The browser stores keys and history in IndexedDB, encrypted with a non-extractable key that the browser keeps
8. Data Retention and Deletion
We retain data only as long as necessary:
- Account data is retained while your account is active
- Expired messages are removed by periodic server cleanup, as are message copies not read within 30 days and deleted messages after 7 days
- Temporary call signaling state and persistent call history are separate. Call history metadata is retained to provide history across devices; IP addresses in call records are removed after 30 days
- Device records can include revoked devices; revocation prevents further authorized access and does not itself erase every stored record. A device’s last IP address is removed after 90 days without activity
- To request deletion of account data, contact us below. Account deactivation is separate from physical deletion of stored records
9. Emergency Data Deletion
Synapse includes a company emergency "panic button". Administrators configure its password; a company member who knows that password can activate it. When accepted by the service:
- The service deletes the company’s conversations and messages, the message copies its users sent or received in other conversations, and their media, backups, call records and avatars
- All user accounts in the organization are deactivated
- All registered devices are revoked
- Connected apps are notified and erase their local data
- The action cannot be undone in the app. It does not guarantee immediate erasure of copies on offline devices or deletion of every retained record, such as the audit log
10. Your Rights
Under applicable data protection laws (including GDPR), you have the right to:
- Access the personal data we hold about you
- Correct inaccurate personal data
- Request deletion of your personal data
- Object to or restrict processing of your data
- Data portability (receive your data in a structured format)
Note: Due to end-to-end encryption, we cannot provide access to message content as we do not have the ability to decrypt it. Message content can only be accessed on an authorized device.
11. Device Permissions
The Synapse app may request the following device permissions:
- Microphone — Required for voice calls
- Camera — Used for video calls and scanning device-linking QR codes
- Push notifications — To receive message and call notifications
You can manage these permissions in your device settings at any time.
12. Changes to This Policy
We may update this Privacy Policy from time to time. We will notify you of any material changes through the app or by email. Your continued use of Synapse after changes become effective constitutes acceptance of the updated policy.
13. Contact Us
If you have questions about this Privacy Policy or wish to exercise your data rights, please contact us at [email protected].
Data Controller: Cabakorp
Website: https://cabakorp.com