1. What this policy covers
This policy explains how the PunishyBot website and Discord bot handle information in the current version of the service. Discord server staff make their own moderation decisions and may keep separate records outside PunishyBot. Discord and other providers have their own privacy policies.
2. Information we process
- Discord identity and server information: user IDs, usernames, display names, avatar references, server IDs, names and icons, member information, and permissions used to verify staff access or locate a member.
- Moderation records: the affected member and staff identifiers, punishment type, reason, extra details, duration, timestamps, IDCode, action status and DM delivery status.
- Appeals: the statement you submit, staff decisions, responses, follow-up messages and related timestamps.
- Server configuration and activity: alert templates, feature settings, supported Discord audit events, optional member join/leave events, bot command names and dashboard actions.
- Connection and login information: temporary OAuth access tokens, session identifiers, login state and connection addresses used for request limits. Hosting infrastructure may also process request and error logs.
The application does not request your Discord password or email address. It does not request message-content access or collect ordinary server chat history. Moderation reasons and appeals can still contain information entered by users or staff. The current appeal form does not accept file attachments.
3. Why we use it
We use this information to sign you in, check permissions, show the appropriate profile and case records, deliver punishment DMs, perform authorized moderation, process appeals, apply server settings, and diagnose errors or prevent abuse. The current application has no advertising, analytics-tracking or data-sale integrations.
4. Who can see information
Authorized server staff can access moderation records and appeals for their server. Signed-in users can access their own stored cases. An exact-username lookup can reveal a Discord profile without login, but does not reveal case counts or details. The visitor must provide an IDCode matching that profile to unlock a case. Keep codes private, because knowing the username and matching code allows access without proving ownership of the Discord account.
If staff configure a Discord log channel, people with access to that channel can see punishment details and final appeal decisions, including the staff response. The server controls access and retention for those Discord messages. Submitted appeals and follow-up messages are shared with the relevant server’s staff. Staff responses are visible through the corresponding appeal page. PunishyBot operators and hosting providers may need access to operate, secure or troubleshoot the service. Information may also need to be disclosed where required by applicable law.
Discord processes API requests, moderation actions, bot DMs and avatar requests under its Privacy policy. Some pages load fonts from Google Fonts, which sends the visitor’s connection information to Google; see Google Fonts privacy information. Hosting and these providers may process data in locations outside your country.
5. Cookies and browser storage
We use essential cookies for sign-in sessions, OAuth request verification and temporary username-lookup sessions. Sign-in sessions last up to one hour, login-verification state lasts up to ten minutes, and username-lookup sessions last up to thirty minutes. These server-side sessions are held in memory and are cleared when the app restarts.
Browser session storage temporarily holds an IDCode while you complete Discord login. The page removes that saved value after successfully loading the case. The development color controls have been removed; previously saved color preferences may remain on your device until you clear site data. Clearing site data removes browser preferences and session storage; it does not delete server-side moderation records.
6. How long information is kept
Audit entries are retained for 30 days. The app removes older entries when data is accessed, at startup and during scheduled cleanup while it is running. Cleanup resumes after downtime.
Punishment records, appeals and server settings do not currently have an automatic deletion schedule. They remain in the private application database until removed by the operator. Logging out, revoking Discord authorization or removing the bot does not automatically delete them. Hosting logs and backups are separate from the app’s audit store and may have different retention periods.
Private records and credentials are stored outside the publicly served website folder. Access checks protect case and staff endpoints. These measures reduce risk but cannot guarantee that every system or transmission is completely secure.
7. Your choices and requests
You can log out, revoke PunishyBot’s authorization in Discord, stop submitting information, or ask your server’s staff about a moderation decision. Depending on applicable law, you may have rights to access, correct, delete or restrict use of your personal information, or to raise a concern with a relevant privacy authority.
For access, correction, deletion or other privacy requests, join our Discord support server and ask the PunishyBot team for a private way to send your request. Include your Discord user ID and enough context to locate the records. Do not post passwords, tokens, private IDCodes or case details in public channels. We may need to verify your identity before disclosing or changing records. There is no automatic deletion button at present.
We will review requests in accordance with applicable requirements. Some information may need to be retained for legitimate security, dispute-resolution or legal reasons. Records held independently by server staff, Discord or another provider must be addressed with that party.
8. Age requirements and updates
PunishyBot is intended for people who meet Discord’s minimum age requirements and any higher minimum age required where they live. If you believe information about an ineligible child has been submitted, contact the PunishyBot team through our support server.
We will update this page when relevant features or data practices change. Check the revision date above. You can also read our Terms of service.