Skip to main content
TokenLab keeps operational records for different purposes and with different lifetimes. A 30-day request-capture window does not define the lifetime of task records, billing history, saved assets, or copies held by your application. For the customer-facing policy, see TokenLab data retention.

​
Request and response captures

In the Console, captured request and response details are available for 30 days from capture. Access ends at the exact expiry time; delayed, batched physical cleanup does not extend it. After expiry, the captured content is no longer available, while the request record and related task or billing history may remain under their own lifetimes. A capture that was not saved or could not be read is a separate condition from an expired capture.

​
Generated media URLs

Eligible generated image, video, and audio results available as HTTP(S) media URLs are copied for 30 days. Normal AI-protocol JSON results keep their existing media_retention fields: days and items, with each item reporting url, kind, status, and expires_at. Use metadata=true on a media-result URL to read its current state. A pending (saving) or failed copy is not a guarantee that TokenLab has retained the file. Once expired, the result URL returns HTTP 410. The signed storage URL used to serve a ready copy lasts at most five minutes. That short signature lifetime is separate from the 30-day result lifetime; fetch a fresh URL while the result remains active. Repeated reads do not extend expiry. Manually saving an item to the Media Library creates a separately owned asset with its own lifecycle. The automatic URL-copy retention does not cover 3D model files, Worlds, inline Base64 or binary media, input URLs, or links embedded in generated text. Async terminal task snapshots are also independent of request-capture expiry. Save outputs to storage you control if they must remain available longer.

​
Other records and copies

  • Billing ledger, usage history, and async task records have lifetimes independent of request/response captures.
  • Organization call-record export files expire after 90 days. The export lifetime does not set the lifetime of the underlying usage or billing records.
  • Console and Agent temporary upload references allow new requests for 24 hours. Physical cleanup is a separate process: temporary input objects become cleanup candidates after seven days, subject to accepted-task references and terminal grace. Do not treat reference expiry as proof that the object has already been physically deleted.
  • Agent conversation history is separate from request captures. Browser storage, downloaded files, and copies saved by an Agent or another client are outside TokenLab’s server-side request-capture expiry and follow their own owner or device storage controls.
  • Database backups normally preserve a recoverable chain covering about 7–14 days. They are disaster-recovery copies, not a way to extend customer-facing access; restore handling must reapply ordinary expiry before serving data.
For request troubleshooting, see Logs and troubleshooting. For media task polling, see Async jobs and polling.