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
| Provider | What it does for us | Data | Where |
|---|---|---|---|
| Google Cloud | Hosts 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 information | The Console: us-east1 (South Carolina, USA), backups in nam4 (Iowa and South Carolina, USA). Endpoints: the Google Cloud region you choose |
| Amazon Web Services | Runs endpoints in its regions. | Customer Content of endpoints in its regions; technical and usage information | The AWS region you choose |
| Oracle Cloud Infrastructure | Runs endpoints in its regions. | Customer Content of endpoints in its regions; technical and usage information | The Oracle Cloud Infrastructure region you choose |
| Microsoft Azure | Runs endpoints in its regions. | Customer Content of endpoints in its regions; technical and usage information | The Azure region you choose |
| Cloudflare | DNS 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 keys | For 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
| Provider | What it does for us | Data |
|---|---|---|
| Stripe | Payment 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 |
| Resend | Sends 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 |
| Anthropic | Writes 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. |
| PagerDuty | Pages 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
- Sign-in providers you choose (Google, for Sign in with Google) handle that sign-in under their own terms, and so does your browser's request for this website's fonts (Google Fonts); neither is a sub-processor for your Customer Content.
- This list matches section 6 of the Privacy Policy. When we add a sub-processor, it appears here and in the Privacy Policy.
- Questions, or a signed agreement covering sub-processors: privacy@swengle.com.