Provider Note
We never store your prompts or responses. Two exceptions: evals you give us as content, in a chat or through the API (cases, reference outputs, scorer settings, judge and incumbent), which we keep with your account; and eval model outputs, which we keep for up to 90 days (in our replay cache and your eval results), so re-running an unchanged eval doesn't call the models or bill you again, and so you can inspect results. The model providers we route to never train on your data, and they may keep it only for abuse monitoring, for up to 30 days, before deleting it.
Every call BenchRouter sends to a model provider, live or eval, goes only to a provider that does not train on API data, keeps data only for abuse monitoring for at most 30 days, and has every optional retention feature BenchRouter controls (such as caching, stored completions, and request logging) turned off. OpenRouter calls ask OpenRouter to use only providers that do not collect data. A direct provider receives calls only while a dated review of our account with it is on record.
Direct providers are preferred where BenchRouter has a configured direct path. OpenRouter is used as a fallback/gap-filler when a model is not served through a direct provider path. Model providers may act as subprocessors or independent third-party providers depending on the contract path.
Current Subprocessors
| Name | Purpose | Data categories | Policy |
|---|---|---|---|
| Cloudflare | Worker hosting, D1/KV/queue infrastructure, asset hosting, operational logs | Account, route, eval, usage, billing, and operational metadata | https://www.cloudflare.com/privacypolicy/ |
| Google Sign-In | Authentication when you sign in with Google | Google account identifier, email address and name | https://policies.google.com/privacy |
| GitHub | Authentication, GitHub App installation, workflow dispatch, PR/run metadata | GitHub login, repo metadata, installation metadata, workflow and PR metadata | https://docs.github.com/en/site-policy/privacy-policies/github-general-privacy-statement |
| Stripe | Checkout, payments, billing webhooks, ledger references | Billing account, checkout, payment, tax/accounting metadata | https://stripe.com/privacy |
| Google Analytics | Secondary acquisition measurement | Closed event name, pathname, closed CTA name, and Google measurement data when downstream delivery is allowed | https://policies.google.com/privacy |
| OpenRouter | Fallback/gap-filler upstream model routing where no direct provider path is available | Prompts/outputs for routed or eval requests sent through OpenRouter; usage/cost metadata | https://openrouter.ai/privacy |
| Google Vertex AI | Direct model provider path where configured | Prompts/outputs for routed or eval requests served through Vertex; usage/cost metadata | https://policies.google.com/privacy |
| Groq | Direct model provider path where configured | Prompts/outputs for routed or eval requests served through Groq; usage/cost metadata | https://groq.com/privacy-policy |
Changes
We update this page as production subprocessors or direct provider paths change. We do not list aspirational providers that are not used in production.
Contact
Questions about subprocessors or data handling: privacy@benchrouter.com.