The key point: Inferno can read message content in servers where it operates because its moderation and logging features need it. A configurable, short-lived message cache is different from warning records and Discord log messages, which may last longer. Server administrators choose which features and log channels to enable.
1. Who and what this covers
Inferno AIO operates the bot, the website at infernoaio.com, and the administrator dashboard at admin.infernoaio.com. Contact the operator at [email protected]. This policy covers data handled by Inferno. Discord and Stripe operate their own services under their own policies.
A server administrator decides whether to install Inferno, activate features, select log channels, and grant staff access within their server. The Inferno operator controls the hosted bot and can access private operational records described below.
2. What information we handle
| Information | How it is used or stored |
|---|---|
| Discord sign-in and server access | Discord user ID, display name, servers you administer, server names and icons, and current Administrator permission are used to sign you in and show eligible servers. The operator-only service view can also request a server's current approximate member count and the bot's join time from Discord. Those refreshed values are held in memory for up to ten minutes and are not saved in the dashboard database. OAuth access tokens are used during sign-in and are not saved in the dashboard database. We do not ask for your Discord password. |
| Website sessions | A Secure, HttpOnly session cookie keeps you signed in for up to eight hours; a short-lived OAuth state cookie helps protect Discord sign-in. Session and sign-in state expire or disappear on bot restart. Technical connection information, such as an IP address, may be processed by the web host to deliver and protect requests; Inferno does not run a separate advertising tracker or analytics profile on these pages. |
| Server and member information | Server, channel, role, user and message IDs; usernames, display names, nicknames, avatars and profile changes; member joins/leaves; and voice-channel join/leave/move metadata are processed when relevant features are enabled. If a server enables new-account alerts, Inferno compares account creation time with a six-month cutoff and posts an age notice in its chosen private staff channel. Account age alone does not establish that an account is a bot or unsafe. Inferno does not record voice audio or private direct messages between members. |
| Messages and moderation | Message text, attachment names or links, edits and deletions can be processed for AutoMod, spam controls, rank counting, honeypots and configured event logs. When Inferno deletes a post containing a link or image, the server's on-by-default evidence setting may copy its text and up to two attached images into a private staff log before deletion. Links in that copy are made non-clickable. Images are held briefly in memory for the copy and are not saved separately by Inferno; the Discord log copy remains under that server's channel retention. Administrators may turn this off or choose another private staff destination. A temporary message cache helps show text that was later edited or deleted only while either of those logs is enabled. It has age and row limits plus hard caps of 32 MiB per server and 128 MiB across servers. Voice join, leave, and move logs are sent to Discord without local event records. For /vctime, Inferno separately saves the server and member IDs and start/end times of observed voice intervals, without channel IDs or audio. Configured private/ignored and AFK channels are excluded; any server member can request another member's current tracked session and rolling totals. Warnings, cases, report reasons, action history and some excerpts may be saved separately. A report also opens a private Discord ticket channel where the reporter and authorized staff can discuss it; those messages remain in Discord under that server's deletion choices and Discord's policies. |
| Administrator invite lookup | When Inferno can read server invites, it saves invite codes, creators when Discord supplies them, and use counts for administrator-only lookup. It saves a joining member's ID, display name, and join time against an invite only when one changed invite and one join can be matched clearly. Discord does not supply the invite code on a member-join event, so older or ambiguous joins are not attributed. This history is separated by server and remains while that server's Inferno data is retained. |
| Optional invite-burst protection | When an administrator enables anti-raid, Inferno uses invite counts and recent joins to detect more than 10 uses of one non-administrator invite in 90 seconds. Its burst window stays in memory for 90 seconds and an incident for up to 15 minutes; this is separate from the administrator invite-lookup history above. Administrators save official invite codes in server settings. A triggered alert posts the invite code and action results to the selected private staff channel, where Discord retention applies. Inferno attempts to delete the triggering invite; vanity, allowlisted, and current administrator-created invites are exempt. |
| Optional banned-image matching | When administrators enable it, Inferno briefly reads uploaded images to calculate a 64-bit perceptual hash and a small preview in memory. Its database saves each server's banned hashes, numeric IDs and creation times; it does not store original images or previews. Administrators choose private Discord channels where Inferno posts preview copies, matched-upload notices, member IDs and moderation outcomes. For escalating responses, Inferno temporarily stores server, member and message IDs plus timestamps for matching offenses, without offense image bytes. External image links are not fetched. |
| Features you use | Per-server configuration, reaction roles, rank counts (including optional voice-time credits when enabled) and 30-day /vctime durations, giveaway entries and winners, music queue/session information, virtual game coin balances and poker/blackjack state, and other feature data are used to provide those tools. Music searches and URLs are sent to the selected media source or its service as needed for playback. |
| Giveaway draw receipts | For each draw, Inferno retains the giveaway and round number, entry and eligible counts, closing time, rules used, and winner IDs. A server member can request that draw receipt; it does not publish the full entrant list. |
| Member journey and incident views | Inferno counts joins, verifications, and each member's first qualifying message in seven- and thirty-day summaries. It temporarily uses a server-scoped member ID to count each step once, without saving message text for this view. Server administrators can also see a private timeline assembled from moderation cases, reports, appeals, and security incidents. This timeline is not a recording of every message or action. |
| Ban appeals and setup recovery | A banned member who signs in with the same Discord account may submit one explanation for an eligible Inferno ban case. Server administrators can see the appeal, decide it, and record a decision note. Optional setup recovery records the settings backup reference, channel permission changes, channel renames, and newly created role/channel IDs so an administrator can review or reverse safe changes. |
| Website bug reports | When a server administrator selects Report bug, Inferno saves their Discord ID/name, a description of up to 1,500 characters, and a point-in-time copy of that server's saved bot settings, role/channel names and permissions, active giveaway summaries, reaction-role setup, and enabled packages. This diagnostic copy does not include message contents, ticket conversations, credentials, member inventories, or payment details. Unsaved dashboard edits are not included. |
| Community reviews | An administrator of an active Inferno server may submit one review with a 0–10 rating and up to 1,000 characters. Reviews and ratings are collected privately and are not displayed on the public website for now. Before submitting, the reviewer acknowledges that their review, rating, date, Discord display name, and profile picture may be shown publicly if reviews launch later. The operator-only moderation page also stores and shows the Discord username, user ID, and names and IDs of the active Inferno servers the reviewer administered when submitting. User and server blacklist entries are kept privately to prevent or hide abusive reviews. Signing in alone does not submit a review. |
| Administrator and service records | Saved settings changes record the Discord ID/name of the acting administrator, time, server, result, and before/after configuration. The Inferno operator can review these private records for service administration, security and support, including for servers where they are not a Discord administrator. Other server administrators cannot view these records. The operator can also see service and billing status across servers. |
| Service announcements and payment notices | Inferno may send a direct message to selected Discord owners of active, connected servers for an operator-approved service announcement. The operator sees each owner's Discord username and ID before confirming a message. For a paid subscription, Inferno may message the Discord account that purchased for that server when service activates and before a scheduled automatic renewal. Inferno privately stores the announcement text or notice, selected recipient Discord IDs, username snapshots for selected announcement recipients, related server references, send time and delivery results. Discord keeps its own copy of a delivered DM; a recipient may block bot DMs. |
| Billing, when available | Stripe processes payment details. Inferno stores the selected server ID, buyer Discord ID, checkout/session reference, Stripe customer and subscription IDs, and payment/service status to activate the correct server. Inferno does not store full card numbers. Checkout is available only when billing is enabled. |
3. Why we handle it
We use this information to authenticate administrators, keep each server's settings separate, perform enabled bot functions, detect abuse, show configured logs, maintain service and backups, process subscriptions when enabled, and answer support or privacy requests. We do not sell Discord data, use message content to train AI models, or use it for advertising profiles.
Inferno processes some events automatically without a person reading them. A human may still see content when it appears in a private staff log, a warning/report, a support request, or a necessary security investigation.
4. Who can see information
Server administrators choose Discord log destinations and who can view those channels. Staff with channel access may see edited/deleted text, moderation details and profile or voice events that were logged. A report ticket is visible to its reporter, server administrators, and any moderators an administrator grants access. Discord Administrators can bypass channel restrictions. The server's own Discord permissions govern these channels and copies. The Inferno operator can access hosted configuration, operational audit and website bug reports for operation and support. Only the Inferno operator's protected owner pages can list and download website bug reports; submitting administrators receive a reference number but cannot browse another server's reports. Server administrators using the dashboard see only servers they currently administer and that are eligible for service.
Configured private-channel exclusions prevent Inferno from posting those events to its logs. They do not remove Discord's own data or copies that were already posted elsewhere.
5. How long data stays
For progressive general AutoMod timeouts, Inferno stores a server ID, member ID, timeout step, and time of the last successful timeout. The next step resets after the quiet period chosen by that server's administrators (24 hours by default). Inactive counters are pruned after about 31 days. A private timeout notice can also remain in the server's chosen Discord log channel until its administrators delete it.
- Message cache: used only when edit or deletion logging is enabled. It is configurable from 1 to 30 days, seven days by default, with a per-server row limit. Hard caps of 32 MiB per server and 128 MiB across servers remove the oldest cached text first. Expired or over-limit entries are pruned about every ten minutes while the bot runs; turning both logs off clears that server's cache on the next prune. This cache is not a full archive.
- Banned-image records: banned perceptual hashes remain until a server administrator removes them or the server's Inferno data is purged. Matching-offense ID and timestamp rows are pruned after 30 days by the hourly retention task while the bot runs. Warnings and other moderation cases created by a response can last longer. Image previews and offense notices posted in private Discord channels follow those channels' retention, not Inferno's database cleanup.
- Short-lived event records: blacklist incidents and rank-message deduplication are pruned after about 30 days; role-mention spam incidents after about one day. These windows are separate from warning or case history.
- Blackjack hand state: finished hand details are removed from Inferno hosting after seven days. The shared coin balance remains while the server uses Inferno; game posts in Discord follow that channel retention.
- Member journey and security summaries: member-specific journey markers are pruned after about 35 days, daily aggregate counts after about 180 days, and the extra security-incident summaries after about one year. Existing moderation cases, reports, and appeals have their own longer feature retention.
- Voice-time durations: /vctime interval timestamps and server/member IDs are deleted from live storage after 30 days by the hourly retention task while Inferno runs. Current sessions are updated about every 30 seconds; a restart or outage can leave a short gap. Older activity cannot be reconstructed. Routine backups may retain an older copy until their usual rotation.
- Website bug reports: open reports remain available for diagnosis while the server uses Inferno. After the Inferno operator marks one fixed, the active report file and copies in routine on-server snapshots are deleted after seven days by an hourly cleanup task while the bot is running. Reports for removed servers, including open reports, are deleted with that server's data after its 30-day recovery window. A recent snapshot being written can delay cleanup until the next retry. Manually created recovery copies outside the routine snapshot folder may remain until separately removed.
- Community reviews: a submitted review remains private during collection and may be published later as described above. It stays saved until the Inferno operator deletes it; a user or server blacklist prevents it from appearing if public reviews launch. Reviewer and blacklist records have no automatic expiry. A deleted review may remain in a routine backup until that backup rotates. Contact us to request deletion of your own review.
- Moderation, rank, giveaway, game-wallet, poker, audit, settings and billing records: generally remain while needed for the feature, server service, accounting or dispute resolution; there is no universal automatic 7-day deletion for them. Ask us about a specific record.
- Service-message records: confirmed announcement text, selected recipient IDs, username snapshots and delivery results remain while needed for service administration and dispute review; no fixed automatic deletion period currently applies. Unconfirmed previews expire after ten minutes and are pruned when a new preview is made. Owners left unchecked on confirmation are removed from that announcement's recipient record. When a removed server reaches its 30-day data purge, its name and ID are removed from recipient mappings, its payment notices are deleted from live data and retained routine snapshots, and a recipient username is cleared if no server reference remains. Delivery receipts can remain without that server reference. A delivered DM remains subject to Discord and the recipient's own deletion choices.
- Discord logs and ticket discussions: messages posted in a log or report ticket channel remain there under that server's Discord retention and deletion choices. Closing a ticket makes its reporter read-only; it does not delete the conversation. Deleting Inferno's local cache does not delete these posts.
- Retired early-access signups: signup and Dollar 50 membership tracking have ended. Old signup records were removed from the active database when the program closed. Earlier backups may retain a copy until their normal rotation.
- Removed servers: a secondary server's hosted configuration and feature data are held for a 30-day re-add window, then the bot runs a purge of that server's records and retained on-server snapshots. The purge can be delayed if the service or cleanup is unavailable. This does not delete the Discord server or its messages.
- Backups: on-server snapshots run daily and keep the latest 14. Routine new snapshots omit temporary message-cache text while retaining configuration, moderation, security, and other feature records. An optional private offsite backup may copy those snapshots to Cloudflare R2 or DigitalOcean Spaces if configured; that job removes its archives older than 14 days. Older or manually made snapshots can still contain cached text until they rotate or are removed. Other deleted live data can remain in a snapshot until rotation, except where the removed-server purge also scrubs that server from those snapshots. Other required operational or legal records may be kept as law permits or requires.
7. Security and limits
Inferno uses HTTPS for the website, Discord OAuth, server-side permission checks, private hosting storage, and restricted access to private operational records. No online service can guarantee perfect security. Server administrators are responsible for Discord channel permissions: a “private” log channel is visible to anyone they allow into it.
8. Your choices and requests
You can sign out of the dashboard or ask a server administrator to change enabled logging or delete Discord log posts they control. To ask Inferno for access, correction, or deletion of hosted data, email [email protected] with your Discord user ID and the server ID if relevant. Do not send passwords or payment-card details. We may verify your connection to the account and retain limited records where required for security, billing, legal obligations, or disputes. We will explain any limit that applies to a request.
Removing the bot from a server triggers the 30-day recovery window described above. It does not by itself remove messages Inferno already posted in Discord or cancel a Stripe subscription; subscription management is separate.
9. Changes and contact
We will update the date on this page when the policy changes. Material changes to how Inferno handles data will be announced through the site or service before they take effect when practical. Questions or privacy requests: [email protected].