Trust Center / Subprocessors
Named processors and customer-selected destinations.
This draft distinguishes providers required to operate ChangeWitness from destinations a customer chooses for notification delivery.
| Provider | Relationship | Purpose | Location and Disclosure |
|---|---|---|---|
| Vercel | Core subprocessor | Application hosting, Node.js Functions, global CDN for static assets, routing, logs, preview deployments, and support access. | Frankfurt for core Functions; global delivery and control-plane processing may occur elsewhere. |
| Supabase | Core subprocessor | PostgreSQL, Auth, Queues, Cron, private Storage, backups, logs, and support access. | Frankfurt, eu-central-1, for the selected primary project. Backup details require production confirmation. |
| Resend | Core subprocessor | Transactional email delivery with standard 30-day email-data retention, provider logs, API records, and support. | Ireland sending region. Account data, email metadata, logs, and API records are stored in the United States. |
| Microsoft Azure | Core subprocessor | Azure Key Vault for connector keys and Entra workload identity for access from production compute. | [AZURE KEY VAULT REGION PENDING CONFIRMATION] |
| Stripe | Core subprocessor | Subscription billing, Checkout, Billing Portal, Tax where enabled, invoices, and payment processing. ChangeWitness does not store card details. | Processor locations and transfer terms per Stripe documentation and the final DPA review. |
| Slack | Customer-selected destination | Delivery of notifications to a customer-configured Slack installation or webhook. | Destination-dependent transfer under the customer's Slack configuration. |
| Microsoft Teams | Customer-selected destination | Delivery of notifications to a customer-configured Teams Workflow webhook or supported incoming-webhook mechanism. | Destination-dependent transfer under the customer's Microsoft 365 configuration. |