MUAYBOT / COMMUNITY TOOLS
Privacy Policy
Who this policy covers
This policy explains how TwinPR, operator of MuayBot, processes information through the bot and its optional dashboard. Contact for privacy questions, corrections, access, or deletion: razortied@gmail.com. Effective date: 10/2/2026. Community owners separately control their Discord channels and connected game servers. Their handling of information outside MuayBot is governed by their own practices.
Information processed
Depending on enabled features, MuayBot processes Discord user, server, channel, and role identifiers; usernames and permission information; command inputs, button selections, and submitted form fields; self-reported in-game usernames and account links; virtual wallet and bank balances, transaction records, purchases, delivery status, cooldowns, game state, clan records, bounties, and supported gameplay statistics; community settings, shop products, schedules, and audit records; ticket owner, channel, and status records; and membership customer IDs, plans, activation dates, expiry dates, and status. Connected game-server data includes server names, public addresses, RCON ports, provider labels, RCON credentials, command responses, and supported game events. Only configured features determine which of these records are created.
Messages, tickets, and sign-in
The current bot is designed around commands and interactions and does not collect a general archive of Discord conversations. Ticket conversations remain in their Discord channels; the bot database stores ticket metadata rather than a transcript archive. Information you voluntarily send directly to support is also processed to resolve your request. If the dashboard is enabled, Discord sign-in provides your identity and list of Discord communities for access checks. The dashboard uses an authentication-state cookie lasting up to five minutes and a session cookie lasting up to eight hours. Current dashboard sessions are held in server memory and end on logout, expiry, or restart. Hosting providers may process connection metadata such as IP addresses and request logs under their own policies.
Why information is used
We use information to deliver requested features, identify the correct community and player, authorize staff and developer actions, maintain virtual economies and memberships, send authorized game commands, provide support, prevent abuse, investigate errors, and meet applicable obligations. Account linking is self-reported and is not independent identity verification. The bot does not need your Discord password or payment-card details. Do not include unnecessary sensitive information in commands or support requests.
Who can access information
Authorized community staff can access information needed to administer their own community. Players may see information intentionally displayed by enabled features, such as leaderboards, clans, game results, and announcements. The MuayBot operator has technical access across communities for operation, support, security, and administration. Discord processes interactions and messages. Connected game servers and their hosts receive the commands and player information needed to perform requested actions. Infrastructure providers process data as needed to host or support the service. We may disclose information when legally required. We do not sell personal information, use it for targeted advertising, or use Discord API data to train AI models. Publicly posted results can be seen or copied by people with access to those channels.
Storage, security, and retention
MuayBot stores persistent operational records in a server-side SQLite database. Stored RCON passwords are encrypted by the application; other database records are not encrypted by SQLite itself. Access restrictions and deployment-level safeguards protect the remaining records. No system can guarantee absolute security. Records are retained only while needed for the stated features or applicable legal obligations. Removing the bot or allowing membership to expire does not itself automatically erase its database records. The operator handles cleanup and deletion requests manually, including relevant backups; there is currently no general automatic retention schedule. Temporary dashboard authentication data expires as described above. We will promptly delete Discord API data when it is no longer needed, when you or Discord request deletion, or when operation ends, except where law requires retention. Where legal retention is necessary, we restrict use to that purpose.
Your choices and requests
Email razortied@gmail.com to request access, correction, or deletion of your information. Include your Discord user ID and, when relevant, the community ID so we can find the right records. Never send passwords, tokens, or RCON credentials. We may ask for proportionate proof that the account or community is yours. We respond promptly and within applicable legal time limits. Deletion can remove linked usernames, virtual progress, and other features that depend on the deleted records. You may stop using the bot or revoke Discord authorization. Records held independently by Discord, community administrators, or game hosts must also be addressed with those parties. Depending on your location, you may have additional rights to portability, restriction, objection, withdrawal of consent where relied on, or a complaint to your local data-protection authority.
Children, international processing, and updates
MuayBot is not intended for anyone below Discord’s minimum age or a higher minimum required locally. Contact us if you believe information from an ineligible child has been collected. Discord, hosting providers, and connected servers may process information in countries other than yours. Where applicable law requires safeguards for international transfers, the operator must arrange them. We will update this policy when our practices change and give notice of material changes through the service or support channel where reasonably practicable. The current policy will remain publicly accessible.