01 Scope & Hosting
This policy describes information Combat Master, a self-hosted Discord staff bot maintained by mob5824, is designed to process when its features are used. It applies to an instance operated by or for the Maintainer. It does not replace Discord’s privacy policy or the policies of a host, network, or other service.
For an independently self-hosted or community-hosted copy, the instance operator controls the machine, files, dashboard access, staff log channel, backups, and retention. In normal operation the bot writes its records to that instance’s local data directory and communicates with Discord; the Maintainer cannot access or delete records on a server they do not operate. Ask that instance’s operator how it handles information.
02 Information Processed
The information stored depends on which features an administrator enables. A local instance may process or store:
| Category | Examples | Why it is used |
|---|
| Discord identifiers and settings | Server, channel, message, role, and user IDs; display names; configured staff roles, channels, time zone, and feature settings. | Address Discord resources, authorize staff operations, deliver messages, and keep server-specific configuration. |
| Announcements and approvals | Announcement titles and bodies, author IDs and names, scheduled or repeating posts, templates, mention-role IDs, approval requests and decisions, quiet-hour settings, and pin status. | Prepare, schedule, publish, manage, and audit staff communications. |
| Polls and events | Poll questions, options, settings, and results. Button-poll votes can include a voter’s Discord ID, displayed name, selected option, and vote time. Older reaction polls store final counts. Event titles, descriptions, times, creator IDs, and message references are also stored. RSVP counts are read from Discord; the bot may temporarily read up to 50 RSVP member IDs to mention people in a reminder, but does not save the RSVP member list in its own database. | Run polls and events, show results, schedule reminders, and report participation features. |
| Tickets and transcripts | Ticket opener ID and name, ticket/channel status and times, and—when a ticket is closed successfully—a transcript of up to the first 1,000 messages (oldest first), with timestamps, authors, message text, and attachment URLs. | Operate private support tickets, track idle activity, close ticket channels, and let authorized staff review or download saved transcripts. |
| Audit records and configuration | Staff actor ID and name, source (Discord, dashboard, or system), action, details, and time; bot and dashboard tokens; configured roles, channels, and welcome text. | Record staff and scheduled operations, configure the bot, and authenticate dashboard sessions. Tokens are secrets. |
| Runtime and dashboard security | Startup and diagnostic messages in the local log. For dashboard login throttling, the client network address is processed in memory after failed attempts; the dashboard’s HTTP access log is disabled by default. | Run and troubleshoot the instance and limit repeated failed dashboard logins. |
Combat Master enables Discord’s Message Content intent so it can create ticket transcripts. Its general message handler only updates the last-activity time for a matching open ticket; it does not save ordinary server-chat message text. Ticket history is read when a ticket is closed. Attachment URLs may appear in transcripts, but the bot does not copy the attachment files into the transcript.
03 How Information Is Used
The instance uses this information to receive Discord commands and interactions; check configured staff access; create and publish announcements; maintain schedules, polls, events, and roles; operate and close tickets; record actions; and display or export information to authorized dashboard users.
Ticket transcripts are saved in the local SQLite database and posted as a text file to the configured staff log channel. The database copy remains available to the dashboard after the Discord ticket channel is deleted. Button-poll votes are stored with voter identifiers so the bot can tally and display who chose each option.
04 Storage & Retention
By default, Combat Master stores its files in a data/ directory beside the application. The operator can relocate them by setting COMBAT_MASTER_DATA. The main files are bot.db (SQLite records and transcripts), config.json (live settings and tokens), and bot.log (a plain log appended on each run). The configuration file is intended to be private; on supported systems the application sets restrictive file permissions. The operator’s host, containers, backups, or service provider may create additional copies.
Combat Master documents no general automatic retention period for its database, audit history, poll voter records, or ticket transcripts. A successfully saved transcript is not automatically deleted when the ticket channel is removed or when an idle ticket closes. Records remain under the instance operator’s control until that operator removes or resets them, subject to individual feature actions and any backups or copies held elsewhere.
Deleting a message or changing a feature in Discord does not necessarily remove its local database record, a transcript already posted to a staff log channel, or a backup. Removing the bot from a server does not by itself erase its files or messages it previously sent.
05 Sharing & Third Parties
- Discord: The bot connects to Discord to receive interactions and carry out server features. Announcements, welcome messages, ticket panels, event posts, and staff transcript files may be sent to configured Discord channels. Discord handles that information under its own policies.
- Server staff and operator: People who can access the host, database, dashboard token, or configured staff log channel may be able to read stored records and ticket transcripts. Dashboard access should be restricted to trusted staff.
- Hosting and network providers: A provider selected by the instance operator may process or back up data as part of running the bot. The Maintainer does not control that provider.
- This website: The project pages are hosted by GitHub Pages and request fonts from Google Fonts. Those providers may process connection data under their own policies.
The Maintainer does not receive local records from an independently hosted copy through ordinary bot operation. The Maintainer does not sell those records.
06 Access, Correction & Deletion
- Self-hosted or community-hosted Combat Master: Contact the instance operator. That operator controls the database, transcript files, staff log channel, and backups and is the person able to review, correct, export, or remove its records.
- An instance operated by the Maintainer: Email with “Combat Master privacy request” and enough information to locate the relevant data. Do not send passwords, bot tokens, or dashboard credentials.
- Discord-held information: Use Discord’s privacy and account tools for information Discord controls. Removing a bot or leaving a server does not automatically erase records held by the instance operator.
Requests can be handled only for information the recipient controls and are subject to applicable law, identity checks, and copies retained in backups or Discord.
07 Security
The dashboard listens on loopback by default, uses a separate token, and disables HTTP access logging. These measures reduce some risks but do not guarantee security. The instance operator is responsible for protecting credentials and files, restricting local and staff access, securing the host and backups, and using HTTPS, a firewall, and suitable proxy settings if the dashboard is deliberately made reachable over a network.
Do not expose ticket transcripts, tokens, or database files in public channels or repositories. Anyone with sufficient access to the host, staff log channel, or dashboard may be able to see information available there.
08 Children’s Privacy
Combat Master is not intended for anyone below Discord’s minimum age requirement or a higher minimum age that applies in their location. Server operators must consider the ages of their members and must not collect information from children in violation of applicable law. If you believe information was collected improperly, contact the instance operator or, for an instance operated by the Maintainer, use the contact details below.
09 This Website
The project and policy pages are static pages hosted by GitHub Pages. They do not contain a submission form or first-party analytics. The theme preference may be saved in your browser’s local storage; the site code does not send that preference to Combat Master. Google Fonts is requested from Google to render the selected typefaces. GitHub and Google may process connection data under their own policies.
10 Changes to This Policy
This policy may be updated when Combat Master’s features, deployments, or legal requirements change. A revised “Last updated” date will appear at the top of this page. An independently hosted operator may have different practices and should provide their own notice where required.
11 Contact
For questions about this policy or privacy requests concerning an instance operated by the Maintainer, contact . Include “Combat Master privacy” in the subject and do not include credentials.
Project: ·