Privacy policy
Ticket System is a Discord bot for support tickets with a dashboard on this website. Here you can read what information we store, why we store it, and how to have it deleted.
Who is responsible
Jens Sejer, Gyldenhusvej, 5260 Odense. You can always contact us at ticketsystem.support@gmail.com.
When a Discord server uses Ticket System, we process information about the server’s members on behalf of the server. The server owner decides how tickets are used on their server. That is agreed in our data processing agreement.
What we store
| Information | Why | How long |
|---|---|---|
| Your Discord user ID, username and avatar, and whether your Discord account has two-step login, when you log in to the dashboard | To log you in and show who you are | Until you log out, and at most 7 days without activity |
| The names of your Discord servers and your permissions on them | To show the servers you are allowed to manage | Same as above |
| The server’s setup: categories, roles, channels, texts, quick replies and tags, and up to six copies of the setup, so you can go back to an earlier one | So the bot works on the server | As long as the bot is on the server, and 90 days after it is removed. The copies of the setup are deleted after 90 days |
| Suggestions with voting and bug reports (only on servers that have switched it on): the text, who sent it, who has voted for and against (for bug reports: who also has the bug), and the reply the server’s staff have given | So the server can collect ideas and bugs from its members and reply to them | The 200 newest suggestions and bug reports per server, as long as the bot is on the server, and 90 days after it is removed. Who has voted is deleted when the suggestion has received its reply or the bug has been closed. After that only the number of votes is kept |
| Bans and timed roles (only on servers that have switched it on): who it concerns, which role, when it expires, who gave it, the reason, and which of the user’s other roles the bot has taken meanwhile. If the server has connected its game server, the game server sends the player’s Discord ID, the reason, the end date and the name of the person who banned | So the server can ban a user for a period and give the roles back afterwards | Until the ban is lifted or expires. Then it is deleted at once, except for the line in the history of bans (see the next row). That it happened is also noted in the server’s change log |
| History of bans (only on servers that use a ban role): who was banned, when, until when, who gave the ban, the reason, and how it ended | So the server’s staff can see whether a user has been banned before | One year after the ban ended. Then the line is deleted by itself. The server can delete a line at any time on the dashboard |
| Warnings (only on servers that have switched it on): who received the warning, when, who gave it, the reason, and which ticket it was given in | So the server’s staff can give a warning before a ban and keep track of how many warnings a user has | As long as the warning lasts: the server chooses 30, 90, 180 or 365 days. Then it is deleted by itself. The server’s staff can remove a warning at any time |
| Who is verified (only on servers that have switched on "Remember who is verified"): the user’s Discord ID, the server and the time | So a member who leaves the server and comes back can get their role back without verifying again | For 12 months. It is deleted at once if the server switches it off, if the server’s staff take the role from the member themselves, and when the bot is removed from the server |
| Tickets: who opened, claimed and closed them, answers to questions, timestamps, ratings and comments on ratings, and the priority and tags (e.g. Bug or Complaint) the server’s staff have put on the ticket, and whether you have reopened the ticket yourself. If the ticket is an application: whether it was approved or rejected, by whom and with what reason | To run tickets and show statistics to the server’s staff | As long as the bot is on the server, and 90 days after it is removed |
| Transcripts: a copy of the messages in a ticket, with names, links to avatars and attachments, and a copy of the images sent in the ticket | As a record for the server’s staff and for the person who opened the ticket | As long as the bot is on the server, and 90 days after it is removed. If the server has switched on automatic deletion, a transcript and its images are deleted when the ticket has been closed for 30, 90, 180 or 365 days (the server chooses) |
| Alert on sensitive changes (only on servers that have switched it on): the name of the person who changed access, roles or security on the dashboard, and what was changed, is sent as a private message on Discord to the server owner | So the server owner notices if someone changes who has access | The message is stored by Discord. On our side the change is in the server’s change log, together with the other changes |
| Payments: who started a purchase of Premium, amounts, timestamps, invoice numbers, the e-mail and country used at payment, card type and the last four digits of the card, and the payment provider’s risk assessment. If you cancel and choose to tell us why, we also store your answer | To deliver Premium, show receipts, send a confirmation by e-mail when you buy, when the subscription is cancelled and when a payment is refunded, prevent fraud and be able to document the purchase in case of a disagreement | As long as the bot is on the server, and 90 days after it is removed. The accounting records themselves are kept by Stripe for 5 years, as required by Danish bookkeeping law |
| Reviews you choose to share yourself (only on servers that have switched it on): the number of stars, what you write, and your Discord name and avatar are shown in a channel on the server | So the server can show what users think of the help. Nothing is shared until you press "Share my review" yourself | The review stays in the server’s channel until the server deletes it there. We only store that it was shared, not the text itself |
| Automatic rules (only on servers that have switched it on): the bot reads what you write when you open a ticket, and your first messages in it, to see whether one of the words the server has chosen is in them. The text itself is not stored for that reason. Only which rules have worked in the ticket is stored | So the server can sort its tickets by itself, e.g. set a priority or alert management | Together with the ticket: as long as the bot is on the server, and 90 days after it is removed |
| Scheduled calls (only on servers that have switched it on): the time, which staff member scheduled the call, a short note about the subject, and whether you have said yes to the time | So the bot can remind you and staff about the call when it is time | Until the call is cancelled or the ticket is closed. Then the appointment is deleted. The messages about it are in the ticket and therefore in the transcript |
| A ticket on hold (only on servers that have switched it on): when staff will get back, who put the ticket on hold, and a short message to you | So the ticket does not close by itself meanwhile, and staff are reminded about it in time | Until the hold ends or the ticket is closed. Then it is deleted. The message about the hold is in the ticket and therefore in the transcript |
| Internal staff thread (only on servers that have switched it on): the server’s staff can discuss your ticket in a private thread that you cannot see. The messages in the thread are only kept by Discord. We do not store them, and they are not in the transcript. We only store which thread belongs to the ticket | So staff can help each other solve the case | The thread disappears when the ticket is deleted on Discord |
| Supporter of the month (only on servers that have switched it on): once a month the bot posts in a channel on the server which staff member helped in the most tickets, with the number of tickets and the average of the users’ stars | So the server can praise its team | The message stays in the server’s channel until the server deletes it there. We do not store anything new: the numbers are calculated from the tickets that are already stored |
| Staff notes: short notes that the server’s staff write about a user, with who wrote them and when | So the server’s staff can remember earlier cases with the same user | As long as the bot is on the server, and 90 days after it is removed. The server’s staff can delete a note at any time |
| Free trials: the server’s ID, the owner’s Discord ID and the date of the trial | So each server and each owner only get one free trial | The owner’s ID for 6 months. The server’s ID is kept, also after the server’s other data is deleted, so the trial cannot be started again |
| Support requests: what you write to us under Support on the dashboard, your Discord name and ID, your e-mail if you give it, and our replies. If you own a server with the bot, we may also write to you ourselves about the server’s use of Ticket System (e.g. if the setup has stalled). That message is stored in the same place, and you can switch them off with the button in the message | To help you and to be able to follow up | As long as the bot is on the server, and 90 days after it is removed |
| Invitation for support: when you invite Ticket System support to the server, we store the invitation and who made it (Discord name and ID). If we ask the server owner for an invitation ourselves, we store when we asked and what the answer was | So we can help on the server when you say yes to it yourselves | The invitation: until it expires, at most 7 days. The request: 7 days, and 30 days after a no, so we do not ask again |
| Change log: who changed what on the dashboard and when | Security and oversight for the server owner | The latest 300 changes per server |
| Backups of the above | So data is not lost if something fails | 14 days |
We only read messages in ticket channels. Messages in the server’s other channels are not stored.
Transcripts and links
A transcript can be opened through a link containing a long, random key. Anyone with the link can read the transcript, so only share it with those who should see it. Transcripts are not shown in search engines. Images from the ticket are stored with the transcript and deleted together with it. The server can choose that a transcript can only be opened after logging in with Discord: then only the person the ticket belongs to and the server’s staff can read it.
Cookies
We only use necessary cookies: ts.sid, which keeps you logged in to the dashboard, and ts.lang, which remembers whether you chose Danish or English. The dashboard also keeps a few choices in your own browser: which server you opened last, how the menu should look, whether you have seen the tour and the latest news, which pages you last jumped to with the search, and where you were heading if you have to log in first. That information stays in your browser. We use no cookies for statistics, advertising or tracking, and we do not load fonts or scripts from other companies. We count how many times the pages are shown, which website a visit came from, how many press "Add to Discord", and how many times each page in the demo is opened. The numbers are stored as daily totals. To count how many different people visit the site without counting the same one several times, we turn your IP address into a code using a secret key. The IP address itself is not stored, the code cannot be read back into the address, and it is deleted after 7 days. We cannot see who you are or which pages you in particular have viewed.
Why we are allowed to process the information
- To deliver what you asked for: when you log in to the dashboard, buy Premium or write to support, we process your information to be able to provide the service to you (Article 6(1)(b) of the General Data Protection Regulation).
- To run the service securely: the change log, the prevention of fraud and of abuse of the free trial, and the counting of visits are based on our legitimate interest in a secure and well-functioning service (Article 6(1)(f)).
- Because the law requires it: accounting information about purchases is kept under Danish bookkeeping law (Article 6(1)(c)).
- On behalf of the server: information about the members of a server (tickets, transcripts, notes, warnings and bans) is processed by us for the server. It is the server owner who decides over it and is responsible for there being a basis for the processing.
Who we share information with
We never sell information. We use these providers to run the service:
- Discord, which the bot and login run through. We also receive our own notifications about new support requests, purchases and new servers in a private channel on Discord.
- Hetzner Online GmbH (Finland), where the server with the bot and the database is hosted.
- Google (Gmail), which sends our e-mails: replies to you, if you have given an e-mail address in a support request, a confirmation to the e-mail address used at payment when you buy, when a subscription is cancelled and when a payment is refunded, and notifications to ourselves about new requests (with your Discord name and what you wrote to us).
- Stripe, which handles the payment for Premium. Card details go directly to Stripe and never reach our server.
Transfers outside the EU
Our server is located in the EU, and the backups are kept in the EU. Discord, Stripe and Google are American companies or owned by American companies. The information that passes through them (your login and the bot’s messages at Discord, the payment at Stripe and e-mails through Gmail) may therefore be processed in the USA. This is based on the European Commission’s decision on the EU-U.S. Data Privacy Framework or the European Commission’s standard contractual clauses.
Your rights
You have the right to access the information we hold about you, to have it corrected or deleted, and to object to the processing. Write to ticketsystem.support@gmail.com. The owner of a server can also ask us to delete all of the server’s data immediately.
If you are unhappy with how we process your information, you can complain to the Danish Data Protection Agency (Datatilsynet) at datatilsynet.dk.