Discord Ticket Transcripts: Retention, Privacy and What to Check
What a Discord ticket transcript is, how long each bot keeps one, who can read the link, how to turn transcripts off, and the privacy rules that apply to them.
Dani, Founder, AI Ticket Bot
5 min readUpdated
What is in a Discord ticket transcript?
The conversation: who said what, in order, with timestamps. On AI Ticket Bot a transcript is stored and published at a token URL under aiticketbot.com/transcripts/, so the record outlives the ticket channel, which is deleted on close to keep the server clean.
That last point is the one people miss. The Discord channel goes away. The transcript is the record. If transcripts are off, closing a ticket destroys the conversation permanently.
Why does transcript retention matter?
Because the moment you need a transcript is never the day the ticket closed. It is:
- Two months later, when a member says your staff promised them a refund.
- When a staff member is accused of being rude and you need the actual exchange.
- When two moderators remember a decision differently.
- When someone asks you to delete their data and you need to know what you hold.
A bot that keeps transcripts for 7 days technically has transcripts. It does not have a record.
| Typical free tier | AI Ticket Bot Free | AI Ticket Bot paid | |
|---|---|---|---|
| Transcripts exist | Usually | Yes | Yes |
| Retention | Varies, often short | 90 days | 730 days |
| Survives channel deletion | Varies | Yes | Yes |
| Public link | Varies | Yes, gated token URL | Yes, gated token URL |
| Can be switched off | Varies | Yes, server-wide | Yes, server-wide |
Retention on paid plans is two years, which covers most dispute and audit windows without you archiving anything by hand.
Who can read a transcript?
This is worth checking on any bot, because "public link" can mean two very different things.
On AI Ticket Bot the transcript URL is gated: it opens for the person who opened the ticket, for anyone with Manage Server, and for staff whose role holds the Read transcripts permission. Not for anyone who happens to have the link. The token is not a secret handshake that leaks the whole conversation to a random visitor.
That middle clause is worth reading twice. Reading transcripts is its own per-role permission rather than something every staff role gets, so a role you created to let somebody teach the AI does not also hand them every conversation your server has ever had.
Open a transcript link in a private window, signed out, before you trust it
Thirty seconds, and it answers the question definitively
Assume a token in the URL means it is private
A long random URL is not an access control, it is an obscure one
Tell members in your panel description that tickets are saved
Silent recording is the problem, not recording
Post a transcript link in a public channel to "prove" what someone said
Even a gated link is a record of a private conversation
If you are evaluating a different bot, the specific question is: can someone who is not in my server read this URL? If yes, treat transcripts as public content and tell your members so.
Can I turn transcripts off?
Yes, and sometimes you should. AI Ticket Bot has a server-wide switch on the Tickets settings tab, with no plan gate. Turning it off means closing a ticket builds and stores nothing and shows no transcript link. The member still gets the close notification, it simply carries no link.
Turn them off when
- Your community handles genuinely sensitive personal matters
- Your legal position is simpler if you hold nothing
- Members have specifically asked you not to retain conversations
Keep them on when
- You need staff accountability, which is most servers
- You resolve disputes about what someone was told
- You onboard new moderators, who learn a lot from reading how good tickets went
- You ever need to answer "what did we actually say to this person"
Transcripts and privacy rules
If you operate in the EU or serve EU members, a transcript is personal data. Three practical consequences:
Tell people
A line in your rules or panel description saying tickets are saved is enough. Silent recording is the problem
Have a deletion path
Someone can ask you to remove their data, and "we cannot" is not an answer
Retain for a reason
Retention that matches a real purpose is defensible. Indefinite "just in case" retention is not
Know what happens when the bot leaves
On our side, all data tied to a server is purged 48 hours after the bot is removed
Our own handling is documented on the privacy page, including which parties process ticket content and for how long.
What about tickets from a connected bot?
Worth knowing if you use /ticket connect to put our AI inside another bot's tickets: external tickets store no messages and no transcripts on our side. The AI answers, but the record belongs to whichever bot created the ticket. Closing stays with that bot too.
If transcripts are your reason for using a ticket bot, the connected setup does not give you ours. That is a genuine limitation of the connect path and it is stated in full in the connect guide.
What to check before you commit
Five questions for any ticket bot
- How long are transcripts kept, in days, on the plan you will actually be on?
- Can a non-member open the link? Test it signed out
- Does the record survive the channel being deleted?
- Can you turn it off entirely if you need to?
- Can you delete a single transcript on request, without deleting everything?
If you are still setting up, the setup walkthrough covers turning transcripts on before you need them rather than after an argument about what someone was told.
Sources and further reading
Keep reading
Frequently asked questions
The saved record of a ticket conversation, produced when the ticket closes and reachable at a link. It matters because the Discord channel is usually deleted on close to keep the server tidy, so the transcript is the only surviving copy of what was said.
It varies by product and by plan, and retention is the number worth checking rather than whether transcripts exist at all. On AI Ticket Bot it is 90 days on the free plan and 730 days on every paid plan. A bot that keeps transcripts for 7 days technically has transcripts but does not have a record.
That depends entirely on the bot, and "public link" can mean two very different things. On AI Ticket Bot the transcript URL is gated: it opens for the person who opened the ticket, for anyone with Manage Server, and for staff whose role holds the Read transcripts permission, not for anyone who happens to have the link. Reading transcripts is its own per-role permission, so a role you created only to teach the AI cannot read every past conversation. On any other bot, test it while signed out before you assume.
On AI Ticket Bot, yes: there is a server-wide switch on the Tickets settings tab with no plan gate. With it off, closing a ticket builds and stores nothing and shows no transcript link. The close notification to the member still goes out, it just carries no link.
If you operate in the EU or serve EU members, yes, a transcript contains personal data. The practical consequences are that you should tell people tickets are saved, have a way to delete a transcript on request, and not retain indefinitely without a reason. Retention that matches a real purpose is defensible; keeping everything forever is not.
Not on our side. If you use the connect feature so our AI answers inside another bot's tickets, those tickets store no messages and no transcripts with us. The record belongs to whichever bot created the ticket, and closing stays with that bot too.
It’s not just an AI, it’s your AI.
See it on your own server.
Add the bot free, teach it a few of your most common answers, and watch it clear the repeat tickets on its own.
Free plan, no card. Your first panel starts 14 days of Premium.
Keep reading.
All articlesDiscord Ticket Logs: Four Events, Four Channels, One Blind Spot
Ticket log channels are free on every plan and set per event, so opens, claims, closes and transfers can each land somewhere different. What each one carries.
9 min read
How to Open a Ticket in Discord (and What Decides If It Opens)
Members open a ticket by pressing a button on a panel. Behind that press sit five steps in a fixed order, and five routes in that do not all pass them.
9 min read
Discord Ticket Panel Design: What You Can Change, and What Discord Decides
The ticket panel is designable on every plan. What you can change, the two layouts, how members pick a category, and the rules Discord imposes on all of it.
9 min read