Subprocessors
Structure required
Section titled “Structure required”The list below is taken from spec 9.10 and the vendor table in spec 5. Purposes are factual. Locations, transfer mechanisms and the change-notice process are for counsel to confirm.
| Subprocessor | Purpose | Data | Location |
|---|---|---|---|
| Railway | API, worker and console hosting; Postgres database | All customer and account data at rest | To be confirmed |
| Cloudflare | DNS, TLS, WAF and bot management; R2 storage of public source files; docs hosting | Request metadata in transit; public data at rest | To be confirmed |
| Upstash | Redis: rate-limit counters, idempotency cache (24 hours), hot firm cache | Cached responses, request metadata | To be confirmed |
| TypeSafe | Decision model (Jev) | Compact decision inputs (redacted, guarded) | To be confirmed |
| Stripe | Payments for packs and auto top-up | Billing contact and payment data | To be confirmed |
| Resend | Transactional email only (verification, receipts, alerts) | Email address, message content | To be confirmed |
| Doppler | Secrets management | Service secrets, no customer data | To be confirmed |
| Sentry | Error tracking | Error metadata, redacted | To be confirmed |
| Log vendor (Axiom or Grafana Cloud, to be chosen in WP12) | Logs, traces and metrics | Structured logs without bodies, keys or personal data | To be confirmed |
| treg (phase 2) | Vendor data pass-through | Vendor requests the customer makes | To be confirmed |