Sub-processors

Last updated: July 20, 2026

We use the following sub-processors to provide Change Agent. Each processes personal data only on our instructions, under a data-processing agreement (see status below), and only as needed for its stated purpose. Region/transfer details should be confirmed against each provider's current documentation and your account configuration.

Sub-processorPurposePersonal data processedLocationDPA status
WorkOSAuthentication, SSO, MFAIdentity (email, name, auth identifiers)USIn progress
SupabaseApplication database (users, conversation metadata, sessions, usage events, feedback)Identity, conversation metadata, usage, feedback (incl. screenshots)US East (AWS us-east-1, N. Virginia)Signed
OpenRouterLLM request routingPrompts + responses (routed, not stored by OpenRouter; request metadata retained). Retention at the destination provider is listed per provider below.USIn progress
Google (Gemini via Vertex AI)Primary language modelPrompts + responses — zero retention; does not trainUS / EU / Global (OpenRouter-routed; pinned to Vertex — AI Studio endpoints disabled)Via OpenRouter
Meta (Llama)Evaluation-tier language modelPrompts + responses (when used) — retained 30 days; does not trainUSVia OpenRouter
OpenAIText embeddingsSearch query text. Called directly, not routed via OpenRouter; retention governed by OpenAI's API termsUSIn progress
LangChain — LangGraph PlatformAgent orchestration; stores conversation state/checkpointsPrompts + responses (conversation state)US (GCP)Signed
LangChain — LangSmithObservability / tracingPrompts + responses (traces)US (GCP, us-central-1)Signed
VercelFrontend hosting / edgeRequest metadata (IP, user-agent); no conversation content storedUS East (Vercel iad1)In progress
Neo4j AuraKnowledge-base graph (read-only at request time)None user-identifiable (queries only; no user content stored)US (GCP us-east1, South Carolina)In progress

DPA status key. Signed — a data-processing agreement is executed with this provider. In progress — requested or under review. Via OpenRouter — reached through OpenRouter rather than a direct account, so the OpenRouter agreement is the governing contract.

Notes