Subprocessors
Responsibility follows the exact route.
Arc.AI distinguishes core service providers, selected inference endpoints, billing providers, identity providers, and optional connectors. A strict ZDR route excludes any connector that cannot meet its policy.
These rows illustrate the processor categories a production schedule would cover; they are not a legal subprocessor list. Exact legal names, services, countries, and change-notice terms belong in the applicable DPA and deployment schedule.
CategoryPurposeData scopeRegionApplicability
Cloud infrastructureGateway, database, cache, object storageOperational metadata; payload only for request processingConfigured deployment regionCore service
Model providersInference and model executionRequest payload and provider usage metadataEndpoint-specificSelected route only
Payment providersPayment authorization, capture, refund, chargebackPayer, order, payment and risk dataSeller and rail-specificBilling only
Email deliveryInvitations, alerts, documents and account noticesRecipient and delivery metadataProvider-specificControl plane
Identity providersEmail/Google login; OIDC/SAML enterprise SSOIdentity claims and authentication metadataProvider-specificAccount system
Guardrail providersOptional content and security evaluationPolicy-selected input/output subsetConfiguration-specificDisabled on incompatible ZDR routes
Observability providersOptional telemetry exportMetadata by default; payload only by explicit policyCustomer-selectedOptional connector
Data processing termsReview the DPA and deployment-specific processor list.
Contact sales