voidOperator and contact
This policy covers the independently operated Void Bot Discord application and its dashboard. Contact the operator through the Void Bot support server for support, privacy questions, or data access and deletion requests. Request a private conversation for sensitive matters.
Discord sign-in
The dashboard requests your Discord account identity and the list of servers you belong to. This information is used to identify you and show servers you can manage or access as delegated staff. The dashboard does not request your email address or Discord password.
Your Discord access token stays on the server, in memory. Dashboard sessions last up to one hour and end when the bot restarts. The browser receives a secure session cookie. Signing out removes that dashboard session; you can also revoke the application’s authorization in Discord.
Information processed by the bot
The bot processes Discord server, channel, role, user and message identifiers and message text needed for its configured features. Stored information can include server configuration and settings change history (actor identifiers, timestamps and before/after settings); ticket ownership and staff-access records; issue forms and conversation transcripts; moderation cases and triggering-message evidence; support and AI feedback; reusable support resolutions; and ban appeals submitted through a configured appeal flow. Transcripts can contain attachment links.
Configured moderation rules inspect messages in channels the bot can access. The ticket helper processes bot ticket conversations. Word and spam filters do not analyze image, voice or attachment contents.
Community tools
When enabled or used by a server manager, community tools store suggestion text, authors and votes; event details and RSVP user IDs; polls and ballots; welcome text and links; self-service role choices; temporary voice room ownership; and scheduled announcement text and delivery status. Public poll ballots show voter IDs and selections. Anonymous polls use random poll-specific salted hashes rather than raw voter IDs in ballot storage; the hosting operator still has access to host files and Discord interactions during operation.
Activity collection is optional. It counts messages in text channels visible to everyone and non-bot member joins/leaves when member events are available. It stores daily totals, UTC hourly counts and channel totals for 30 recorded days, without message text or individual message-author IDs. Counts are saved periodically and can miss recent activity if the process stops abruptly. Counts start when enabled; earlier activity is not reconstructed. Community items retain up to 300 recent/active records, with limits on active items and ballots. Removing a Discord post does not automatically erase its local record or retained backups.
Purpose, access and providers
Information is used to provide each server’s configured support, moderation, automation, accountability, backup and recovery features. Server data is separated into server-specific storage. Dashboard access is checked against current Discord permissions; sensitive case evidence and reusable solutions are also limited by their staff-role scope, with Administrator access where supported.
Assigned staff, server administrators and other people granted access in Discord can see the conversations or logs they can access. Administrators can export and restore their server’s data. The hosting operator can access host files when operating, supporting or recovering the service; server separation is not encryption against the operator.
Discord processes API activity, messages, attachments, DMs and login authorization. The service’s VPS and its hosting infrastructure store and process the bot’s local data. The current helper extracts and matches confirmed support fixes locally; it does not send ticket conversations to an external generative AI provider.
Retention and backups
Settings change history starts when the feature is enabled and retains up to 200 changes or approximately 5 MB per server. Full data restores preserve the current history instead of replacing it with an older copy. Managers can grant selected roles website access to tickets; delegated staff remain limited by ticket roles and channel visibility and cannot read configuration history.
Operational records, local transcripts and reusable knowledge may remain until removed through the available management tools or by the operator. Deleting a Discord ticket channel does not automatically delete its local transcript, moderation history, knowledge entries or backups. The default 24-hour closed-ticket cleanup concerns the Discord channel, not every archived copy of its data.
Automatic and manual full snapshots normally retain the latest 14 files, with a pending restore snapshot protected from rotation. Settings backups, restore-recovery copies and deployment recovery snapshots can retain earlier data until the operator removes them. A restore can bring back information contained in its selected snapshot. Contact the operator to discuss removal of retained copies.
Website operation
The website does not use advertising or analytics trackers. Request addresses are held briefly in memory for rate limiting. Website access logging is disabled. Operational errors and bot records may be retained for troubleshooting. Necessary session cookies support dashboard sign-in.
Access and deletion requests
For server-specific configuration questions, contact that Discord server’s owner. To request access to or deletion of stored bot data, contact the operator through the Void Bot support server. Provide the relevant server or account ID and your relationship to it so the operator can verify your request. Do not share credentials or private ticket contents publicly.
The operator can remove a server’s local operational data and review associated backups and recovery copies. Removing local data does not delete records independently held by Discord or copies already downloaded by server staff. The handling of a request depends on its scope, verified authority and applicable obligations; this page does not promise automatic removal of every copy when a bot or channel is deleted.
Policy changes
Updates to this policy will be published here with an updated date. Use the support server to contact the operator about the current policy or how a feature handles your information.