Security, privacy & routing.
Understand how your requests and account data are handled.
Your prompts and responses
RouterPlex does not store your prompts or responses. We process their content in memory to deliver the model response. We retain usage metadata for billing and abuse prevention.
Your model provider’s own terms apply. Explicitly selected Contributor models may permit provider training on the content you send. Contributor models are never our default or fallback.
Read the full Privacy Policy →Retention and deletion
We retain account data while your account exists and usage metadata for accounting and abuse prevention. After account deletion, we delete or anonymize personal data within 30 days, except records we must legally retain. We have not published a separate fixed retention period for usage metadata.
Request access or deletion ↗Account security
We encrypt traffic in transit with TLS. We store passwords as salted hashes and API keys in hashed or encrypted form. During guided setup, we keep an encrypted recoverable copy of your key until your first successful request.
Report a suspected incident to [email protected]. Do not include API keys or private prompt content.
Contact support about an incident ↗Routing and model identifiers
A model identifier in your usage log can differ from the identifier in your request. We do not guarantee that every requested model is always preserved. We are documenting provider selection, aliases, substitutions, and failure behavior in a complete routing policy.
We do not publish an automatic-failover or quality-preservation guarantee here. Check service status and the returned error details when a request fails. Contributor models are used only when you explicitly request one.
Error documentation ↗Status and evaluations
Check the current service state and available incident history. Review external benchmark snapshots separately from our blind arena, including dates, model versions, methods, and limitations.