Data & retention
Clarify keeps just enough to run your tickets well — the conversations, the details members submit, and the transcripts you choose to save. This page lists exactly what's stored, what actually leaves Discord, and how long it stays.
What Clarify stores
For every ticket, Clarify keeps the record your team needs to answer well and to build a transcript later.
What leaves Discord
Clarify is the middleman between a member and your team, so some information has to travel from Discord to Clarify to make the relay work. Here's the full list — and what deliberately stays behind.
| Sent to Clarify | Why |
|---|---|
| Mirrored message content + author identity (id, username, avatar, display name) | To relay messages both ways and build transcripts |
| Your Discord profile (id, username, email) at login | To sign you in to the dashboard |
| Payment event notifications (transaction id, amount, timestamp) | So your team sees an order or membership on the ticket |
Payment events are notifications only — an id, an amount, a time. Clarify never receives full financial records, card numbers or bank details from Stripe, PayPal, Tebex or Patreon.
How long it's kept
Tickets — and with them their transcripts — stay until you remove them. There is no automatic deletion of ticket history at the moment; deleting your server from the dashboard removes its tickets.
Delete or reset
When you want to clear things out, everything lives in the Danger Zone in your general settings.
Reset your configuration
Clears your Clarify setup for the server so you can start fresh.
Delete the server from Clarify
Removes the server and its data from Clarify.
Frequently asked
Only for messages that are part of a ticket. Ordinary channel chatter and DMs unrelated to a ticket never reach Clarify.
No. Full server rosters are never sent to Clarify — it only ever sees the people involved in a ticket.
As long as the ticket exists in Clarify. There is no automatic deletion; deleting the server removes its tickets.
No. Integration keys and tokens are kept in a separate, encrypted store — never inside ticket data. See Encryption.