Legal · Discord apps · Developer Portal

Nefarious Success privileged intents

Effective September 12, 2026 · Last updated October 26, 2026

Paste pack for Discord’s Privileged Intent form for Nefarious Success (application ID 966614821174915092). These answers describe the October 26 deployment: automatic success-channel previews, author-confirmed X sharing, and working interaction fallbacks. Retained storage gaps still require resolution or accurate disclosure before certification.

Apply for Message Content only. Do not check Server Members or Presence.

On this page · 9 sections

01Reconsideration and fallback functionality

Prepared October 26, 2026. Message Content only, for ordinary posts in the designated success channel. This is review material, not a submission receipt or approval.

Feature-specific reconsideration reasoning

Nefarious Success is built around a community success channel, where members post a screenshot and optional caption as part of the normal conversation. The requested intent is for automatically recognizing those ordinary image posts and preparing an author-controlled sharing preview. It is not needed to calculate leaderboard totals, send a reply or process a button.

Without Message Content, an unmentioned ordinary message does not supply the attachments and caption needed to prepare that preview. A confirmation button can confirm a preview after it exists, but cannot retroactively give the bot the original unrelated message's protected fields. The revised workflow keeps an explicit author confirmation before publishing to X; it does not require the member to retype the caption or upload the image again merely to be offered that choice.

The operator wants members to keep posting naturally rather than learning a command before sharing their result. Automatic detection offers the same sharing path to each eligible ordinary post in the designated channel. A manual-only path changes that coverage to the members who remember to invoke the app. This is a product requirement and adoption concern, not a claim that slash commands are impossible or that users have been surveyed.

Alternatives considered
The deployed /success attachment-and-caption command and author-only Submit success message action are functional alternatives for deliberate submissions. The context action avoids retyping but still requires the member to select every post. Neither automatically discovers ordinary channel posts. Points and leaderboard interactions work independently of Message Content, so they are excluded from the intent justification.

Continuity while access is reviewed

Deployed: /success, Submit success, /sp, /leaderboard, /scl, /sclm, /sclw, /scly and /success_delete. Both submission paths use the same author confirmation, deduplication and points flow. Post mapping is now persistent; ambiguous posting outcomes are held for review rather than automatically republished.

Only the configured success channel is the source for automatic submission detection. The author can decline sharing. X is an external public destination and is disclosed before confirmation. Storage migration of active state does not establish that historical copies and logs are encrypted; those controls require separate verification before certification.

02Current review status and next steps

Request declined; normal-post workflow retained with deployed interaction fallbacks

Decision dated September 30, 2026; follow-up updated October 26, 2026. Discord determined that the described use case can be implemented without Message Content.

/success and the author-only Submit success message action are deployed, along with points and leaderboard interactions.
Normal success-channel posts still trigger a sharing preview when Message Content is available. Both paths now require the author to confirm before X publication.
Post mapping now persists across restarts for new posts. Older posts without a mapping and complete data-erasure requests still require operator handling. Historical storage and logs remain a certification gap.

The implementation notes below describe inspected behavior, not an approval guarantee. Discord’s alternatives guide.

03Verified storage and retention status

Bot storage rechecked October 26, 2026. Active Success state and configuration now use encrypted storage. Historical files, Docker logs and shared NAS snapshots still retain unencrypted copies.

The bot’s logs have no configured size or file-count limits. No automatic expiry was established for those logs. Do not select “Yes” for encryption of all stored API data or promise a 30-day deletion limit on the basis of this page.

The retention and deletion rules below describe each data category. A removal request must also address logs and backups containing the requested data. Retained-copy migration, bounded logs and a verified deletion procedure remain required operational work.

04Intent matrix

Message Content — YES. Automatic preview creation reads the image attachments and captions of ordinary messages in the designated success channel, without a bot mention. Message Content supplies those protected fields. An author-only button then confirms X publication. /success and the Submit success message action provide an implemented manual fallback, but do not automatically detect untouched channel posts. Points, leaderboards and output delivery do not independently justify this intent.
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.

05Application details (paste)

What does your application do?

Nefarious Success supports a member-success channel in the Nefarious Discord. Members post a normal screenshot and optional caption in that channel. The bot detects an eligible image, prepares a preview in the same conversation, and lets only the original author confirm sharing to the public Nefarious X account. A point is awarded after X accepts the post. Points and monthly, weekly, yearly and all-time leaderboards are part of the same service. The October 26 deployment adds author confirmation before external publication, durable source-to-X mappings for deletion after a restart, shared deduplication, slash commands and a message-context fallback. The normal-message workflow remains implemented; fallback commands are available if intent access is unavailable.

Do you have a public Privacy Policy?

Yes

Where is your Privacy Policy available?

The public policy is linked from the bot legal page and the policy URL below. Operators should keep the Developer Portal policy field and user-facing bot links current.

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

06Message Content intent (paste)

Why do you need the Message Content intent?

Please reconsider the September 30 decision against the implemented passive success-channel workflow, rather than against the bot's leaderboard commands. We are requesting Message Content only. Server Members and Presence are not required.

The event that starts the principal workflow is an ordinary member-authored message containing a success screenshot and optionally a caption. It is posted for the community to see and discuss, without a bot mention or command. The bot must inspect the message's attachments and caption to identify an eligible contribution and prepare its author-confirmed sharing preview. Without Message Content, those protected fields are unavailable for an ordinary unmentioned guild message. The bot cannot automatically identify the eligible image or build its preview from just the message ID, author ID and channel ID. A later confirmation button belongs to the bot's preview and does not supply the unrelated original message's protected content retroactively.

Our October 26 implementation responds directly to the concern that interactive alternatives should be evaluated. We deployed /success with an attachment and caption, and a 'Submit success' message-context action that the original author can invoke on an existing success-channel post. These work without Message Content and allow essential service continuity during review. All point and leaderboard commands now have interaction alternatives too. We are not asking for privileged access simply to parse !sp or !scl, and we are not claiming that an interaction-based submission system is impossible.

The remaining difference is automatic participation in the existing channel workflow. With the normal-message path, a member posts their screenshot once using Discord's regular composer, the community sees that contribution in its original context, and the bot offers the sharing preview beside it. With the context fallback, the member must know to locate and invoke an app action on each eligible post before the bot receives the protected content. With /success, the member must initiate an application submission and attach the image there. Neither fallback detects an untouched ordinary contribution. This matters for a shared community channel where participating members should be able to post naturally and discover the optional sharing action from the bot's reply. We have not measured an adoption-loss percentage and do not present hypothetical usage figures as evidence.

The request is limited to the passive source-message capture needed for this channel integration. Code rejects automatic ingestion outside the configured success channel, ignores bot authors, selects eligible image attachments, and offers an author-only confirmation before any upload or publication to X. Cancel leaves the success in Discord. Message-context submission also verifies that the selected message belongs to the invoking user and the configured channel. Source IDs deduplicate the passive and context paths, so invoking both does not produce a second X post or another point. Awards follow successful X creation; a failed Discord receipt does not trigger another X post. Author/moderator deletion can use a retained mapping after restart, and /success_delete remains available without Message Content.

We ask you to assess whether this restricted, author-confirmed, ordinary-message integration qualifies for Message Content access. The command fallbacks remain available even if access is approved, and we accept that implementing a fallback does not itself establish a right to privileged access. The linked historical evidence and deployed code should be evaluated separately: older captures predate the new confirmation and fallback controls, and no new live X post was generated merely to create proof.

Proof links (screenshots / videos / live examples)

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

No. The author can choose Keep in Discord or leave the preview unconfirmed, preventing external publication. No persistent per-user opt-out from automatic preview processing is implemented; do not describe the confirmation control as a complete processing opt-out. Administrators can restrict source-channel access or disable the bot. Contact Business@nefarious.trading for broader processing or deletion requests.

Are you storing message content data off-platform?

Yes. X receives the image and composed caption only after the original author presses Share to X. Discord receives previews and receipts. Public X posts and selected website evidence screenshots have no automatic expiry. Preview and image processing use memory, without a separate local body/image archive. Persistent IDs, display names, point timestamps, source-to-post mappings and dedup markers are stored on the host.

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

No.

07Off-platform API Data (paste)

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. No automatic 30-day expiry is implemented for points or dedup/post mappings, or public website evidence. New post mappings persist after restart. /success_delete or the trash reaction removes the X post and its point for the author or configured moderator. Historical X posts without mappings still require support. This is not yet a complete erase-all-user-data command; minimal dedup and post mapping records remain. Backup, historical snapshot and host-log retention require operator review.
Deletion contact: Business@nefarious.trading (Business@nefarious.trading).
Encrypting at rest? October 26, 2026: active points, dedup records, new post mappings and runtime configuration were copied to a verified encrypted dataset. Original plaintext stack copies, unencrypted Docker logs and historical shared snapshots remain. Do not certify that every retained copy is encrypted until those gaps are resolved and verified.

08Do not apply for Members or Presence

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.

09Proof of the use case

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

1. Ordinary image → preview → author-confirmed X post

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 current deployment prepares a preview and requires the original author to press Share to X before upload. A successful X post earns one point and receives a receipt. The example below is historical evidence of the earlier direct-publication workflow; it does not demonstrate the new confirmation controls.

View this bot’s evidence →

2. Points and leaderboards have working interaction fallbacks

/sp, /leaderboard and /scl, /sclm, /sclw and /scly are registered in the configured server and work without Message Content. The historical prefix-command example below is not a justification for privileged access. The reconsideration request concerns automatic detection of ordinary success-channel posts; /success and the Submit success message action provide a manual fallback for that feature.

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