Account security and data regions

Registration, sign-in and recovery#

Create an account using the email verification or external sign-in options currently shown. Confirm your email and account identity before configuring keys, payments and agents. Use email recovery for forgotten passwords rather than sending passwords or full keys to support.

Manage profile and passkeys from the account page. Give passkeys recognizable device names, remove devices no longer in use and retain an available recovery method.

Session state and reauthentication#

Use the sign-in action when the console reports invalid credentials. Browser sessions, restored tabs, CLI authorization and model API keys are separate paths; first determine whether the error is in console authentication or model inference.

Data region settings#

Data Region displays available regions and network information. Read its constraints before changing preferences, especially for an account already assigned to a region. A routing preference does not imply immediate migration of existing data or guarantee the model provider processes everything in that region.

Application privacy practices#

• Minimize personal or sensitive business data sent to models and redact as appropriate.
• Manage retention separately for application logs, model context, uploaded files and support attachments.
• Review the site privacy policy and actual provider processing requirements; a gateway hostname is not a zero-retention guarantee.