> For the complete documentation index, see [llms.txt](https://ticketking.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ticketking.xyz/docs/transcripts/how-long-transcripts-stick-around.md).

# How long transcripts stick around

Transcripts are kept indefinitely. There is no expiry.

**Indefinitely.** Transcripts have no expiry and are not pruned automatically. Once a transcript is generated, it stays available. This is marketed as "Lifetime Storage".

## Plan changes

Downgrading from premium to free does NOT delete existing transcripts. They stay accessible.

The only premium difference for transcripts is the **per-transcript message capture cap** (1,000 free, 5,000 premium), set at the time of close. Past transcripts keep the cap they were written with.

→ [Transcript capture limits](/docs/logging/transcript-capture-limits.md)

## Server removal

If you remove Ticket King from your server:

* Existing transcripts stay accessible.
* No new tickets or transcripts can be created.
* Re-adding the bot later restores the same transcript list.

## Transcript viewer versions

New tickets always use the current transcript viewer, version 2. Older version 1 transcripts still open, but they show a notice that version 1 is being retired. If you still need an old version 1 transcript, save a copy.

## Related

{% content-ref url="/pages/Gjspl5mwSsfoYl8bZR1H" %}
[What's in a transcript](/docs/transcripts/whats-in-a-transcript.md)
{% endcontent-ref %}

{% content-ref url="/pages/9LgYeMt3zCRpnojBs9ZU" %}
[Where to find a transcript](/docs/transcripts/where-to-find.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ticketking.xyz/docs/transcripts/how-long-transcripts-stick-around.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.