Skip to content
IQ Routing

Subprocessors

To operate IQ Routing we rely on a small set of third-party subprocessors. The tables below list each one with the purpose it serves and the category of personal data it may process on our behalf. We update this page as subprocessors are added or removed.

Infrastructure and tooling

SubprocessorPurposeData category
VercelMarketing site and dashboard hostingAccount identifiers, request logs
Fly.ioGateway compute and managed Postgres / RedisUsage metadata, account identifiers, encrypted keys
ClerkAuthentication and session managementAccount identifiers, authentication data
StripeBilling and payment processingAccount identifiers, billing data
SentryError monitoring and telemetryDiagnostic data, request metadata
ResendTransactional and digest email deliveryEmail address, account identifiers

Upstream LLM providers

When you route a request, the request and response payloads are transmitted to the upstream provider that serves the chosen model. Three providers are live in production today (OpenAI, Anthropic, Google), with more coming. Separately, to select a model tier, IQ Routing sends a short, truncated excerpt of each routed request's prompt to OpenAI; this routing-classification call runs on IQ Routing's own OpenAI credentials, is independent of any provider key you configure, and is used only to choose a tier, not to generate your response. Each provider's own privacy policy governs the data it receives.

SubprocessorPurposeData category
OpenAIUpstream model inference for routed requests; model-tier routing classification on IQ Routing's own credentials for every routed requestRequest and response payloads; truncated prompt excerpt
AnthropicUpstream model inference for routed requestsRequest and response payloads
GoogleUpstream model inference for routed requestsRequest and response payloads

A Data Processing Addendum (DPA) is available on request. Contact privacy@iq-routing.com to request a copy.

Last updated: July 3, 2026