Discord Tickets data processing annex
The Art. 28(3) specifics for hosted Discord Tickets, and the 24-month retention period that is part of your instructions to us.
What this annex is
The Art. 28(3) specifics for Discord Tickets where we host it. It is part of the data processing agreement, which carries the obligations.
Discord Tickets is not a GHub product and does not run on GPlatform. That changes its licence, not our obligations to you.
Nature and purpose of the processing
Operating a support ticket system for your Discord server: receiving tickets, carrying the conversation, archiving it on close, collecting feedback, and running whatever automations you configure.
Categories of data subjects
- Members of your Discord server who open a ticket — and anybody who writes in one, whether or not they opened it.
- Your staff, who appear as claimants, responders and closers.
- Members on your blocklist.
Categories of personal data
Ticket records: opener, topic, category, claimant, closer and close reason, timestamps, message count, priority, tags, and the answers given to your opening questions.
Conversation content, where archiving is on (it is by default): the content of every message, its author, and whether it was edited or deleted; the username, display name, avatar reference and hoisted role of everyone in the ticket; and a rendered HTML transcript of the whole ticket.
Feedback: rating, comment, and the answers to your feedback form.
Configuration: your blocklist of users and roles.
Special categories
Not sought and not intended. A support ticket is free text written by somebody asking for help, and people disclose health, financial and other sensitive matters in support conversations without being asked to. Archiving is on by default, so that material is retained by default. Consider whether your server should have archiving on at all.
Processing operations
Collection from Discord, encryption, storage, retrieval and display to your staff, transcript rendering, automation, export, and deletion when you ask for it.
Sub-processors
Those named in the general agreement — IONOS SE and Contabo GmbH, both in Germany, plus our own hardware in Germany — and Sentry (Functional Software, Inc.), EU data region: error reports, performance traces and the bot's operational log lines, with credentials filtered out and no IP addresses; errors and log lines can contain Discord user, channel and server IDs and details of the ticket an operation was handling. Transfers to the United States rest on the EU-US Data Privacy Framework, with standard contractual clauses as a fallback. No others: no analytics and no AI provider.
Discord is the source of the data rather than a sub-processor: the conversation happens in Discord under Discord's own terms with your members.
Security measures particular to this service
- Message content, usernames, display names, feedback and question answers are encrypted before storage. Disabling encryption in a production environment requires deliberately setting a second variable named
I_KNOW_DISABLE_ENCRYPTION_IS_DANGEROUSand the process prints a warning banner at every start. On instances we host it is enabled. - Archiving can be switched off per server, in which case conversations are not written down at all — the strongest available minimisation and the one worth considering first.
- A guild-level data export exists, and pruning tooling exists.
Retention — read this one
A ticket's archived conversation is deleted 24 months after the ticket closed: its messages, the people and roles in it, the answers given when it was opened, its feedback and its transcript. The ticket's own record stays.
That period is part of your instructions to us under this agreement. If your server needs a shorter one, switch archiving off or delete sooner; we help with either. If it needs the conversations for longer, export them before the 24 months are up.
On termination
As set out in the general agreement: return or deletion at your choice, 30 days of export availability by default, backups expiring on their own cycle.