Privacy Policy
Last updated: 4 November 2026
Scope and operator
This policy covers the independently operated Wrath Discord bot and its dashboard. The bot owner operates the service and is the contact for privacy questions and deletion requests. Discord’s own processing is covered by its separate privacy policy.
Discord account and server data
Depending on enabled features, Wrath processes user, server, channel, role and message identifiers; usernames, display names and avatars; membership, role and permission information; and presence or custom status information Discord makes available. Server settings, command preferences, moderation cases and warnings, tickets, counters scheduled announcement text and delivery status, temporary role expiries and other feature records may be stored to provide the selected features. Activity statistics record daily joins, leaves and message counts without message content; per-day user IDs are kept to count unique active members for a rolling 30-day window. Ticket records may include priority, inactivity and first-staff-response timestamps. Command favourites are stored in your browser, scoped to your dashboard account and server.
Messages and uploads
Wrath can process command text, messages and attachments required for moderation, logging, tickets, saved content and bot chat features. Configured logs or transcripts may preserve content. The bot owner can read and reply to messages sent to the bot through the owner-only DM inbox, including attachments. Do not send the bot information you do not want its operator to see. Server administrators may access records generated by the features they manage.
Dashboard sign-in and browser storage
Discord sign-in requests identify and guilds to identify your account and determine server access. The dashboard uses an essential session cookie and temporary OAuth security cookies. Dashboard sign-in is remembered on each browser for up to 30 days. Random session identifiers are stored in an essential HttpOnly cookie; encrypted session records, including Discord access and refresh tokens, are stored on the bot host to survive restarts and renew access. Logout removes that browser’s stored session; expired records are pruned at startup or on dashboard activity. Revoked Discord authorisations require signing in again. Appearance preferences may be saved in your browser’s local storage. Your browser and the hosting infrastructure also transmit technical request information such as IP addresses, timestamps and browser information; operational logs may record request details.
Optional recovery and server backups
Member recovery separately requests identify and guilds.join. Consenting account identifiers and encrypted OAuth access and refresh tokens are stored so the bot can add those accounts to an eligible replacement server through recovery. This does not reveal Discord passwords. Source server owners can view authorised account identities. Server backups can retain server structure, roles, permissions, channel configuration and supported member records; they are not a complete copy of all Discord content. Removing the bot or leaving a server does not automatically erase saved backups or recovery consent.
How information is used and shared
Information is used to execute commands, apply settings, provide moderation and community features, authenticate dashboard access, enable requested recovery, diagnose faults and prevent abuse. Requests and relevant data are sent to Discord and, when selected features require them, external APIs or media providers. Hosting infrastructure processes data to operate the service. Server staff can see feature records for their server, and the operator can access stored service data for administration and support. Wrath does not sell personal data or use Discord API data to train AI models.
Retention
Feature records and configuration are generally persistent and do not all have automatic expiry. They are kept while needed for the feature, recovery or legitimate security and operational purposes, and should be deleted when no longer necessary. Recovery credentials remain stored until revoked or removed; token expiry alone is not deletion because refresh tokens can renew access. Saved backups and exported files may survive removal of the bot. Copies downloaded by server administrators are controlled by those recipients. This policy does not promise an automatic deletion schedule that the software does not implement.
Your choices and deletion requests
You can revoke Wrath in Discord’s User Settings → Authorised Apps. The ,mb revoke command also removes your stored recovery authorisations from the running service. Signed-in users can submit access and deletion requests through the dashboard Operations centre (Your privacy). These are reviewed manually by the bot operator. For correction or other privacy requests, contact the bot owner on Discord and provide your Discord user ID, relevant server ID and the type of data involved. Do not send passwords or OAuth tokens. Identity or authority may need to be verified. Requests will be handled as required by applicable law; limited records may need to be retained for legal obligations or legitimate security reasons. Ask server administrators separately about copies they exported or logs they control.
Security, location and changes
Dashboard access is permission restricted, public connections use HTTPS when deployed as configured, and stored recovery tokens are encrypted. No system can guarantee complete security. Discord, hosting and integration providers may process information in other countries. This policy will be updated when processing changes. Contact the bot owner on Discord with concerns about how Wrath handles your information.