The third parties that process customer data for Synapse AI, what they do, where they operate, and how to get notice of changes.
Effective date: [EFFECTIVE_DATE] · Last updated: [EFFECTIVE_DATE] [LEGAL_ENTITY_NAME] (“Synapse”, “we” or “us”) uses a limited number of third-party service providers to operate Synapse AI. This page lists the subprocessors that may process Customer Personal Data on our behalf, explains how we choose and oversee them, and describes how we notify customers before we add or replace one.
A subprocessor is a third party that Synapse engages to process personal data contained in Customer Data while we provide the Service. Our use of subprocessors is governed by the Data Processing Addendum (“DPA”). Capitalized terms used on this page have the meanings given in the DPA and the Terms of Service.
This list does not include:
Before we engage a subprocessor, and periodically afterward, we:
Synapse remains responsible for the performance of each subprocessor’s obligations under the DPA.
| Subprocessor | Purpose | Location | Data categories |
|---|---|---|---|
| [CLOUD_HOSTING_PROVIDER] | Cloud infrastructure for the Synapse platform: application hosting, compute, databases, file storage, search and vector indexes, and encrypted backups. | [DATA_REGIONS] (the hosting region of each workspace) | All categories of Customer Personal Data, including user profile and account data, work content such as tasks, docs and attachments, meeting recordings and transcripts, and service logs. |
| [LLM_PROVIDERS] | AI model inference for AI Features, including triage classification, speech-to-text transcription, meeting summaries, AI automation steps, embeddings and Synapse Copilot answers. Requests are routed according to each workspace’s data policy. | [LLM_PROVIDER_LOCATIONS] | Content retrieved for a request from sources the requesting user is permitted to access, meeting audio and transcripts, user questions and prompts, and generated outputs. |
| [EMAIL_DELIVERY_PROVIDER] | Delivery of transactional email, including workspace invitations, notifications, meeting summaries, weekly digests and account messages. | [EMAIL_DELIVERY_LOCATION] | Recipient names and email addresses, and message content such as task titles, summary excerpts and digest contents. |
| [PAYMENT_PROCESSOR] | Payment processing and fraud screening for plan purchases. | [PAYMENT_PROCESSOR_LOCATION] | Billing contact name, email address and billing address; payment card details submitted at checkout; order and transaction records. |
| [SUPPORT_TOOL_PROVIDER] | Customer support ticketing, chat and help-desk communications. | [SUPPORT_TOOL_LOCATION] | Requester name, email address and workspace details, and the messages, attachments and screenshots customers share with our support team. |
For billing and account contact data, Synapse acts as a controller, as described in the Privacy Policy. We list the payment and support providers here as well so that security and procurement reviewers see every provider that may receive customer information.
Customer Data is stored in the hosting region of each workspace. Customers on every plan can choose the hosting region for their workspaces from the available regions: [DATA_REGIONS].
AI Features send a model provider only the content needed to complete a specific request, after filtering that content by the requesting user’s permissions. Workspace admins configure which model providers are permitted for their workspaces, and the Synapse model router sends requests only to permitted providers. Our model training commitment and the retention terms that apply to model providers are set out in Section 5 of our AI & Responsible Use Policy.
At least [SUBPROCESSOR_NOTICE_DAYS] days before a new subprocessor begins processing Customer Personal Data, we will:
Customers that have accepted the DPA may object to a new subprocessor on reasonable data protection grounds during the notice period, as set out in Section 6.4 of the DPA. If we must replace a subprocessor urgently to protect the security or continuity of the Service, we will give notice as soon as reasonably practicable, and the objection period runs from that notice.
To receive advance notice of subprocessor changes, email [PRIVACY_EMAIL] from your work email address with the subject line “Subscribe to subprocessor updates” and include your organization name and workspace name. We will confirm your subscription by email.
You can add several contacts, such as your security, privacy and procurement leads. Enterprise customers can also ask their named escalation contact to add contacts. To unsubscribe, reply to any update or write to [PRIVACY_EMAIL].
| Date | Change |
|---|---|
| [EFFECTIVE_DATE] | Initial publication of the subprocessor list. |
Questions about our subprocessors or this page can be sent to [PRIVACY_EMAIL] or by mail to [LEGAL_ENTITY_NAME], Attn: Privacy, [MAILING_ADDRESS].
Release notes, engineering deep dives and delivery playbooks from the Synapse team.
© 2026 Synapse AI Systems LLC. All rights reserved.
Third-party product names and logos are the property of their respective owners; their use does not imply endorsement.