Sub-processors
Last updated: 2026-05-18
Tripswitch uses the following third-party services (“sub-processors”) to provide the service. This list reflects sub-processors currently processing customer data in production.
| Sub-processor | Purpose | Data categories | Location |
|---|---|---|---|
| Gigalixir | Application hosting (runs on GCP) | All processed data (in-flight and at rest) | US (GCP us-central1, Iowa) |
| Google Cloud Platform | Compute, networking, storage, self-hosted TimescaleDB node | All processed data | US (us-central1, Iowa) |
| Stripe | Payment processing and subscription management | Name, email, billing address, payment-method metadata (card brand, last 4, expiration, country). No card numbers or CVVs ever transit Tripswitch infrastructure. | US |
| WorkOS | Authentication (OAuth via Google / GitHub, magic links) | Name, email, OAuth identifier, session tokens | US |
| Resend | Transactional email (sign-in links, account and billing notifications, alert emails) | Email address, message content | US |
| Fastmail | Inbound support email | Email address, message content of inbound support messages | Australia (with US presence) |
| Redis Cloud (Redis Inc., deployed on GCP) | Caching, rate limiting, session state | Operational data; no customer-identifiable content | US (GCP us-central1, Iowa) |
Notification of changes
We notify customers at least 30 days before a new sub-processor begins processing customer data. Notification is sent by email to account owners and posted to this page.