Nefarious Success privileged intents

• Message Content — YES. Automatic reposting reads attachments and captions from ordinary server messages in the designated success channel. Message Content supplies these fields when the bot is not mentioned. Existing !sp / !scl / !sclm / !sclw / !scly commands also read ordinary message text. Discord's DM, mention, own-message and message-context-menu exceptions do not cover the automatic channel workflow.
• Server Members — NO. The bot does not assign or sync roles and does not listen for join, leave, or member-update events. Moderator checks for tweet deletion use a REST member fetch, which does not require the privileged Server Members intent.
• Presence — NO. The bot never reads online status, devices, or streaming activity.

What does your application do?

Nefarious Success automatically republishes the first supported image attachment, optional message caption, and author's Discord display name from the designated success channel to our public Nefarious X account. Each successful X post earns one point. Members use !sp, !scl, !sclm, !sclw and !scly to view points and all-time, monthly, weekly and yearly leaderboards. There is no confirmation dialog before an eligible image is published. The original author, an administrator or a designated moderator can request deletion with a trash reaction on the bot reply while its in-memory post mapping exists. The bot then attempts X deletion, point removal and deletion of the Discord messages; missing permissions or API failures can prevent completion. After a restart, older posts require operator assistance. Reposting is restricted to the configured channel, but command parsing runs on messages delivered to the bot in other accessible channels and DMs. Server Members and Presence are not enabled.

Do you have a public Privacy Policy?

Yes

Where is your Privacy Policy available?

Publicly on the Nefarious website at the URL below. The operator should also add this URL to the application's Developer Portal profile.

Privacy Policy URL

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

Terms of Service URL (Developer Portal app listing)

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

Install URL: https://discord.com/oauth2/authorize?client_id=966614821174915092&scope=bot+applications.commands

Why do you need the Message Content intent?

Message Content is required for the bot's only features:

- Success reposts: the existing workflow handles ordinary image messages without requiring a bot mention. Message Content provides their attachments and optional caption. The bot publishes the first supported image with the caption and author's display name to X, then awards one point.
- Prefix commands: !sp shows points; !scl / !sclm / !sclw / !scly show leaderboards. Ordinary server command messages without a mention depend on Message Content.

Discord's exceptions for DMs, mentions, the bot's own messages and message context menu commands do not cover automatic reposting. Slash commands or a message context menu could replace this design, but are not implemented. We request access for the current channel workflow, not because prefix commands alone cannot be redesigned. No AI training or auto-moderation is implemented. Command parsing can run on other messages delivered to the bot; server channel permissions determine its access.

Proof links (screenshots / videos / live examples)

• https://discord.com/channels/909011353342181426/909400273364078612
• https://x.com/NefariousTrades
• https://www.nefarious.trading/legal/nefarious-success/intents#proof

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

No. The current implementation has no per-user opt-out setting. Avoid posting image attachments in the success channel to prevent new X reposts, and avoid commands to stop requesting points or leaderboards. This does not prevent Discord from delivering other accessible messages to the bot's command parser, and it does not erase existing records. Contact Business@nefarious.trading for deletion. Administrators can restrict channel access or disable the bot. Posting to a channel should not be represented as a verified consent mechanism unless a clear advance disclosure is actually present.

Are you storing message content data off-platform?

Yes. Yes. An eligible image, optional caption and Discord display name are published publicly on X and have no automatic expiry. The bot does not write a separate local message-body or image archive. Its library may temporarily cache delivered messages in memory. Local persistent records contain user IDs, display names, X post IDs, point timestamps and processed message IDs. Operational output includes usernames, channel/message/media IDs, post URLs and API errors; host log retention must be checked separately.

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

No.

If the form asks these under Members (it may still appear when you store API Data for any intent):

• Storing API Data off-platform? Yes (Discord user IDs, display names, points, X post IDs).
• 30 days or less? No. The current code has no scheduled purge: points, account rows and processed-message markers may remain beyond 30 days. Successful reaction deletion removes the matching earned-point entry, but leaves the user ID/name row and processed-message marker. Full erasure requires operator action. Public X posts remain until removed through the bot, the operator account or X. Deletion mappings are in memory and disappear on restart. Backup and host-log retention are not established by the source review.
• Deletion contact: Business@nefarious.trading (Business@nefarious.trading).
• Encrypting at rest? Checked September 19, 2026: the deployed persistent storage is on an unencrypted apps dataset. 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.

Leave Server Members and Presence unchecked. The bot does not assign roles, welcome members, track invites, or read online/streaming status. Delete-permission checks use a REST member fetch when someone clicks 🗑️ — that is not the privileged Guild Members gateway intent.

Live channel (guild 909011353342181426): https://discord.com/channels/909011353342181426/909400273364078612. Public X account: https://x.com/NefariousTrades.

1. Image in #success → tweet + point (needs Message Content)

A member posts an image (and optional caption) in the success channel without mentioning the bot. Message Content supplies the attachment and caption for this ordinary server-message workflow. The bot uploads the first supported image, caption and author’s display name to X and replies with a linked “Success posted on Twitter!” embed, the new point total, and a 🗑️ reminder.

2. !scl leaderboard (needs Message Content)

Ordinary server prefix commands without a bot mention need Message Content to read !scl / !sp and show ranks. The underlying points are Discord IDs and counts; neither Presence nor role assignment is needed. Slash commands could replace these commands but are not implemented.

Capture the current leaderboard separately; a repost acknowledgement does not verify it.