Sub-processors

Who else handles your data.

Every third party that processes customer data for SwengleIO, what it does for us, what it receives and where. Customer Content is what your applications send through the Services; account data is what the Console keeps about your organization and its members.

Updated 10 November 2026

Infrastructure

ProviderWhat it does for usDataWhere
Google CloudHosts the Console, its API and the account database; runs endpoints in its regions; Firebase Authentication handles sign-in; Firebase Hosting serves this website.Account data; sign-in credentials and identity; Customer Content of endpoints in its regions; technical and usage informationThe Console: us-east1 (South Carolina, USA), backups in nam4 (Iowa and South Carolina, USA). Endpoints: the Google Cloud region you choose
Amazon Web ServicesRuns endpoints in its regions.Customer Content of endpoints in its regions; technical and usage informationThe AWS region you choose
Oracle Cloud InfrastructureRuns endpoints in its regions.Customer Content of endpoints in its regions; technical and usage informationThe Oracle Cloud Infrastructure region you choose
Microsoft AzureRuns endpoints in its regions.Customer Content of endpoints in its regions; technical and usage informationThe Azure region you choose
CloudflareDNS for our domains. Cloudflare R2 stores encrypted copies of the backups of every region we offer, so they survive the loss of a region or of a cloud provider.Backup copies, encrypted before they leave our cloud: Cloudflare holds ciphertext only, never the keysFor regions in the UK and the EU: the European Union. For other regions: near eastern North America or Asia-Pacific, a preference Cloudflare does not guarantee (by region)

Services

ProviderWhat it does for usData
StripePayment methods, invoices and payments.Your organization's billing details, payment method (card details go to Stripe on its own pages and never reach us), usage billed and invoices
ResendSends the email we send: account and sign-in email, invitations, billing email, incident updates and our operators' alerts.Recipients' email addresses and the emails' contents
AnthropicWrites the Console Assistant's replies with its Claude models, through its API.The chat being answered and what the Assistant looks up in that chat's organization, only as far as the asking person's own permissions allow; never that person's name, email address or picture, other members' email addresses or secret keys. Under Anthropic's commercial terms it does not train its models on them by default.
PagerDutyPages our on-call operator for the most serious alerts.Alerts about our systems, which can name resources such as a cluster's id and its region. No Customer Content and no personal information

These providers process data where they operate; see each provider's own terms.

Notes