Transparency
Service providers for the Swain API Integration connector
The providers below help Swain operate, secure, support, and bill for the connector.
Last updated: 12 July 2026
Provider locations describe the configured Swain production service or the provider’s principal processing footprint. Global providers may process support, security, or resilience data in additional locations under their data-processing terms.
| Provider | Purpose | Configured or principal location | Connector data involved |
|---|---|---|---|
| Cloudflare, Inc. | DNS, TLS termination, content delivery, network security, and abuse protection | Global network, including the UK, EEA, and United States | IP address, request metadata, endpoint path, security signals, and transient request traffic |
| Vultr Holdings, LLC / The Constant Company, LLC | Production compute, container runtime, and primary PostgreSQL database hosting | London, United Kingdom | Swain account, OAuth, tenant, connection, schema, tool-request, audit, and operational data |
| Scaleway SAS | Object storage for Swain-managed artifacts and user-image assets | Paris, France (fr-par) |
Stored artifacts or assets associated with a Swain account where the relevant feature is used |
| Functional Software, Inc. (Sentry) | Application error tracking and reliability monitoring | International; processing governed by the configured Sentry account and data-processing terms | Scrubbed error, stack, release, environment, request-ID, and technical diagnostic data; Swain removes request headers, user identity, and known secrets before sending events |
| Twilio Inc. (SendGrid) | Transactional account, lifecycle, password, and service email | International, including the United States | Recipient email address, display name where supplied, message content, and delivery metadata |
| Stripe group companies | Swain account billing, subscriptions, credits, and payment administration | International, including the UK, EEA, and United States | Billing contact, customer and subscription identifiers, transaction metadata, and payment information entered directly into Stripe; MCP tool payloads are not sent to Stripe merely by using the connector |