Nefarious Backup Terms

Nefarious Backup is a private disaster-recovery process for the Nefarious Discord (guild 909011353342181426). It is not a public App Directory product, not a membership perk you purchase, and not a bot we invite other communities to install.

• Daily mirror (2:00pm America/Los_Angeles): copies new messages from configured source text channels into matching channels on a private backup Discord server, using webhooks so the copy shows the author’s display name and avatar.
• Weekly snapshot (Saturday 2:00pm America/Los_Angeles): writes JSON (and image files) to operator-controlled storage and keeps the last 4 weekly folders.
• Restore: operators can load a numbered weekly snapshot back onto the backup server (purge + repost) and reapply saved roles, nicknames, and bans.
• Some categories are excluded. Some high-volume channels keep only the latest 250 messages.

Prefix commands (?backup, ?backup status, ?backup list, ?backup load <n>, ?backup setup, and related) work only for Discord user ids on an operator allow-list. Everyone else is told they are not authorized. Ordinary members have no backup UI.

• Operators — people we authorize to run the bot, host its stack, or access snapshot files. Commands are refuse-by-default.
• Members of a guild the bot is configured to copy. If you post in a backed-up channel, that post may be mirrored and snapshotted as described in the Privacy Policy.
• You must meet Discord’s minimum age. Nefarious community tools are not directed at children under 13.

We do not offer this bot to third-party servers. If you see it outside Nefarious-operated guilds, it is not a supported install.

Discord’s privileged-intent form asks why a bot needs Message Content, Server Members, or Presence. Answers for this bot come from the running code, not from MEE6 welcome/leveling text. Full paste pack: /legal/nefarious-backup/intents.

• Message Content: used. The bot copies ordinary message text, embeds, and image attachments from the source guild into a backup guild and into weekly JSON snapshots. Operators also use prefix commands (?backup). Discord strips content, embeds, and attachments without this intent.
• Server Members: used. Complete weekly snapshots list members (id, username, nickname, role ids) via fetch_members so a restore can recreate nicknames and role assignments. Role definitions and bans are also snapshotted. The running stack can leave this intent off (ENABLE_MEMBERS_INTENT); without it, member rows fall back to authors seen in messages only.
• Presence: not used. The bot never reads online, idle, DND, device, or streaming status.

Presence is not requested. Slash commands cannot replace history copy: the bot must read messages members already posted.

You keep whatever rights you have in content you post on Discord. To run backups we need a limited licence to copy, store, and redisplay that content on the backup guild and in snapshot files for disaster recovery and operator review — not to sell it or to train AI models.

This is an operations copy, not a public archive. The backup guild is not a second community for members to browse. See Privacy for what is stored, how long, and how to ask for deletion.

THE BOT, THE BACKUP GUILD, AND EVERY SNAPSHOT ARE PROVIDED “AS IS” AND “AS AVAILABLE”, WITHOUT WARRANTIES OF ANY KIND, WHETHER EXPRESS, IMPLIED, OR STATUTORY, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, COMPLETENESS, AND UNINTERRUPTED OPERATION.

We do not warrant that:

• every channel or message will be copied, or copied in order, or copied on time;
• attachments other than images, or messages Discord hides from the bot, will be saved;
• a restore will succeed, match the original server, or preserve reactions, threads, or pins exactly;
• snapshots will survive disk failure, operator error, or a Discord outage;
• the backup guild will stay private, online, or unpurged.

Rate limits, missing permissions, excluded categories, the 250-message cap, and Discord API gaps all mean backups can be incomplete. This tool exists to reduce loss. It is not a guarantee against loss.

TO THE MAXIMUM EXTENT PERMITTED BY LAW, NEFARIOUS AND ITS OWNERS, OPERATORS, AND CONTRACTORS WILL NOT BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR LOST DATA, LOST MESSAGES, FAILED RESTORES, BUSINESS INTERRUPTION, OR TRADING LOSSES, ARISING FROM THIS BOT OR THESE TERMS — EVEN IF ADVISED THAT SUCH DAMAGES WERE POSSIBLE.

TO THE MAXIMUM EXTENT PERMITTED BY LAW, TOTAL LIABILITY FOR CLAIMS RELATING TO Nefarious Backup WILL NOT EXCEED THE GREATER OF (A) THE AMOUNTS YOU PAID US SPECIFICALLY FOR THIS BOT IN THE THREE MONTHS BEFORE THE CLAIM (typically none; the bot is not sold) OR (B) FIFTY U.S. DOLLARS (USD $50).

Some places do not allow certain limitations. Those limits apply only as far as local law allows. Nothing here excludes liability that cannot be excluded (including fraud). This section works with the site-wide limitation of liability and Section 13 of the site Terms.

Nefarious Backup runs on Discord. Your use of Discord is governed by Discord’s Terms of Service and Community Guidelines. Nothing here overrides Discord. We may disable intents, rotate tokens, exclude channels, or shut the bot down to stay within platform rules.

Hosting (including the nefarious-backup Docker stack and NAS volume) is operator-controlled infrastructure, not a consumer cloud product we sell you.

You may not:

• run or impersonate Nefarious Backup on servers we did not authorize;
• use operator commands if you are not on the allow-list, or try to bypass that check;
• treat snapshot files or the backup guild as a public leak, scrape, or resale archive;
• use restored or mirrored content to harass, doxx, or violate Discord’s rules or the law;
• demand that we keep a perfect, indefinite archive of every message.

We may stop the bot, prune snapshots, or purge the backup guild at any time.

We may update these Terms by posting a new version at this URL. The “Last updated” date will change. Continued presence in a backed-up server after an update is acceptance. Material changes will also be noted on the legal hub when that page is live.

Contact

Business@nefarious.trading. Deletion and privacy: Privacy Policy, deletion.

This is not a welcome, leveling, or invite bot. A daily run posts webhook copies that look like the original author. A weekly run writes JSON that includes the message content field — that is the off-platform store described in Privacy.

Operator commands use the ? prefix. Source guild: discord.com/channels/909011353342181426. The backup guild is private and is not an invite for members.