How Synapse AI processes customer personal data as your processor and service provider, with security, transfer and deletion terms.
Effective date: [EFFECTIVE_DATE] · Last updated: [EFFECTIVE_DATE]
This Data Processing Addendum (the “DPA”) forms part of the Terms of Service or other written agreement for Synapse AI (the “Agreement”) between [LEGAL_ENTITY_NAME] (“Synapse”) and the customer that entered into the Agreement (“Customer”). It sets out the terms that apply when Synapse processes Customer Personal Data on Customer’s behalf to provide the Service.
This DPA takes effect automatically when Customer accepts the Agreement. No separate signature is required. Customers that need a countersigned copy for their records can request one at [PRIVACY_EMAIL].
1.1 Scope. This DPA applies where, and to the extent that, Synapse processes Customer Personal Data on behalf of Customer while providing the Service, and that processing is subject to Data Protection Laws.
1.2 Data outside this DPA. This DPA does not cover personal data that Synapse processes as an independent controller or business. That includes account and billing contact details, website visitor data, sales and marketing communications, and information Synapse uses to secure the Service, prevent fraud and meet its own legal obligations, to the extent Data Protection Laws allow Synapse to decide the purposes of that processing. Synapse handles that data as described in its Privacy Policy.
1.3 Order of precedence. If there is a conflict, the following order applies: (a) the Standard Contractual Clauses and the UK Addendum, where they apply; (b) this DPA; and (c) the rest of the Agreement. Nothing in this DPA reduces either party’s obligations under Data Protection Laws.
1.4 Affiliates. Where Customer’s affiliates use the Service under Customer’s account, Customer enters into this DPA on their behalf and remains the single point of contact for Synapse.
Capitalized terms not defined in this DPA, including “Customer Data”, “Authorized User”, “Guest”, “Workspace”, “AI Features”, “Order Form” and “Term”, have the meanings given in the Agreement.
3.1 GDPR and similar laws. As between the parties, Customer is the controller of Customer Personal Data and Synapse is its processor. Where Customer acts as a processor on behalf of a third-party controller, Synapse acts as Customer’s subprocessor, and Customer is responsible for obtaining any authorizations its controller requires.
3.2 CCPA and US state laws. Customer is the business or controller, and Synapse is the service provider or processor, for Customer Personal Data. The service provider terms in Section 13 apply.
3.3 Independent controller data. Synapse is an independent controller for the data described in Section 1.2 and is not a processor for that data under this DPA.
3.4 Details of processing. The subject matter, nature, purpose and duration of the processing, and the categories of data subjects and personal data, are described in Annex 1.
4.1 Documented instructions. Customer instructs Synapse to process Customer Personal Data to provide, secure and support the Service in accordance with: (a) the Agreement and this DPA; (b) Customer’s configuration and use of the Service, including Workspace settings, AI Feature settings, approval policies, integration connections, automation definitions and retention settings; and (c) other reasonable written instructions from Customer that are consistent with the Agreement. Instructions outside that scope require prior written agreement, including any applicable fees.
4.2 Unlawful instructions. Synapse will inform Customer without undue delay if, in its opinion, an instruction infringes Data Protection Laws, and may suspend the affected processing until Customer confirms or modifies the instruction.
4.3 Customer responsibilities. Customer is responsible for:
4.4 Restricted data. Unless expressly agreed in writing, Customer will not submit to the Service special categories of personal data, government identification numbers, financial account or payment card numbers, protected health information, or personal data of children under 16, other than incidental content in ordinary business communications and documents. The Acceptable Use Policy also applies.
5.1 Processing on instructions. Synapse processes Customer Personal Data only on Customer’s documented instructions, unless applicable law requires otherwise. In that case, Synapse will inform Customer of the legal requirement before processing, unless the law prohibits this on important grounds of public interest.
5.2 Personnel. Synapse ensures that personnel authorized to process Customer Personal Data are bound by confidentiality obligations, receive appropriate security and data protection training, and have access only where needed to provide, secure and support the Service.
5.3 AI processing. When Customer uses AI Features, as further described in the AI & Responsible Use Policy, Synapse:
5.4 Model training. Synapse’s commitment regarding the use of Customer Personal Data to train machine learning models is as follows: [AI_TRAINING_POLICY]
5.5 Model provider retention. Retention of Inputs and Outputs by model providers is governed by the following terms: [ZDR_STATUS]
5.6 Aggregated service data. Synapse may generate aggregated operational metrics, such as service performance, reliability and feature usage statistics, that do not identify Customer, any Authorized User or Guest, or any other individual. Synapse uses these metrics only to operate, secure and improve the Service and will not attempt to re-identify them.
5.7 Assistance. Taking into account the nature of the processing and the information available to it, Synapse will provide reasonable assistance with Customer’s data protection impact assessments and prior consultations with supervisory authorities, including by making available the information described in Section 10.
6.1 General authorization. Customer grants Synapse general written authorization to engage Subprocessors. The current list, including each Subprocessor’s purpose, location and data categories, is published on the Subprocessors page.
6.2 Subprocessor obligations. Synapse will: (a) assess each Subprocessor’s security and privacy practices before engaging it; (b) impose, by written contract, data protection obligations that are no less protective than those in this DPA, as appropriate to the service the Subprocessor provides; and (c) remain responsible for each Subprocessor’s performance of those obligations to the same extent as for its own.
6.3 Notice of new Subprocessors. At least [SUBPROCESSOR_NOTICE_DAYS] days before a new Subprocessor begins processing Customer Personal Data, Synapse will update the Subprocessors page and send an email notice to subscribed contacts. Customers can subscribe by writing to [PRIVACY_EMAIL], as described on the Subprocessors page. Customer is responsible for keeping at least one current contact subscribed.
6.4 Right to object. Customer may object to a new Subprocessor on reasonable data protection grounds by writing to [PRIVACY_EMAIL] within the notice period. The parties will discuss the objection in good faith. Synapse may propose an alternative, such as not using the Subprocessor for Customer’s Workspaces, routing AI Features to a different permitted model provider, or disabling the affected feature. If the parties cannot resolve the objection within 30 days after Synapse receives it, Customer may terminate the affected Order by written notice, and Synapse will refund prepaid fees for the unused remainder of the terminated Term. This is Customer’s sole remedy for an unresolved objection.
6.5 Urgent replacement. If Synapse must replace a Subprocessor urgently to protect the security or continuity of the Service, it may do so and will give notice as soon as reasonably practicable. Customer’s right to object under Section 6.4 then runs from the date of that notice.
7.1 Security measures. Synapse implements and maintains the technical and organizational measures described in Annex 2. They are designed to protect Customer Personal Data against Security Incidents and to ensure the ongoing confidentiality, integrity, availability and resilience of the systems that process it. Additional detail is available in the Security Overview.
7.2 Updates. Synapse may update these measures as technology and threats evolve, provided that updates do not materially reduce the overall protection of Customer Personal Data during Customer’s current Term.
7.3 Customer security. Customer is responsible for securing its own use of the Service, including account credentials, identity provider and SSO configuration, user provisioning and deprovisioning, role and sharing settings, API keys, webhook signing secrets and AI exclusion settings.
8.1 Notice. Synapse will notify Customer without undue delay, and in any event within [BREACH_NOTICE_HOURS] hours, after becoming aware of a Security Incident. Notice is sent by email to Customer’s Workspace owners and to any security or privacy contacts Customer has designated.
8.2 Content of notice. To the extent known at the time, the notice will describe: (a) the nature of the Security Incident, including the categories and approximate number of data subjects and records concerned; (b) its likely consequences; (c) the measures taken or proposed to address it and mitigate its effects; and (d) a contact point for further information. Where information is not available at once, Synapse will provide it in phases without undue delay.
8.3 Response. Synapse will promptly take reasonable steps to contain, investigate and remediate the Security Incident, cooperate with Customer, and provide information Customer reasonably needs to meet its own notification obligations to supervisory authorities and affected individuals.
8.4 No admission. Notice of a Security Incident is not an acknowledgment of fault or liability. Unless required by law, Synapse will not notify Customer’s data subjects or supervisory authorities about a Security Incident on Customer’s behalf without Customer’s approval.
9.1 Self-service tools. The Service lets Customer access, correct, export and delete Customer Personal Data through the admin console, export tools and the Synapse API.
9.2 Requests received by Synapse. If Synapse receives a request from a data subject or consumer relating to Customer Personal Data, it will direct the requester to Customer, where the request identifies Customer, and will not otherwise respond unless Customer authorizes it or the law requires it.
9.3 Assistance. Where Customer cannot fulfill a request using the self-service tools, Synapse will provide reasonable assistance, taking into account the nature of the processing.
9.4 Government and third-party requests. If Synapse receives a legally binding request from a public authority or other third party for Customer Personal Data, Synapse will attempt to redirect the requester to Customer, notify Customer promptly unless legally prohibited, challenge requests it reasonably considers unlawful or overbroad, and disclose only the minimum information the request lawfully requires.
10.1 Documentation. On written request, and subject to confidentiality obligations, Synapse will make available the information reasonably necessary to demonstrate its compliance with this DPA. This may include:
10.2 Audits. If that information is not sufficient to demonstrate compliance, or an audit is required by a supervisory authority or follows a Security Incident, Customer or an independent auditor bound by confidentiality (and not a competitor of Synapse) may audit Synapse’s compliance with this DPA, subject to the following conditions:
10.3 Results. Customer will share audit findings with Synapse and treat them as Synapse’s confidential information. Audits under Clause 8.9 of the SCCs are carried out in accordance with this Section 10.
11.1 During the Term. Customer may export or delete Customer Personal Data at any time using the export tools and API. Admin-configured retention settings, such as retention periods for meeting audio and transcripts, apply automatically.
11.2 After termination. After Customer’s final Term ends, Customer may request an export of Customer Personal Data for [DATA_RETENTION_PERIOD]. Synapse then deletes it from production systems. Copies in backups are deleted as those backups expire within [BACKUP_RETENTION_PERIOD] and remain protected by this DPA until deletion.
11.3 Legal retention. Synapse may retain Customer Personal Data where applicable law requires it, only for as long as required, and subject to the confidentiality and security obligations of this DPA. Retained data will not be processed for any other purpose.
11.4 Model providers. Deletion of any Customer Personal Data held by model providers follows the retention terms in Section 5.5.
11.5 Certification. On written request, Synapse will certify in writing that deletion has been completed.
12.1 Hosting locations. Synapse is based in the United States. On all plans, Customer may select the European Union or the United States as the hosting region for its Workspaces, from the regions available ([DATA_REGIONS]). Synapse and its Subprocessors may access or process Customer Personal Data from other locations to provide support, security and AI Features, as listed on the Subprocessors page and subject to this Section 12.
12.2 Transfers from the EEA. For Restricted Transfers subject to the GDPR, the SCCs are incorporated into this DPA by reference and completed as follows:
12.3 Transfers from the United Kingdom. For Restricted Transfers subject to the UK GDPR, the UK Addendum is incorporated into this DPA by reference and completed as follows: Table 1 with the party details in Annex 1; Table 2 with the modules and clause selections in Section 12.2; Table 3 with Annexes 1 and 2 and the Subprocessors page; and Table 4 so that neither party may end the UK Addendum under its Section 19. Where the UK International Data Transfer Agreement is required instead, the parties will enter into it on request with equivalent content.
12.4 Transfers from Switzerland. For Restricted Transfers subject to the FADP, the SCCs apply as set out in Section 12.2 with these changes: the Swiss Federal Data Protection and Information Commissioner is the competent supervisory authority for transfers governed by the FADP; references to the GDPR include the FADP; and references to “Member State” are read to allow data subjects in Switzerland to bring claims in their place of habitual residence.
12.5 Transfer assessments. Synapse will provide reasonable information about its processing and the laws that apply to it to help Customer complete any required transfer impact assessment.
12.6 Replacement mechanisms. If a transfer mechanism is invalidated, amended or replaced, Synapse may adopt an alternative lawful mechanism, such as an updated version of the SCCs, and will notify Customer.
13.1 Business purposes. Synapse processes Customer Personal Data as a service provider for the limited and specified business purposes of providing, securing, maintaining, supporting and improving the Service under the Agreement, and for the other purposes that the CCPA and its regulations permit for service providers.
13.2 Restrictions. Synapse will not:
13.3 Compliance. Synapse will comply with the CCPA obligations that apply to service providers, provide the same level of privacy protection the CCPA requires of businesses, and notify Customer if it determines that it can no longer meet its obligations under the CCPA.
13.4 Customer rights. Customer may take reasonable and appropriate steps, including through Section 10, to ensure that Synapse uses Customer Personal Data consistently with Customer’s CCPA obligations. On notice, Customer may take reasonable and appropriate steps to stop and remediate unauthorized use.
13.5 Consumer requests. Synapse will cooperate with consumer requests as described in Section 9, including requests to delete, correct and know, and will pass relevant deletion instructions to its own service providers and contractors.
13.6 Deidentified data. Where Synapse receives deidentified information from Customer, it will take reasonable measures to ensure the information cannot be associated with a consumer or household, maintain and use it only in deidentified form, and not attempt to re-identify it.
13.7 Subcontracting. Synapse engages service providers and contractors to process Customer Personal Data only under written contracts that bind them to obligations consistent with this Section 13.
13.8 Certification. Synapse certifies that it understands the restrictions in this Section 13 and will comply with them.
13.9 Other US state laws. Where the consumer privacy laws of Colorado, Connecticut, Texas, Virginia or another US state apply, Synapse, as processor, will: follow Customer’s documented instructions; ensure that each person processing Customer Personal Data is subject to a duty of confidentiality; delete or return Customer Personal Data when the provision of the Service ends, in accordance with Section 11; make available information needed to demonstrate compliance and allow assessments in accordance with Section 10; and engage subcontractors only under written contracts with equivalent obligations, after giving Customer an opportunity to object under Section 6.
Each party’s liability arising out of or related to this DPA, whether in contract, tort or any other theory, is subject to the limitations and exclusions of liability in the Agreement, except where Data Protection Laws or the SCCs do not permit those limitations, including with respect to rights of data subjects under the SCCs.
15.1 Duration. This DPA remains in effect for as long as Synapse processes Customer Personal Data, even after the Agreement ends.
15.2 Changes. Synapse may update this DPA to reflect changes in Data Protection Laws, decisions of supervisory authorities or courts, or changes to the Service, provided that updates do not materially reduce the protection of Customer Personal Data during Customer’s current Term. Synapse will notify Workspace owners of material changes in advance.
15.3 Governing law. Except where the SCCs or the UK Addendum require otherwise, this DPA is governed by the law that governs the Agreement.
15.4 Severability. If any provision of this DPA is found invalid or unenforceable, the remaining provisions remain in full effect.
Send questions about this DPA, subprocessor objections and data protection requests to:
[LEGAL_ENTITY_NAME]Report suspected security issues to [SECURITY_EMAIL]. If Synapse is required to appoint a representative in the European Union or the United Kingdom, the representative’s contact details will be published in the Legal Center.
| Detail | Data exporter | Data importer |
|---|---|---|
| Name | Customer, as identified in the Agreement or account records | [LEGAL_ENTITY_NAME] |
| Address | As provided in Customer’s account or Order records | [REGISTERED_ADDRESS] |
| Contact | Workspace owner or privacy contact designated by Customer | Privacy team, [PRIVACY_EMAIL] |
| Activities | Use of the Service for project, task, meeting, document and capacity management | Provision of the Service under the Agreement |
| Role | Controller, or processor on behalf of its own controllers | Processor, or subprocessor where Customer is a processor |
| Signature and date | Deemed signed on acceptance of the Agreement | Deemed signed on acceptance of the Agreement |
For transfers under the SCCs, the competent supervisory authority is the authority of the EEA Member State where Customer is established or, where Customer is not established in the EEA, the authority of the Member State where Customer’s representative is established or where the data subjects concerned are located. For UK transfers, it is the UK Information Commissioner’s Office. For Swiss transfers, it is the Swiss Federal Data Protection and Information Commissioner.
This annex describes the categories of controls Synapse maintains to protect Customer Personal Data. Specific implementations may change over time in accordance with Section 7.2. More detail is available in the Security Overview.
| Control category | Measures |
|---|---|
| Security governance | A documented information security program led by Synapse’s Head of Security & Compliance, written policies reviewed on a regular schedule and after material changes, risk assessments and management oversight. |
| Personnel security | Background checks where permitted by law, confidentiality agreements, security and privacy training at onboarding and on a recurring basis, and a disciplinary process for policy violations. |
| Customer access controls | Google and Microsoft OAuth sign-in on all plans; SAML 2.0 and OIDC single sign-on on Business and Enterprise plans; SCIM 2.0 provisioning, domain capture and custom roles on Enterprise plans; role-based access control, guest controls and Workspace audit logs. |
| Internal access controls | Least-privilege access to production systems, multi-factor authentication, time-limited elevated access, logging of administrative actions, periodic access reviews and prompt revocation when personnel leave. |
| Encryption | Encryption of Customer Personal Data in transit using TLS 1.2 or higher and at rest using AES-256, with managed encryption keys and restricted key access. |
| Tenant isolation | Logical separation of each customer’s data, per-Workspace search index isolation, and permission checks applied to every retrieval before results reach a model. |
| AI safeguards | Model routing that enforces each Workspace’s data policy, detection of prompt injection in retrieved content, PII redaction options, validation of outputs against defined schemas, per-Workspace rate limits, human approval gates for agent write actions, and logging of agent actions and Copilot queries. |
| Application security | A secure development lifecycle with peer code review, automated dependency and secret scanning, independent penetration testing ([PENTEST_CADENCE]), risk-based vulnerability remediation, scoped short-lived tokens for agents, and HMAC-SHA256 signatures on webhook payloads. |
| Infrastructure and network security | Hosting with [CLOUD_HOSTING_PROVIDER], network segmentation, restrictive firewall rules, hardened system images, timely patching, denial-of-service protections and API rate limiting. |
| Logging and monitoring | Centralized logging of security-relevant events, automated alerting, on-call response and tamper-resistant storage of audit records. |
| Resilience and backups | Redundant infrastructure, encrypted backups retained for [BACKUP_RETENTION_PERIOD], periodic restore testing and documented business continuity and disaster recovery plans. |
| Incident response | A documented incident response plan with severity classification, defined roles, customer notification in accordance with Section 8 and post-incident reviews. |
| Subprocessor management | Security and privacy due diligence before engagement, written data protection terms, and periodic review of each Subprocessor’s controls. |
| Physical security | Customer Personal Data is stored in data centers operated by Synapse’s hosting provider, which maintain physical access controls. Synapse is a remote-first company and does not store Customer Personal Data on office premises. |
| Data minimization and retention | Admin controls to exclude spaces and fields from AI processing, configurable retention for meeting audio and transcripts, and deletion workflows in accordance with Section 11. |
| Independent assurance | [SOC2_STATUS] |
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.