Torve AI

Account, usage and billing information

We process account information to sign you in and manage access. We store API key identifiers, plan assignments, token usage, request metadata and payment/order records to enforce limits, provide support, investigate failures and maintain billing history. Metadata can include model alias, timestamps, response codes, latency, token counts and hashed client network information.

Prompts and images go to a provider

The API gateway relays request content, including images, to the provider configured for the selected model. The gateway’s request telemetry records metadata rather than prompt or response bodies. This does not mean that content never leaves Torve AI: provider processing is required to answer the request, and provider handling may differ by route.

We do not promise a universal retention period or training policy for every third-party provider. Ask support about the current route before sending sensitive material. Public image URLs may be retrieved by that provider; Base64 sends the image bytes in the request.

Playground chat history

When you use the web Playground, we save your messages and the assistant replies in your account so you can reopen chats on another device. These saved chats are separate from API request telemetry. You can delete a chat in the Playground; deleting it removes its saved messages from the active database. A request that fails before a reply may remain only in your current browser tab. Avoid entering passwords or API keys in a chat.

Support conversations

Monu AI support conversations are stored as conversation history and can be reviewed by authorized administrators. Information you provide in support or payment flows may also be retained to resolve the issue. The gateway telemetry policy does not apply to saved support messages. Do not include passwords, API keys or unnecessary private images in support conversations.

Service providers and browser storage

Authentication, hosting, data storage and payment services process information needed to provide their part of the service. Session cookies support sign-in, and browser preferences can remember choices such as theme and language. API credentials should remain in your server environment rather than public client code.

Questions and requests

For questions about your data or a request concerning your account, contact support. Provide enough information to identify the account without sharing secrets. Billing, security or audit obligations may affect which records can be removed.

See our provider availability policy for service limitations.