Subprocessors
Last updated: 6 May 2026
Trinity Bridge uses the third-party subprocessors listed below to deliver its products (including Trinity Yasha, Trinity AI University, and our consulting + advisory services). Each subprocessor is bound by a Data Processing Agreement where applicable and processes only the customer data necessary to perform its function.
By using our services, customers consent to use of these subprocessors. Material changes (new subprocessor, removal of a subprocessor, or change to processing region) are announced to customers at least 30 days before they take effect via in-app notice and email to billing contacts. Customers may object during the notice period; an unresolved objection is grounds for termination per the Master Services Agreement.
Active subprocessors
| Name | Purpose | Region | DPA |
|---|---|---|---|
OpenAI, L.L.C. USA | LLM inference for measurement, content generation, image generation, brand strategy Brand metadata, queries, content drafts | USA | View |
DataForSEO Cyprus | Google SERP rank, AI Overview detection, competitor SERP feature matrix Brand queries, geographic targeting | EU + USA | View |
Resend, Inc. USA | Outbound transactional + sequence emails on customer's behalf Recipient email + content | USA | View |
Stripe, Inc. USA | Payment processing, subscription billing Billing email, payment method, transaction history | USA + EU | View |
Supabase, Inc. USA | Authentication, JWT issuance, session management Email, hashed password, session tokens | USA | View |
Cloudflare, Inc. USA | DNS, edge CDN, DDoS, WAF Request metadata, IP addresses | Global anycast | View |
IONOS SE Germany | Compute (CapRover hosts), persistent volumes All Service data at rest | EU | View |
GitHub, Inc. (Microsoft) USA | Source code, CI/CD, issue tracking Code only — no customer data | USA | View |
Anthropic, PBC USA | Code-authoring assistance during development Code only — no customer data | USA | View |
Sub-subprocessors
The active subprocessors above may use sub-subprocessors (e.g., AWS for OpenAI compute). Customers acknowledge that Trinity Bridge has no contractual relationship with sub-subprocessors and relies on each direct subprocessor's DPA terms to govern that chain.
Removed subprocessors
None as of the date above. When a subprocessor is removed, the entry remains here for 12 months tagged with the removal date for customer records.
Data residency
Trinity Bridge does not currently offer data residency guarantees. Compute, storage, and processing happen primarily in the EU (IONOS, Frankfurt) and USA (subprocessor cloud regions). Customers requiring strict data residency (e.g., EU-only) should contact us before signing up.
Customer responsibilities
- Ensuring you have legal basis to send any third-party data (e.g., recipient email addresses) into our services
- Configuring channel + CRM integrations only with credentials you're authorized to use
- Notifying your end-users (e.g., subscribers receiving emails sent via our services) per applicable law
Questions
Email privacy@trinitybps.com with subject [SUBPROCESSORS].