Security model
1routers security: keys, profiles, and isolation
1routers is designed around one account identity, one active API key, isolated client configuration, and explicit routing choices. Security claims should stay concrete and verifiable.
1routers
Learn how 1routers approaches account identity, local configuration, API keys, and route isolation.
Account identity stays simple
The account email is the unique login credential in the current account model. It is not treated as an editable profile field, reducing ambiguity around ownership and recovery.
One active key
An account keeps one active API key instead of accumulating forgotten credentials.
Reset when exposed
Resetting creates a replacement path while the old credential becomes unusable.
Isolated profile
1routers configuration is kept separate from an existing Codex environment.
Routes are product infrastructure
Model requests necessarily pass through the selected route. Ordinary 1routers usage records store the metering and routing facts needed to operate the service rather than complete prompt or response bodies. Diagnostic handling and retention are described in the Privacy Policy.
This page describes the current product architecture, not a completed compliance certification.
Security is an operating practice
Keep the client current, reset a key that may have leaked, protect the account email, and review route and usage activity from the dashboard.