Who we are and what this covers
JackpotMC LLC ("JackpotMC", "we", "us") operates the JackpotMC Discord bot and determines how information is used for its community, account-linking, support and administration features. This policy covers information the bot receives from Discord, information you submit through its features, and connected Minecraft and support records it uses.
The bot operates within Discord and uses connected support services. Discord's own processing is covered by the Discord Privacy Policy. Purchases, payment details and checkout are covered separately by the Tebex privacy policy. This bot policy does not replace those policies or describe every activity on the Minecraft network.
Information we process
What we process depends on the channels you use, the features you interact with and the information you choose to share.
- Discord account & interactions
- Discord user IDs, usernames and display names, avatar links, server membership and roles; server, channel and message IDs; commands, button selections, form responses and relevant timestamps. The bot receives member information and message content in channels available to it through Discord's permissions.
- Support tickets & transcripts
- Your Minecraft username, Java or Bedrock platform, selected game server and question; ticket identifiers, status, routing and closure details; messages, replies, attachments and evidence you provide. Transcripts may contain participant names, timestamps, message and embed text, downloaded images or videos, and links to other attachments. Purchase support may involve a Tebex transaction ID or receipt you submit.
- Minecraft account linking
- Discord IDs linked to Minecraft UUIDs, usernames and verification codes submitted in the linking channel or by direct message to the bot; linked-account status and role eligibility. The bot also reads existing game-network player records, including IP addresses, to identify related accounts and prevent duplicate linking or reward abuse. Discord does not provide your IP address to the bot.
- Applications & interviews
- Staff application answers, including Minecraft and Discord usernames, age, game activity, Minecraft and staffing experience, and written answers; media applications, including social-channel links, follower counts and average views; application status, reviewer actions and interview dates and times. Information you provide is included in the application review process.
- Community activity & moderation
- Chat experience points and levels associated with your Discord ID; recent message content, timing and conversation participants used to score chat and detect repetition; leaderboard entries; counting-game messages; suggestions and voting interactions; relevant role changes, ticket statistics, moderation actions and ticket blacklist records. Recent chat content is held in memory for scoring; the saved level file contains IDs, XP and levels.
- Service operation & correspondence
- Operational errors, request and delivery information, identifiers needed to troubleshoot failures, and communications you send to our privacy contact. If you email us, we receive your email address and the content of your message.
The bot does not request your Discord password, login token or full payment-card details. Avoid including passwords, financial details or unrelated sensitive information in tickets, applications, screenshots or logs.
How we use information
- Respond to commands, deliver notifications and operate community activities, chat levels and leaderboards.
- Verify Minecraft account links, assign relevant Discord roles and check eligibility for linked-account benefits.
- Answer support questions, route issues to staff, investigate reports and retain a record of ticket handling.
- Review staff and media applications, coordinate interviews and communicate decisions.
- Moderate the community, prevent abuse and duplicate claims, troubleshoot problems and maintain the service.
- Handle privacy requests and comply with applicable legal obligations.
We do not sell Discord API data or use it for advertising or data brokerage. Our use of ticket content with an AI service is explained below.
Where applicable data protection law requires a legal basis, we rely on providing the services you request, our legitimate interests in running and protecting the community, and compliance with legal obligations, as appropriate to the activity. Where consent is required for a particular use, that use must be subject to consent that you can withdraw.
AI-assisted support
Our support system uses Anthropic's Claude through a support service hosted on Supabase. When you open a support ticket, the bot sends the Minecraft username, platform, game server and question you enter, together with the Discord ticket-channel ID, to that service. Relevant conversation text and ticket context are supplied to Claude to generate replies and help identify when an issue needs staff attention.
While AI support is active, the bot forwards follow-up text sent by the ticket owner to the support service. Once a ticket is handed to staff, this automatic forwarding stops. Staff can return a ticket to AI support. Information already sent is not withdrawn by handing a ticket to staff.
Email tylshum@gmail.com for privacy requests without opening an AI-assisted ticket. You can also ask staff to handle an existing ticket; its initial question may already have been processed by the AI service.
AI-generated replies can be inaccurate. Staff can review issues that need human judgment. We use this integration to provide support; it is not a feature for training our own AI models. Provider-side storage, safety processing and retention are governed by the applicable service agreements and provider policies. Closing a ticket in our system does not itself send a deletion request to Anthropic.
Storage and retention
Information is stored across the bot's databases and local files, the Supabase support backend, and Discord messages and attachments. We maintain four daily database backups. A record removed from a live database may remain in a backup until that backup is rotated out; database deletion does not automatically remove a Discord message or transcript.
Support conversations
When a ticket closes, the bot requests deletion of its ticket and message records from the live support backend. Before closing the Discord channel, it creates a transcript, posts a copy to the staff transcript channel and attempts to send a copy to the ticket owner's direct messages. Temporary local transcript files are scheduled for cleanup after processing. A failed closure, deletion or cleanup request may need manual follow-up.
Discord transcripts & applications
Transcripts, application posts, staff logs and related Discord messages do not have a fixed automatic expiry in the bot. They remain until removed through Discord or by an administrator. Closing a ticket, deleting an original message or leaving the server does not automatically erase an existing transcript.
Account & community records
Account links, chat-level records, ticket statistics, blacklist entries and operational logs have no fixed automatic expiry in the bot. They remain until updated or removed through the relevant feature or administrator action. An unlink request does not by itself delete transcripts, application records, game-network records or backups. Recent chat-scoring data is kept in memory and cleared as activity is processed or the bot restarts.
Short-lived records
Interview scheduling records are automatically removed after the interview time plus 30 minutes when the cleanup task runs. This does not remove application or interview messages on Discord. Account-linking channel messages and bot replies are scheduled for deletion after a short interval, normally five seconds; the underlying link record is separate. Linking direct messages do not have the same automatic deletion schedule.
Records without automatic expiry require manual review and removal. We assess whether information remains necessary for the purpose described in this policy and handle deletion requests through the contact below. Where a legal obligation requires continued retention, we retain the necessary information for that obligation. Copies independently saved by other users and records controlled by Discord or another provider may require a separate request to that recipient.
Security
The bot uses Discord channel permissions for ticket access and role or permission checks for administrative actions. Ticket and AI API connections use HTTPS. Storage and access controls also depend on the hosting, database and support services involved.
No system can guarantee absolute security. If you suspect unauthorized access to bot information, contact tylshum@gmail.com with enough detail for us to investigate, without sending passwords, tokens or other secrets.
Your choices and privacy rights
You can choose whether to link a Minecraft account, submit an application or use a support ticket. Some information, such as member details or messages in channels the bot can access, is processed as part of community features even without a direct command. Leaving the server stops new server interactions but does not automatically erase previously stored records.
To request access, a copy, correction or deletion of information we hold, email tylshum@gmail.com. You can also contact staff through the JackpotMC Discord server. Email remains available if you cannot access Discord or do not want to open a ticket.
- Include your Discord user ID and, if relevant, Minecraft username or UUID and ticket or application reference.
- Tell us what you want to access, correct, delete or unlink. You do not need to include your password or login token.
- We may ask for proportionate proof that you control the account before disclosing or changing personal information.
Deletion may affect linked roles, rewards, support history or other features that depend on the record. We handle requests within the time required by applicable law and explain any necessary limitation, including legal retention or information controlled by another provider.
Depending on your location, you may also have rights to object to processing, restrict it, receive portable data, withdraw consent where applicable, or complain to your local data protection authority. Contact us to exercise those rights. For information held by Discord or Tebex under their own policies, use their privacy request processes.
Age requirements
The bot is intended for people who meet Discord's minimum age requirements, including any higher minimum age required in their country. It is not intended for children under 13. If you believe a child below the applicable minimum age has provided personal information, contact us so we can investigate and address the information we control.
Policy updates and contact
We may update this policy when bot features, providers or data-handling practices change. The date at the top identifies the latest revision. Material changes will be communicated through this page and, where appropriate, the JackpotMC Discord community.
