Datenschutz

Your sign-in provider or email registration supplies account details. The existing account system handles authentication. API keys are represented by a non-reversible hash and masked prefix after creation.

State and questions are sent to the configured inference provider. Usage records contain identifiers, model, status, counts, cost, and timing rather than prompt content. Provider data practices also apply.

Configured payment providers process checkout information. The service keeps order and credit records needed to reconcile purchases and usage.

The browser uses session and language preference cookies. Feature announcements store a browser-local read flag per announcement, without account or request data. API secrets are held only in the one-time creation dialog, not localStorage. Account settings provide available account-management options.

These pages describe this implementation. Additional commercial terms or retention periods must be supplied by the operator before they are represented as promises.