Nefarious Backup privileged intents

• Message Content: required. Required to read ordinary source-channel message text, embeds and attachments for history backup and webhook mirroring, for the passive archive. Deployed /backup commands replace operator input when needed, but do not supply unrelated historical messages. The Archive this message action saves only an explicitly selected record.
• Server Members: optional, currently off. Currently disabled in the deployed configuration. Request Server Members only to enable complete member-state snapshots through fetch_members. That feature records IDs, usernames, nicknames and role assignments for members with a nickname or extra roles. The current fallback records message authors with no role assignments; role definitions and bans alone do not require this intent.
• Presence: no. Online status, activities and streaming presence are not used by the backup workflow.

What does your application do?

Nefarious Backup is an operator-controlled disaster-recovery application. It reads configured ordinary source-channel history into a durable NAS archive, saves scheduled snapshots and mirrors supported content into a separate backup Discord server. Author display names/avatar URLs, message text, embeds, IDs, timestamps and supported media metadata are retained; permitted photos/videos are downloaded subject to actual-file-type checks. Unsupported media can be skipped.

Only allow-listed operators in the configured source or backup guild can use /backup help, status, list, verify, channel, mirror, snapshot, now, load, setup and cleanup. Load/setup/cleanup require explicit confirmation. Legacy prefix commands remain available while Message Content access permits them. The Archive this message action saves one deliberately selected source record and attachment links, deduplicated by message ID without advancing the full-history cursor. It is not a complete archive or attachment-file download.

The inspected recovery setting preserves existing archive history, including older records in nominally limited channels. Four successful snapshot folders are retained by count; the primary archive, partial snapshots and legacy copies have separate retention. Complete member-state snapshots remain disabled. Role definitions, bans and available message-author rows do not imply full member enumeration. If Discord rejects a privileged-intent handshake, the client retries once with all privileged intents off. If Message Content is unavailable, automatic content capture pauses rather than overwriting archives with empty fields; existing saved records and interaction controls remain available.

Privacy Policy

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

Terms of Service

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

Add the public policy URLs to the application’s Developer Portal settings. A live website policy does not establish that the profile fields have been updated.

Why is Message Content required?

Please reconsider Message Content for the implemented continuous archive and recovery feature, separately from operator command handling. The bot must preserve ordinary community messages, embeds and supported attachments from configured source channels, including history posted when the bot was offline, so a later loss or deletion does not make the authorized backup unusable. Members post those messages normally without mentioning or invoking the bot.

We have deployed /backup interaction controls, including status, snapshot, mirror and restore. Those commands authorize an operation but do not carry the unrelated source messages the operation needs to retrieve. Message Content restrictions apply to REST history content as well as Gateway payloads; switching the trigger to a slash command cannot recover omitted content, embeds or attachment fields. A mention-only workflow would retain only messages mentioning the bot and lose the rest of the channel.

The deployed Archive this message context action is a useful limited fallback. It receives the selected payload and saves that one record, without moving the full-history cursor or falsely marking the archive complete. Requiring an operator or every author to select every message is a different collection service: it omits unselected and offline-period messages, requires continuous human intervention and cannot provide the existing complete-history recovery behavior. A /backup command alone cannot eliminate that gap.

The request is limited to configured source guild/channels, exclusions and allow-listed operators, with a separate backup destination. It does not read DMs or use content for AI training, advertising or resale. Request only Message Content; complete member snapshots are disabled and Presence is unused. If access is unavailable, the client can run interaction-only controls while automatic content capture is explicitly paused. Stored records are preserved rather than overwritten with missing fields.

The evidence must show an actual permitted source record, stored archive and controlled destination/restore outcome. Existing historical retention, manual deletion handling and legacy/log encryption gaps are disclosed; these limitations are not cured by publishing policy wording. Reviewers should evaluate the implemented archive rather than treating slash administration as a substitute for its underlying data access.

Can users opt out?

No automated per-user opt-out. There is no in-bot per-user exclusion. Contact Business@nefarious.trading to request deletion or a collection restriction. Operators can exclude channels or categories from future collection. Leaving the server does not erase historical copies or prevent accessible old posts from appearing in a later history scan. Requests require manual handling across the archive, snapshots, images and backup Discord copies.

Do you store message content off-platform?

Yes.

Yes. A durable SQLite archive and JSON exports on operator storage contain message text, embeds, message and author IDs, usernames, display names, avatar URLs, timestamps and attachment metadata. Snapshot folders also contain permitted downloaded photos/videos, role definitions, ban records and available member rows. The backup Discord guild holds a separate mirrored copy. Snapshot rotation does not expire the durable archive.

Is message content used for AI training?

No.

Request this only if complete member nickname and role backup is a feature being enabled and demonstrated. The deployed configuration currently disables enumeration; do not describe it as active.

Use this answer only if applying to enable the currently disabled complete member-state backup feature.

With ENABLE_MEMBERS_INTENT enabled, snapshot_guild_metadata enumerates guild members through fetch_members and records Discord user ID, username, nickname and role IDs for members with a nickname or non-default roles. Restore uses these records to attempt nickname and role restoration for users present in the destination guild.

The currently deployed setting is false. The current fallback creates rows from message authors, with display-name-derived nicknames and empty role lists. It cannot preserve every member or their assigned roles. Reading role definitions and bans alone does not justify Server Members. We do not use Presence.

Member-data opt-out

Complete member enumeration is currently disabled. There is no automated per-member exclusion if it is enabled. Privacy requests go to Business@nefarious.trading and require manual handling of retained copies. Leaving does not automatically remove earlier records.

After approval, enabling this feature requires a deployment change and a demonstration of the resulting member snapshot and supported restore. This audit did not change the bot configuration.

Do you store API Data off-platform?

Yes.

Is all stored API Data retained for 30 days or less?

No. The historical archive has no automated age-based expiry and can retain content older than 30 days. The configured rotation retains four successful snapshot folders, counted by completed runs rather than weeks or message age. Partial snapshots and legacy migration copies are outside that rotation. Backup Discord messages and runtime mappings can remain until operator removal. A recent snapshot can contain years-old messages.

Encryption at rest

Checked October 26, 2026: the primary archive dataset is encrypted, but legacy storage and container logs remain unencrypted. Container JSON logs have no configured rotation limits. Do not select Yes for encryption of all stored API data until storage and log remediation is verified.

Deletion requests

Business@nefarious.trading. Requests require manual processing across all retained copies.

Open the source Nefarious server. Discord links require the reviewer to have access. A server link alone is navigation and does not prove a successful backup.

• History collection: configured text-channel history is serialized into a durable message archive. Saved fields include content, embeds, author display data and image attachment metadata.
• Backup output: webhook mirror jobs read the archive and repost supported content in the destination server. Display names and avatar URLs come from the archived author data; mentions are disabled.
• Daily snapshots: scheduled runs save channel JSON and image files before mirroring. Successful snapshots rotate by count; the historical archive and legacy copies have separate retention behavior.
• Operator controls: deployed slash commands include /backup status, /backup list, /backup snapshot, /backup mirror and /backup load. These require an allow-listed user ID in a configured guild; load/setup/cleanup require confirmation. Archive this message saves a selected record without claiming a complete channel backup.

The Evidence page includes inspected snapshot manifests and an operator workflow example. For an end-to-end delivery demonstration, pair a permitted source message with its real destination copy and capture an actual operator status or snapshot result. Include message links and the capture date. Any HTML rendering must be identified as a reconstruction; it is not a Discord screenshot. This page does not claim that a completed member enumeration was observed.

Verify destination access controls, encryption for each retained storage copy and a working deletion process. Confirm the scope and retention of historical collection with Discord where necessary. Publishing legal wording does not by itself establish compliance or guarantee intent approval.

Reference: Discord’s privileged intent documentation and Developer Policy.