How to interpret this table
- Active means required for base hosted runtime.
- Optional means processing occurs only if the customer enables that integration.
- Region is tied to configured deployment or account settings.
This registry helps legal, procurement, and security teams understand where service data may be processed and why. It is updated as integrations evolve.
| Subprocessor | Purpose | Data Categories | Region | Status |
|---|---|---|---|---|
| Railway | Application hosting and persistent runtime storage | LLM telemetry payloads, metadata, and audit data | Per configured project region | Active |
| Anthropic (optional) | LLM quality judge for evaluation and scoring workloads | Truncated prompt/input/output excerpts used for scoring | Per configured account region | Optional |
| Stripe (optional) | Checkout and subscription billing operations | Billing metadata and checkout session attributes | Per configured account region | Optional |
| Resend (optional) | Demo request and sales notification emails | Name, email, company, and message form payload | Per configured account region | Optional |
| Customer-configured Webhook (optional) | Outbound operational and alert notifications | Alert and lead event payloads | Customer-controlled destination | Optional |
Detailed legal basis and flow notes are maintained in the enterprise documentation set:
enterprise/SUBPROCESSOR_LIST_AND_DATA_FLOW_V1.md
Subprocessor changes are reflected in this page and communicated through customer channels in line with contract commitments.