Subprocessor & Service Provider Inventory
We use the following subprocessors and service providers to deliver Zen Mesh. No customer webhook payloads are sent to any subprocessor. We update this list as service providers materially change.
| Subprocessor | Purpose | Data Access | Region |
|---|---|---|---|
| Google Cloud Platform (GCP) | SaaS control plane (GKE, Cloud Storage) | Encrypted at rest/transit | Toronto, Canada |
| Vercel | Public website hosting | No customer data | Global |
| Stripe | Payment processing (Pro tier) | Billing metadata only | Global |
| GitHub | Source control | No customer data | Global |
| AWS | SaaS and/or data-plane infrastructure for Zen Mesh production deployment | Encrypted operational metadata and customer account/configuration metadata as applicable to deployed components. Customer webhook payload access depends on deployed ingress/data-plane processing path. | Deployment-region specific; AWS regions as available |
Note: AWS is included as a subprocessor/service provider for prod-live deployment readiness.