Euphory TicketPrivacy Policy
Last updated: November 4, 2026
Euphory Ticket only stores what it needs to run your server's tickets, and never sells or shares that data for advertising.
1. Who we are and what this covers
This policy explains what data the Discord bot Euphory Ticket stores, why, and for how long. It applies to everyone who uses the bot: server owners and staff, and players or users who open tickets.
- Data controller: Gabriel Jesus Montalvo Vera (GJ Euphory), developer of Euphory Ticket.
- Contact: GJ Euphory (@gjeuphory21) on Discord, or the support server.
- Communities: each server (or pair of linked servers) that activates the bot forms a community. Its Owners decide how the bot is used there: which channels receive logs, whether AI is used and who can see each ticket.
2. What data the bot stores
The bot stores Discord IDs, display names and what people write in ticket forms. It does not store passwords, email addresses or payment details.
| Data | What it includes | About whom |
|---|---|---|
| Community settings | Server, channel and role IDs; ranks, categories, forms, styles, texts in each language (including those changed with the text file), custom languages, colors and /setup options | Owners and staff |
| Owners and managers | Discord IDs of the person who created the community and its managers | Owners |
| Open tickets | Number, category, ID, name and avatar of the person who opened it; ticket language; form answers; who claimed it and who wrote in it | Players and staff |
| Closed ticket history | Same as an open ticket, plus participants, message count, events (claims, closing), rating and comment, and the AI summary | Players and staff |
| Unfinished forms | What someone has answered so far in a form they have not sent yet, so it is not lost if the bot restarts | Players |
| Remembered details for each person | Minecraft platform, device, version and nickname, their explanation of how they connect if they chose “Other”, the date of their last ticket and, for staff, the language they use /setup in | Players and staff |
| Waiting queue | ID and name of the person waiting, category and time | Players |
| Blacklist | IDs blocked by the community, who added them and when | Players and staff |
/setup change history | The last 200 changes: who, when and what changed | Owners and staff |
| Community AI keys | The keys Owners paste in /setup | Owners |
All of this is stored in files on the server (hosting) where the bot runs, kept separate for each community. The files are not encrypted: they are protected by the fact that only the developer and the hosting provider can access that server (see section 7).
3. What it does not store, and where conversations go
Full ticket conversations are not stored by the bot: when a ticket closes they are sent to Discord and the bot removes them from its memory.
- Transcripts: when a ticket closes, the bot reads the channel's messages, builds a transcript (an HTML file with messages and images) and posts it in the log channel chosen by the community. It also sends a copy by direct message to the staff member who closed it and, if the community enabled it, to the player. Then it deletes the ticket channel.
- Files and images: they are downloaded only for a moment to re-upload them to the log. They are not kept on the hosting.
- Messages outside tickets: the bot does not read or store messages from other channels.
- Sensitive data: the bot does not ask for or store passwords, email addresses, phone numbers, addresses or payment details.
Logs posted on Discord belong to the server where they were posted. Its Owners can delete them at any time.
4. How the data is used
The data is used only to provide the ticket service inside each community:
- Create the private channel for each ticket and give access to the right people.
- Show the form and its answers to the staff.
- Remember the player's platform and nickname so they don't have to type them on every ticket.
- Enforce the community's rules: queue, ticket limits, cooldown between tickets, working hours and blacklist.
- Generate the log, transcript, rating and staff statistics.
- Send direct messages: queue turn, rating request, copy of the log and inactivity notices to Owners.
Special Discord permissions
- Message Content: only inside ticket channels. Used to build the transcript and the AI summary when the ticket closes. Messages in other channels are ignored and never stored.
- Server Members: to know who has each staff role, release the tickets of a staff member who leaves the server, and notify Owners when the community is inactive.
5. Artificial intelligence, other services and where data is kept
Each community decides whether to use AI. If it is enabled, when a ticket closes the bot sends the conversation text (display names and messages, no files) to one of these providers to write a summary and review the staff's handling: Groq, Cerebras, OpenRouter, Google Gemini or Mistral.
The bot tries them one after another until one answers. Each provider handles the data under its own privacy policy. Important: the free plans of Google Gemini and Mistral may use the text they receive to improve their models. Each community's Owners can turn AI off completely or choose only the providers they prefer in /setup.
In addition:
- Discord stores the ticket messages, channels and files, like any other Discord message.
- The hosting service where the bot runs stores the data files described above.
Transfer outside Peru
The developer is based in Peru, but the bot's hosting is in another country (currently the United States), and Discord and the AI providers also process data outside Peru. This means the data described in this policy leaves the country you live in. By using the bot, you agree to this transfer. If you do not agree, do not open tickets with Euphory Ticket and ask your community's staff for another way to contact them.
No data is sold or rented to anyone, and it is not used for advertising.
6. How long data is kept
| Data | How long |
|---|---|
| Unfinished forms | 30 minutes at most; if they are not sent, they are deleted |
| Open tickets | Until they are closed |
| Closed ticket history | 90 days in active use; then moved to monthly archives that are deleted after 5 years at most |
| Remembered details for each person (platform, nickname, version, language) | As long as the community exists |
/setup change history | The last 200 changes |
| Blacklist | Until the staff removes the person |
When everything is deleted
- If the Owners delete the community from
/setup, its data is deleted immediately. - If the bot leaves a community's servers, its data is deleted 30 days later. This margin exists in case the bot was removed by mistake.
- If a server never activates the bot, the bot leaves on its own after 7 days.
Messages the bot posted on Discord (logs, transcripts) are not deleted by this: they stay in those channels until someone on the server deletes them.
7. Who can see the data
- Each community's staff sees the tickets and history of their own community, according to the permissions the Owners gave each rank.
- The community's Owners see the settings and change history, and can download copies of the settings (without the AI keys).
- The developer manages the hosting, so they are technically able to see the data files in section 2. The bot can also read the channels it has permission for, including log channels. The developer commits to accessing this data only when needed to provide support, fix a bug, investigate abuse or comply with the law; never to read a community's conversations out of curiosity or to share them.
- The hosting provider may access the server's files under its own policy, as with any cloud service.
A community never sees another community's data.
Security
Data is stored on the server where the bot runs, with no public access. Access to the hosting and the bot's key (token) is protected with a password and two-step verification, and is never shared. AI keys are never shown in full on Discord and are never included in backups. No system is 100% secure: if a problem affects your data, it will be announced on the support server.
Minors
Discord requires users to be at least 13 years old (or the minimum age in your country). Euphory Ticket follows the same rule and does not knowingly collect data from anyone under that age. If you believe data from a minor was stored, contact us and we will delete it.
8. Your rights and contact
You can ask to:
- See what data the bot stores about you.
- Correct wrong data (for example, your nickname).
- Delete your personal data from the history and player details.
To ask, write on the support server or contact the developer. If it concerns a specific community, you can also ask its Owners. We will reply within 30 days at most.
Some data may be kept if the community needs it for safety, for example a blacklist entry. Messages already posted on Discord depend on each server and on Discord.
Changes to this policy
If this policy changes, the date above will be updated and the change will be announced on the support server. Continuing to use the bot after the announcement means you accept the new version.
Languages
This document is also available in Spanish. If the versions differ in any way, the Spanish version prevails.
Contact
- Developer: Gabriel Jesus Montalvo Vera (GJ Euphory)
- Discord: GJ Euphory (@gjeuphory21)
- Support server: https://discord.gg/Eh2tzxXeHK