Skip to app content

Data Processing Agreement

Last updated: November 11, 2026

This Data Processing Agreement ("DPA") forms part of the agreement between Synter, LLC, with offices at 525 Third St., Suite 200, Lake Oswego, OR 97034, USA ("Synter", the "Processor") and the customer entity that has entered into the Agreement ("Customer", the "Controller"), and reflects the parties' agreement with regard to the Processing of Personal Data under the Agreement.

To execute this DPA, request a countersigned copy, or request our HIPAA Business Associate Agreement on a CUSTOM plan, contact privacy@synterai.com. The current sub-processor list is published at /legal/subprocessors, and healthcare privacy controls are documented at /legal/hipaa.

1. Definitions

"GDPR" means Regulation (EU) 2016/679, including as incorporated into United Kingdom law (the "UK GDPR") where applicable. "Personal Data", "Processing", "Controller", "Processor", "Data Subject", "Personal Data Breach", and "Supervisory Authority" have the meanings given in the GDPR. "Customer Personal Data" means Personal Data Processed by Synter on behalf of Customer in connection with the Services, as described in Annex 1. "Standard Contractual Clauses" or "SCCs" means the clauses adopted by the European Commission in Implementing Decision (EU) 2021/914.

2. Scope and Roles

With respect to Customer Personal Data, Customer is the Controller (or a Processor acting on behalf of a third-party Controller) and Synter is the Processor. Customer is responsible for the lawfulness of the Personal Data it makes available to Synter, including lawful basis, notices, and any required consents (including consents for cookies, advertising identifiers, and the Synter Pixel on Customer's properties). This DPA does not apply to Personal Data that Synter Processes as an independent Controller (for example, workspace user registration and billing contacts), which is governed by Synter's Privacy Policy. This DPA also does not apply to non-personal aggregate campaign metrics (such as campaign-level impressions, clicks, spend, and conversion counts) or anonymized data that is no longer Personal Data, as described in the Terms of Service and Privacy Policy. Synter will not treat data as anonymized if it remains reasonably re-identifiable.

3. Processing on Documented Instructions & Zero-Data-Retention

Synter Processes Customer Personal Data only on Customer's documented instructions, including with regard to international transfers, unless required by applicable law (in which case Synter informs Customer unless prohibited). Instructions are documented in the Agreement, this DPA, and Customer's configuration of and interaction with the Services (including Workspace Zero-Data-Retention settings). By default, records queried from Customer's connected data warehouses, CRM systems, ecommerce customer tables, and audience connectors are processed transiently in volatile memory during the active agent execution to compute aggregate operational context and are redacted prior to database persistence.

4. Confidentiality

Persons authorized to Process Customer Personal Data are bound by confidentiality obligations and Process Customer Personal Data only as necessary to provide the Services.

5. Security

Synter implements and maintains appropriate technical and organizational measures as described in Annex 2, in accordance with Article 32 GDPR, and may update them provided the overall level of protection is not materially reduced.

6. Sub-processors

Customer provides general written authorization for the sub-processors listed at /legal/subprocessors (Annex 3). Synter provides at least 14 days' notice before a new sub-processor Processes Customer Personal Data. Customer may object on reasonable, documented data protection grounds; if unresolved, Customer may terminate the affected Services with a pro-rata refund of prepaid fees. Synter imposes materially equivalent data protection obligations on each sub-processor and remains fully liable for their performance.

7. Data Subject Rights

Synter assists Customer, insofar as possible, in fulfilling Customer's obligations to respond to Data Subject requests. Because CRM, warehouse, and audience records are processed ephemerally without raw row retention, Customer remains the primary system of record for those datasets; for any first-party Pixel or Landing Page records retained in standard workspace mode, Synter supports prompt erasure and export upon instruction. Requests received directly by Synter are forwarded promptly to Customer.

8. Personal Data Breach Notification

Synter notifies Customer without undue delay, and in any event within 48 hours, after becoming aware of a Personal Data Breach affecting Customer Personal Data, with the information reasonably required for Customer to meet its obligations under Articles 33 and 34 GDPR. Information may be provided in phases.

9. DPIA Assistance

Synter provides reasonable assistance with data protection impact assessments and prior consultations with Supervisory Authorities, to the extent they relate to the Services.

10. Deletion and Return

Data processed under ephemeral read-only connectors or Workspace Strict Zero-Data-Retention mode is discarded from volatile memory at the conclusion of the request or conversion relay. On termination of the Agreement, at Customer's choice, Synter deletes or returns any remaining Customer Personal Data (absent a legal retention requirement) within 30 days of termination; encrypted database backups rotate out within 90 days.

11. Audits

Synter makes available information reasonably necessary to demonstrate Article 28 compliance, including available audit reports and responses to written security questionnaires (at most once per 12-month period, except after a breach or where required by a Supervisory Authority). Where that is insufficient, Customer or an independent auditor may audit on at least 30 days' written notice, at most once per 12-month period, under reasonable scope and confidentiality terms.

12. International Transfers

Synter and its sub-processors Process Personal Data in the United States and other countries outside the EEA/UK. For EEA transfers without an adequacy decision, the parties enter into the SCCs, Module Two (Controller to Processor), incorporated by reference and completed by Annexes 1-3 (Clause 7 included; Clause 9(a) Option 2 with the notice period in Section 6; Clause 17/18: Ireland). The UK Addendum and Swiss adaptation apply to UK and Swiss transfers respectively. Synter is not currently certified under the EU-U.S. Data Privacy Framework; the SCCs are the operative transfer mechanism.

13. Liability, Precedence, Term

Liability is subject to the limitations in the Agreement except where prohibited by law. In case of conflict, the SCCs prevail over this DPA, which prevails over the Agreement. The DPA remains in force for as long as Synter Processes Customer Personal Data.

Annex 1: Details of Processing

  • Subject matter: Provision of the Synter autonomous advertising infrastructure (cross-platform campaign management, ephemeral CRM and data warehouse context extraction, server-side conversion relay, hosted landing pages, and AI-agent-assisted ad operations).
  • Data Subjects: Visitors to Customer's websites and Synter-hosted landing pages; contacts in Customer's connected CRM, ecommerce, or data warehouse systems queried ephemerally at Customer's instruction; Customer's authorized workspace operators.
  • Categories of Personal Data & Retention Tier:
    1. Ephemeral Connector Data (Zero Persistence at Rest): Records queried from BigQuery, Snowflake, Databricks, Azure Data Lake, HubSpot, Salesforce, Attio, Pipedrive, Klaviyo, Loops, and Shopify customer/order endpoints are read in volatile memory solely during the active execution turn and stripped prior to database storage.
    2. First-Party Conversion & Lead Relay Data: Online identifiers (click IDs, IP addresses, user-agent strings) and form fields submitted via the Synter Pixel or Synter-hosted landing pages. When Workspace strict_zdr or hipaa_baa mode is enabled, Synter relays these fields in memory to Customer's configured CRM and ad platform CAPI endpoints and scrubs Personal Data fields prior to database persistence.
  • Special categories / Regulated Health Data: Not permitted on SOLO or SCALE plans. Regulated healthcare entities on a CUSTOM plan with an executed HIPAA Business Associate Agreement and Workspace hipaa_baa mode enabled are governed by the HIPAA BAA (see /legal/hipaa).
  • Duration: Ephemeral in-memory lifetime for warehouse/CRM reads and ZDR relays; otherwise the term of the Agreement plus the deletion schedule in Section 10.

Annex 2: Technical and Organizational Measures

  • Zero-Data-Retention Persistence Redaction: Automated persistence gates strip raw rows, SQL/SOQL queries, schema columns, and contact records from agent tool executions, chat transcripts, and tool audit logs before database writes. Thread-scoped masking session state (masking_session_data) retains entity names and identifiers encrypted at rest within the authorized workspace thread solely to restore deterministic aliases across resumed agent runs, and is deleted when the thread or workspace is deleted.
  • Deterministic Memory PII/PHI Scrubbing: Conversational and operational agent long-term memory writes (excluding operator-authored workspace skill templates) pass through a deterministic scrubber that removes email addresses, phone numbers, person names, SSNs, IP addresses, and user-level ad click identifiers prior to vector embedding and storage.
  • Encryption: TLS 1.2+ (TLS 1.3 preferred) enforced in transit; AES-256 encryption at rest across cloud databases, volumes, and OAuth credential vaults.
  • Workspace Isolation & RBAC: Strict organization-scoped data boundaries, role-based access control, MFA and SAML/OIDC SSO support, and Google Secret Manager as the source of truth for credentials (with Doppler runtime secret delivery where configured).
  • Tamper-Evident Operational Audit Trail: Every agent-executed campaign and budget mutation generates an HMAC-SHA256 signed agent_shield_receipt recording actor, timestamp, target account, and policy verdict without storing customer PII.
  • Infrastructure & Sandboxes: Hosted on Google Cloud Platform (Cloud Run) with isolated Daytona container sandboxes for opt-in cloud agent threads; automated backups rotate within 90 days.
  • Zero Model Training: AI inference providers operate under enterprise API agreements prohibiting the use of Customer data to train foundation models. We do not use data received through AI assistant connectors or plugins to train artificial intelligence or machine learning models.

Annex 3: Authorized Sub-processors

The current list is maintained at /legal/subprocessors.


Questions, executed copies, and signature requests: privacy@synterai.com.

Data Processing Agreement | Synter