Core platform

Hosting identified by the deployment definitions; operator confirmation of the running configuration is required.

• DigitalOcean

  Purpose:

  Hosting, database, object storage and job execution

  Data:

  Data entered into the corresponding feature; account and application data for infrastructure.

  Region:

  Processing region depends on the configured service and provider terms; not verified by this directory.

  Trigger:

  Deployment definitions target DigitalOcean; running configuration must be confirmed by the operator.

Optional & feature-gated

These pathways receive data when their corresponding credentials, integrations or telemetry settings are used. AI providers can process core ticket and message content.

• Cloudflare

  Purpose:

  Bot-check (Turnstile) verification on protected forms; Cloudflare operations an organization requests for its own sites; desktop app download hosting

  Data:

  Data entered into the corresponding feature; account and application data for infrastructure.

  Region:

  Processing region depends on the configured service and provider terms; not verified by this directory.

  Trigger:

  Only when the corresponding integration, credential, feature or telemetry setting is used.

• Google Cloud

  Purpose:

  Configured Google storage, speech transcription and Vertex AI

  Data:

  Configured storage contents, speech audio, screenshots and transcript text for AI summaries

  Region:

  Processing region depends on the configured service and provider terms; not verified by this directory.

  Trigger:

  Only when the corresponding integration, credential, feature or telemetry setting is used.

• OpenRouter

  Purpose:

  AI prompts, code context and embeddings; underlying model providers also process requests

  Data:

  Ticket content, related code context and attachments, source code, message text and embeddings

  Region:

  Processing region depends on the configured service and provider terms; not verified by this directory.

  Trigger:

  Only when the corresponding integration, credential, feature or telemetry setting is used.

• Anthropic

  Purpose:

  Direct AI requests when the organization supplies its own credential

  Data:

  Data entered into the corresponding feature; account and application data for infrastructure.

  Region:

  Processing region depends on the configured service and provider terms; not verified by this directory.

  Trigger:

  Only when the corresponding integration, credential, feature or telemetry setting is used.

• OpenAI

  Purpose:

  Direct AI requests when the organization supplies its own credential

  Data:

  Data entered into the corresponding feature; account and application data for infrastructure.

  Region:

  Processing region depends on the configured service and provider terms; not verified by this directory.

  Trigger:

  Only when the corresponding integration, credential, feature or telemetry setting is used.

• Resend

  Purpose:

  Transactional email recipients and message content

  Data:

  Data entered into the corresponding feature; account and application data for infrastructure.

  Region:

  Processing region depends on the configured service and provider terms; not verified by this directory.

  Trigger:

  Only when the corresponding integration, credential, feature or telemetry setting is used.

• Stripe

  Purpose:

  Checkout, subscriptions, billing details and refund requests

  Data:

  Data entered into the corresponding feature; account and application data for infrastructure.

  Region:

  Processing region depends on the configured service and provider terms; not verified by this directory.

  Trigger:

  Only when the corresponding integration, credential, feature or telemetry setting is used.

• Sentry

  Purpose:

  Configured error diagnostics and sampled telemetry

  Data:

  Data entered into the corresponding feature; account and application data for infrastructure.

  Region:

  Processing region depends on the configured service and provider terms; not verified by this directory.

  Trigger:

  Only when the corresponding integration, credential, feature or telemetry setting is used.

• Expo

  Purpose:

  Push device tokens and notification content

  Data:

  Device push token, notification title/body/link

  Region:

  Processing region depends on the configured service and provider terms; not verified by this directory.

  Trigger:

  Only when the corresponding integration, credential, feature or telemetry setting is used.

• Google Analytics 4

  Purpose:

  Consent-gated usage events

  Data:

  Data entered into the corresponding feature; account and application data for infrastructure.

  Region:

  Processing region depends on the configured service and provider terms; not verified by this directory.

  Trigger:

  Only when the corresponding integration, credential, feature or telemetry setting is used.

• ipapi.co

  Purpose:

  Opt-in IP geolocation

  Data:

  Data entered into the corresponding feature; account and application data for infrastructure.

  Region:

  Processing region depends on the configured service and provider terms; not verified by this directory.

  Trigger:

  Only when the corresponding integration, credential, feature or telemetry setting is used.

• GitHub

  Purpose:

  Connected repository data and configured writes

  Data:

  Data entered into the corresponding feature; account and application data for infrastructure.

  Region:

  Processing region depends on the configured service and provider terms; not verified by this directory.

  Trigger:

  Only when the corresponding integration, credential, feature or telemetry setting is used.

• Klaviyo

  Purpose:

  Configured marketing contacts and email

  Data:

  Data entered into the corresponding feature; account and application data for infrastructure.

  Region:

  Processing region depends on the configured service and provider terms; not verified by this directory.

  Trigger:

  Only when the corresponding integration, credential, feature or telemetry setting is used.

• Apollo.io

  Purpose:

  Configured prospecting inputs and contacts

  Data:

  Data entered into the corresponding feature; account and application data for infrastructure.

  Region:

  Processing region depends on the configured service and provider terms; not verified by this directory.

  Trigger:

  Only when the corresponding integration, credential, feature or telemetry setting is used.

• Postiz

  Purpose:

  Configured social scheduling content

  Data:

  Data entered into the corresponding feature; account and application data for infrastructure.

  Region:

  Processing region depends on the configured service and provider terms; not verified by this directory.

  Trigger:

  Only when the corresponding integration, credential, feature or telemetry setting is used.

• Twilio

  Purpose:

  Configured calls, SMS and telephony metadata

  Data:

  Data entered into the corresponding feature; account and application data for infrastructure.

  Region:

  Processing region depends on the configured service and provider terms; not verified by this directory.

  Trigger:

  Only when the corresponding integration, credential, feature or telemetry setting is used.

Data residency

Deployment definitions target DigitalOcean. Storage, AI and optional integrations depend on configuration. Google Vertex AI defaults to a global endpoint; a global endpoint does not guarantee a processing location. We do not offer EU-only processing or per-customer residency guarantees. This code-derived inventory does not certify the current production configuration or vendor contracts.

Get notified when this list changes

This page is generated from one source, so a change here is a real change — adding or removing a subprocessor, or a change to what it receives or where it operates — not a wording edit. Subscribe with any RSS/Atom feed reader to be notified automatically:

Subscribe via RSS/Atom — /subprocessors/feed.xml

Change history

• 7 October 2026 — Code-derived processing pathways. Corrected hosting disclosures and listed optional direct AI and infrastructure pathways. Configuration and provider terms determine actual processing.
• 14 September 2026 — Google Analytics 4: expanded the named event set. Google Analytics 4 (used only with your consent — see "Cookies & tracking" on the Privacy Policy) now also records a handful of named product-milestone events beyond signup and plan upgrade: onboarding completion, project and testing-mission creation, and invite sent/accepted. No new subprocessor, and no free-text or personal data in any event parameter — same consent gate as before.
• 31 August 2026 — Subprocessor list published. Published the current subprocessor list and data-residency answers, generated directly from the codebase and infrastructure configuration rather than templated boilerplate.