In this article
A router policy does not establish the behavior of every participant. Separate retention, training use, telemetry and processing location.
Privacy promises are easy to read too broadly. A router may avoid retaining content while sending it to an executor; telemetry can remain, and backup rules may differ. Map the actual request rather than relying on privacy as one general label.
Sources were checked on November 1, 2026. This supports technical comparison and supplier questions, not a determination of legal compliance or a replacement for applicable-terms review.
Separate data categories
List messages, files, outputs, IDs and technical metrics. Map application, router, executor and observation services, identifying each recipient’s data and settings. OpenRouter’s policy separately addresses model-provider practices. An intermediary’s rules do not establish the whole chain.
Preserve the executor’s terms and review date for the chosen model. This keeps conclusions linked to the actual participant rather than the common interface’s brand.
Separate retention and training
No training use does not answer temporary-retention questions. No content storage does not mean no operational records. Ask these separately and explain abbreviations rather than treating them as equivalent guarantees.
Requesty Data Privacy distinguishes payload, telemetry and logging controls. Check the actual organization and key settings. A general description does not prove the required setting is already enabled in your project.
Verify fallback policy
Suppose the primary meets requirements but failure sends the request elsewhere. A successful answer does not establish policy compliance. Check permitted targets and behavior when none remains eligible.
Vercel ZDR controls illustrates filtering by provider conditions and configuration levels. It is one product’s mechanism, not a universal gateway rule. Other services require their own documentation and a test of the selected configuration.
Separate geography and API address
Application region, request-entry location and model-execution location can differ. Specify which property the project requires. For regional routing, check scope and credential-specific exceptions.
Use a participant–data category–period–region–evidence table. Unknown cells should remain questions, not locality assumptions from a domain name. Record who can change logging and executor lists too. A correct initial setup needs controlled changes or future routes can leave the tested boundary without an obvious application modification.
Make verification repeatable
Use synthetic data to test logs, role access and fallback. Preserve configuration and document versions. Repeat significant checks when an executor or route feature changes, because the previous conclusion concerned another chain.
Prepare with hardware security and model versus provider routing.