Provider Logging

How to route only to providers that match your data policy

Each upstream provider has different retention and training policies. TheRouter.ai lets you filter providers to match your organization's risk profile.

Provider data policy filters

Use provider routing settings to require zero-retention or no-training providers. TheRouter.ai will skip providers that do not satisfy the policy and fallback to compliant options.

TypeScript

const body = {
  model: "anthropic/claude-sonnet-4.5",
  messages: [{ role: "user", content: "Review this contract" }],
  provider: {
    data_collection: "deny",
    require_parameters: true,
    allow_fallbacks: true,
  },
};

EU in-region routing

Enterprise workloads that require EU processing can use region-specific ingress and provider allowlists. Keep model selection constrained to approved in-region endpoints.

eu-routing.sh

curl https://eu.api.therouter.ai/v1/models   -H "Authorization: Bearer $THEROUTER_API_KEY"

Operational caveats

Availability tradeoff

Stricter policy filters reduce the provider pool. Configure explicit fallback models so policy compliance does not turn into avoidable downtime.

Document approved providers and review their terms on a recurring cadence. A policy that was compliant last quarter may change with new model or provider terms.