Nefarious Backup privileged intents

• Message Content — YES. The bot must read message text, embeds, and image attachments in source text channels so it can mirror them to a private backup server and write weekly off-platform snapshots. Operators also run prefix commands (?backup). Slash commands cannot replace history copy: members are not invoking the bot when they post.
• Server Members — YES. Full member-state backup lists every member’s id, username, nickname, and role assignments so a restore can put nicks and roles back. Role definitions (name, color, permissions) and the ban list are snapshotted even without this intent; per-member role/nick restore is incomplete without it.
• Presence — NO. The bot never reads online status, activities, or streaming.

What does your application do?

Nefarious Backup is an internal, admin-only disaster-recovery bot for the Nefarious Discord. It is not listed as a public consumer product and ordinary members cannot run its commands.

Once a day it copies new text-channel messages from the main Nefarious guild into a private backup Discord server (webhooks post the author’s display name, avatar, message text, image URLs, and rich embeds). Once a week it also writes a full snapshot to operator-controlled storage: per-channel JSON of message ids, timestamps, author id/name/display name/avatar, message content, embeds, image files, plus guild role definitions, the ban list, and (when Server Members is enabled) member nicknames and role assignments. Operators can restore a weekly snapshot onto the backup server. A short allow-list of operators runs prefix commands such as ?backup status, ?backup list, ?backup load, ?backup mirror, and ?backup now.

The bot does not welcome members, does not level users, does not track invites, does not read DMs, and does not read presence or online status. Some categories are excluded; some high-volume channels keep only the latest 250 messages.

Do you have a public Privacy Policy?

Yes

Where is your Privacy Policy available?

Official Nefarious website (nefarious.trading) and this application's Discord profile.

Privacy Policy URL

https://www.nefarious.trading/legal/nefarious-backup/privacy

Terms of Service URL

https://www.nefarious.trading/legal/nefarious-backup/terms

Install URL (operators only; not a public listing): https://discord.com/oauth2/authorize?client_id=1511899722393063554&scope=bot+applications.commands

Why do you need the Message Content intent?

Message Content is required because this bot’s only job is to copy existing server messages for disaster recovery.

- Daily mirror: the bot reads ordinary text-channel history (content, embeds, image attachments) and reposts those fields to a private backup Discord server. Members are not invoking the bot; they are posting in community channels. Slash commands, context menus, and “bot mention only” exceptions cannot supply historical or passive message text.
- Weekly snapshot: the same fields are serialized to JSON and image files are downloaded to operator-controlled storage so staff can restore the backup server after loss or corruption.
- Operator commands: a short allow-list uses prefix commands (?backup status / list / load / setup / mirror / snapshot / now). Those are ordinary messages; without Message Content the bot cannot see the command text.

Without this intent Discord blanks content, embeds, and attachments, and the backup would be empty. The bot does not use message text to train machine-learning or AI models, does not sell message data, and does not scan DMs.

Proof links

• https://www.nefarious.trading/legal/nefarious-backup/intents#proof
• https://www.nefarious.trading/legal/nefarious-backup/privacy
• https://discord.com/channels/909011353342181426

Can users opt-out of having their message content data tracked?

No. No per-message opt-out inside a backed-up channel. This is a server-wide disaster-recovery copy of configured text channels. A member opts out by leaving the Nefarious Discord, asking operators to exclude a channel or category, or emailing Business@nefarious.trading to request deletion of their messages from snapshots and the backup server.

Are you storing message content data off-platform?

Yes.

Yes. Weekly snapshots store message content off Discord: per-channel JSON files include message id, timestamp, author id/username/display name/avatar URL, the full message text, embeds, image attachment filenames/URLs, and downloaded image files. We keep the last 4 weekly snapshot folders on operator-controlled storage (NAS volume for the nefarious-backup stack) and delete older folders. A live copy also exists on a private backup Discord server (still on Discord). Runtime state (channel maps, last-copied message ids) does not include message bodies.

Will the message content data be used to train machine learning or AI models?

No.

Why do you need the Server Members intent?

Server Members is required for a complete backup of member state, not for welcome messages or invite tracking.

The weekly snapshot writes guild.json with role definitions and, when this intent is enabled, a members list from fetch_members: Discord user id, username, nickname, and role ids for members who have a nick or extra roles. On restore the bot reapplies nicknames and roles and reapplies the saved ban list. Role names/colors/permissions can be read from the guild’s role list without this intent; listing every member’s nick and role assignments cannot.

This bot does not send join/leave greetings, does not assign levels, and does not track invites. Presence is not used.

Can users opt-out of having their member data tracked?

No. No per-member opt-out of the operational backup while they remain in the server. Members can leave the Discord or email Business@nefarious.trading to ask us to remove their member row and messages from snapshots and the backup guild.

After Discord grants this intent, set ENABLE_MEMBERS_INTENT to true in the bot config so the process actually calls fetch_members. Until then the code leaves intents.members off so the container does not crash.

• Storing API Data off-platform? Yes (message JSON, images, roles, bans, member rows).
• 30 days or less? No. Weekly JSON snapshots and downloaded images are kept for the last 4 weekly runs (about four weeks), then pruned. The live backup Discord server may retain mirrored messages longer until operators purge or restore. Channel maps and last-message ids are kept while the bot is operated.
• Deletion contact: Business@nefarious.trading (Business@nefarious.trading).
• Encrypting at rest? Discord requires encryption at rest if you store API Data. Select Yes only if the NAS volume that holds /app/data/snapshots is actually encrypted (for example LUKS or the NAS’s dataset encryption). Do not check Yes if snapshot JSON sits unencrypted on disk.

Leave Presence unchecked. The bot never reads online status, activities, or streaming. Form fields about presence opt-out and storing presence off-platform are N/A: No — we do not collect presence.

Source guild (Nefarious): https://discord.com/channels/909011353342181426. The destination backup guild is private and is not a member invite. Privacy disclosure: /legal/nefarious-backup/privacy.

1. Webhook mirror (needs Message Content)

A member posts ordinary text (and maybe an image) in a source channel. The bot reads message.content, image URLs, and rich embeds — fields Discord blanks without Message Content — and the webhook reposts them under the author’s display name.

2. Weekly NAS JSON (message content stored off-platform)

Saturday’s job writes the same fields to disk. This is the honest “store message content off-platform: Yes” answer. Last four weekly folders are kept; older ones are deleted.

{
  "channel": { "id": "9094…", "name": "general-chat" },
  "message_count": 1842,
  "messages": [{
    "id": "123…",
    "created_at": "2026-09-12T21:04:00+00:00",
    "author": { "id": "196…", "name": "alex", "display_name": "Alex" },
    "content": "anyone else watching the open? volume looks thin",
    "embeds": [],
    "images": [{ "filename": "chart.png", "file": "images/9094…/123…_chart.png" }]
  }]
}

3. Member/role snapshot (needs Server Members for a complete list)

guild.json stores roles and bans always. A full members array (nick + role ids) uses fetch_members, which needs Server Members. Without that intent the bot only records authors it already saw in messages.