Account, key, and data security
Protect accounts and API credentials and handle request sources and sensitive diagnostics.
Protect accounts
Use a unique password and enable available two-factor authentication in account settings. Store backup codes separately from the authenticator. Sign out of shared devices.
Collaborate through team invitations and roles rather than sharing owner passwords, verification codes, or browser cookies.
Protect API keys
Use separate keys for development, testing, production, and different services, with appropriate lines and IP allowlists. Read credentials server-side from environment variables or a secret manager. Browser frontends should call your own application backend.
Keep keys out of source, client packages, URL query parameters, and public frontend environment variables. Do not log complete request headers. Shell history, logs, monitoring events, and screenshots can also retain credentials.
Data and logs
Model requests are sent to the selected model service for processing. Account, usage, order, and task information supports the corresponding services. Playground task data and text API requests may have different handling rules.
Read iRouter's privacy policy and terms for processing scope, retention, model-service data use, and rights requests. API compatibility does not imply identical data commitments across platforms. Confirm retention, location, or enterprise requirements with support before integration.
Respond to exposure
Disable affected keys, inspect unusual usage, replace application credentials, and verify recovery. If login credentials were exposed, change the password and review account security. Support reports should use key names or masked identifiers, not complete keys, verification codes, payment-card details, or sensitive prompts.
See key management for rotation steps.