Security & Data

Your data. Clearly explained.

How standard API calls, browser tools and upstream services handle information.

What does Tokenhot retain?

We process request content, send it to the upstream service and return its response. We do not sell API inputs or outputs or use them to train our own models.

For standard synchronous API calls, our gateway does not persist bodies, including error-body content. Operational records can include IP address, account or request ID, model, time, token counts, charges, status and error codes. Cache billing reflects model or upstream features; it does not mean we store synchronous prompt copies.

The path of a standard synchronous request
  1. Your clientYour app or coding tool
  2. Tokenhot gatewayRoutes requests and responses
  3. Upstream serviceProcesses content to generate a result

Standard synchronous API bodies are not stored by our gateway. Upstream processing follows its own rules.

What changes in the Playground or trials?

Playground history

Conversations, drafts and attachments can be saved in your browser without automatic application expiry. Signing out does not necessarily clear them.

Trial uploads

Uploaded images are private object-storage files shared through time-limited links. Link expiry or removing an input image does not itself delete the stored file.

Asynchronous tasks

These features can use task IDs, statuses and result references. Upstream media can follow separate retention rules.

What about upstream services and website activity?

Upstream retention, caching and training practices vary by provider, model, endpoint and feature. A model brand alone does not identify every service involved.

Support records and website analytics are separate from ordinary gateway logs. Analytics may be associated with account identifiers. Replay masking excludes Playground conversations and model trial input and output areas; other visible content and interactions may still be recorded.

How can I delete saved information?

Remove Playground conversations in the interface or clear browser site storage. Account closure does not automatically remove local history or third-party copies.

Contact hi@tokenhot.ai for account closure, relevant-record deletion or trial-file deletion requests. Retention depends on purpose and legal requirements; there is no single automatic deletion schedule for every record.

Read the full Privacy Policy

The full details, always within reach.

These explanations help you get oriented. The published policies and terms set out the full conditions and exceptions.

Discuss your data requirements

For specific retention, location or contractual requirements, contact hi@tokenhot.ai before submitting the information.