Security architecture
These are implementation boundaries, not a compliance certification or a promise of provider availability.
Identity and access
ZergAI verifies identity through SSO. ZergRouter owns a separate personal routing scope. Router keys have explicit permissions and can be revoked; browser and administrative sign-in do not implicitly grant inference authority.
Router API keys cannot read personal Codex credentials. Workspace and personal-account access are checked separately.
Credential custody
Provider API credentials are encrypted at rest and are resolved on the server for authorized requests. Hosted Codex account credentials use a separate broker-held encryption key; the web process does not receive that vault key.
Each hosted Codex operation uses a private temporary environment. Revocation disables the account and schedules removal of its live credential record. Logical deletion does not erase encrypted backups or database recovery logs before their own retention expires.
Usage and network metadata
The usage log distinguishes verified caller identity from self-reported client metadata. IP addresses and user agents are hidden from API responses after 90 days; a bounded background cleanup removes stored network fields. Stable caller IDs remain for attribution.
Usage history does not imply zero prompt retention. Data handling also depends on the selected provider, route, and account configuration. See the ZergAI privacy policy and your provider’s terms.
Protect your account
Keep the one-time Router key in a secret store, never in source control or screenshots. Revoke exposed keys and lost devices from the dashboard. A configured USD limit covers priced Router usage; it is not a guarantee against every upstream charge.