Legal
Subprocessors
Last updated August 2026
Infrastructure hosting
The production reference architecture uses Amazon Web Services for network, compute, managed PostgreSQL, cache, object storage, secrets, logging, monitoring, DNS, certificates, and edge protection. The final contracting entity, service region, and transfer mechanism must match the customer's deployment and executed agreement.
Model processing
Anthropic is the currently implemented live-model provider integration. It receives only the request context selected for an agent run when that provider is configured and chosen. Test fixtures and local development do not constitute provider processing. Additional providers must be added to this register before production routing uses them.
Payments and communications
Stripe processes checkout, subscription, invoice, and payment-webhook data for paid plans. A deployment may configure an email delivery provider for verification, reset, approval, and operational notices. The specific email provider and processing location must be recorded here before it handles production customer data.
Optional telemetry
OpenTelemetry can export traces and metrics to the endpoint selected by the operator. Error and product-analytics integrations are optional and remain inactive when their configuration is absent. An operator must assess and list the actual telemetry recipient before enabling it with production data.
Changes and due diligence
This engineering register identifies implemented provider paths; it is not a final data processing annex. Procurement and qualified counsel must confirm legal entity names, purposes, data categories, locations, safeguards, and customer-notice obligations before production launch and whenever a provider changes.