Provider Logging

Each AI provider that ARouter routes to has its own data handling policies for logging and retention. This page explains what that means for your data, and how to control it.

​

Provider Data Policies

Every upstream provider (OpenAI, Anthropic, Google, DeepSeek, etc.) has its own terms of service governing:

• Whether prompts are used for training
• How long prompts and completions are retained
• Whether responses are logged for abuse detection

ARouter does not alter or override these provider-side policies. When your request reaches a provider, that provider’s own policies apply.

​

Training on Prompts

By default, most major providers (OpenAI, Anthropic, Google) do not train on API traffic under their enterprise or standard API terms. However, policies vary by provider and plan. You can review each provider’s current data policy by checking their official documentation or terms of service page. ARouter surfaces known provider data policies in the Providers reference.

​

Controlling Provider Selection

If your use case requires strict data handling guarantees, you can control which providers ARouter routes to:

1. Specify a provider explicitly — use the provider/model format (e.g., openai/gpt-5.4) to ensure only that provider handles your request.
2. Use an ordered candidate list — set models to a prioritized list of provider-specific model IDs, all of which meet your data requirements.

See Model Routing and Provider Routing for configuration examples.

​

Data Retention by Provider

Below is a general summary. Always verify with the provider’s current terms:

​

Enterprise: In-Region Routing

For enterprise customers with strict data residency requirements, ARouter supports regional routing configurations. Contact support@arouter.ai for details on region-constrained deployments.