Subprocessors List
Effective Date: 1 July 2026
TurboHelp uses subprocessors to provide, secure, support, and improve the Services. This list is a template and should be updated before publication to reflect actual vendors in use.
For AI vendors, "Training allowed?" should remain "No" unless TurboHelp has made a deliberate legal and product decision and updated customer-facing terms.
| Subprocessor name | Purpose | Data categories | Location / hosting region | AI vendor? | Training allowed? | Link to subprocessor terms |
|---|---|---|---|---|---|---|
| OpenAI, L.L.C. | AI model inference, generation, classification, summarization, evaluation support | Input, Output, conversation content, metadata needed for AI functionality | [United States / configurable region if available] | Yes | No | [OpenAI terms/DPA URL] |
| Anthropic, PBC | AI model inference, generation, classification, summarization, evaluation support | Input, Output, conversation content, metadata needed for AI functionality | [United States / configurable region if available] | Yes | No | [Anthropic terms/DPA URL] |
| Google LLC / Google Cloud | Cloud services, AI model services, infrastructure, analytics, security tooling | Customer Data, Usage Data, logs, account data, technical metadata | [United States / selected cloud region] | Yes, if AI services enabled | No | [Google Cloud terms/DPA URL] |
| Amazon Web Services, Inc. | Cloud hosting, storage, compute, networking, security, backups | Customer Data, Usage Data, logs, account data, technical metadata | [United States / selected AWS region] | No | No | [AWS terms/DPA URL] |
| Supabase, Inc. | Database, authentication, storage, edge functions, application infrastructure | Customer Data, account data, Usage Data, logs, technical metadata | [United States / selected region] | No | No | [Supabase terms/DPA URL] |
| Stripe, Inc. | Payment processing, billing, invoices, tax support | Billing data, account data, payment metadata, invoice details | [United States / global] | No | No | [Stripe terms/DPA URL] |
| PostHog, Inc. | Product analytics, event tracking, feature usage, experimentation | Usage Data, device/browser data, event data, account/workspace identifiers | [United States / EU / selected region] | No | No | [PostHog terms/DPA URL] |
| Functional Software, Inc. d/b/a Sentry | Error monitoring, performance monitoring, diagnostics | Error logs, stack traces, technical metadata, limited Customer Data if included in errors | [United States / selected region] | No | No | [Sentry terms/DPA URL] |
| Resend, Inc. | Transactional email delivery | Email address, name, message metadata, account and notification content | [United States / global] | No | No | [Resend terms/DPA URL] |
| Twilio SendGrid | Transactional email delivery, email infrastructure | Email address, name, message metadata, account and notification content | [United States / global] | No | No | [SendGrid terms/DPA URL] |
| Slack Technologies, LLC | Internal support notifications, incident coordination, customer-requested integrations | Message metadata, support content if Customer enables Slack integration, account identifiers | [United States / global] | No | No | [Slack terms/DPA URL] |
| [Infrastructure vendor] | [Purpose] | [Data categories] | [Region] | [Yes/No] | No | [Terms URL] |
| [Observability vendor] | [Purpose] | [Data categories] | [Region] | [Yes/No] | No | [Terms URL] |
| [Customer support vendor] | [Purpose] | [Data categories] | [Region] | [Yes/No] | No | [Terms URL] |
Subprocessor Changes
TurboHelp may update this list as vendors change. TurboHelp will provide notice of material new subprocessors by updating this list, email, in-product notice, or another reasonable method.
Customers may object to a new subprocessor on reasonable data protection grounds by contacting [email protected] within thirty (30) days after notice.
AI Vendor Commitments
TurboHelp will contractually restrict third-party LLM providers from using Customer Data to train or improve their own models. Third-party LLM providers may process Input and Output only to provide, secure, monitor, or support AI functionality, subject to applicable subprocessor terms.
Customer-Enabled Integrations
Customer may connect TurboHelp to third-party services chosen by Customer. Customer-enabled integrations are not necessarily TurboHelp subprocessors. Customer is responsible for reviewing and approving integrations and for the data Customer chooses to transmit to them.