Nefarious Alerts privileged intents

• Message Content — YES. The bot is a command and filter bot, not a poster-only feed. It must read (1) prefix commands such as !stick and !tickers, (2) unprefixed staff phrases slime / unslime / trump schedule, (3) Zoom and Apex URLs in two configured channels so it can delete them, and (4) $cashtags in a tweet-mirror channel for the 24-hour digest. For ordinary guild messages outside Discord's documented exceptions, Message Content makes text, embeds, and attachments available. Receiving message events or sending role pings does not itself require this intent.
• Server Members — YES. Server Members supplies join/member-update events and the full member list used for recurring staff-impersonation scans. The bot compares usernames, display names, and server nicknames with protected staff names and can automatically apply moderation restrictions. Join events also drive invite attribution. Individual member fetches and role edits are not independent reasons to request this intent.
• Presence — NO. The client never sets intents.presences. No code reads online status, devices, or activities.

What does your application do?

Nefarious Alerts is an operator-run Discord bot for the Nefarious trading community. It is not a public App Directory product.

In configured channels it: (1) replies with a role mention when a watched alert bot posts a new message (so members who opted into that role get a ping); (2) keeps a staff-written sticky message at the bottom of a channel by deleting the old sticky and reposting it after new messages; (3) runs staff-only slime / unslime — strip a member to a pending-removal role, store their previous role IDs, purge their recent messages, lock that role out of some categories, and post a decision message staff can revert with a warning-sign reaction; (4) reads $cashtags from tweet-bot embeds in one monitor channel and posts a 24-hour ticker digest; (5) deletes Zoom and Apex Trader Funding links in two channels; (6) on member join, diffs invite use-counts and posts which invite was used; (7) posts a public presidential remarks schedule and pings a speak role shortly before those events; (8) DMs Early Supporters a personal Whop promo code when they run !ThankYouES; (9) checks usernames, global display names, and server nicknames against configured protected staff names on joins, profile changes, and scheduled member-list scans. Matches can trigger automatic role restrictions, message purges, and a staff review post. Staff can review and reverse role restrictions; deleted messages cannot be restored.

The bot does not level users, does not play music, does not send welcome DMs, and does not read presence or online status. Nothing it posts is investment advice.

Do you have a public Privacy Policy?

Yes

Where is your Privacy Policy available?

Publicly available on the official Nefarious website at the policy URL below. Add that URL to the application's Discord Developer Portal profile before submission.

Privacy Policy URL

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

Terms of Service URL (Developer Portal app listing)

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

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

Why do you need the Message Content intent?

Message Content is required for the features this bot actually runs. These are ordinary Discord messages, not slash commands:

- Alert pings and link filters: in two configured channels the bot reads new (and edited) message text and embeds so it can delete Zoom or Apex links and, when a watched bot posts a clean alert, reply with a role mention. Message Content supplies the text/embeds needed for filtering. The role ping by itself does not require Message Content.
- Stickies: staff type !stick <message>. The bot must see that command text to store and repost the sticky.
- Slime / unslime: staff type slime @user or unslime @user with no slash command. The bot must see the phrase and the mentioned user.
- Ticker digest: the bot extracts $TICKER cashtags from tweet-bot message text and embeds in one monitor channel, then posts !tickers / a daily digest.
- Trump schedule and Early Supporter codes: unprefixed “trump schedule…” phrases and !ThankYouES are ordinary messages.

The gateway receives messages in channels the bot can access and inspects text for supported commands. Filters and ticker extraction are limited to configured channels. Direct-message commands can reach the handler, and requested promo codes are sent by DM. The bot does not maintain a general conversation archive or use message text to train machine-learning or AI models. Without this intent, ordinary guild-message commands and filtering lose the text needed to operate outside Discord's exceptions (including DMs and messages mentioning the bot).

Proof links (screenshots / videos / live examples)

• https://discord.com/channels/909011353342181426/1511418965249888377
• https://discord.com/channels/909011353342181426/1504278715125993512
• https://discord.com/channels/909011353342181426/1519909922417021019
• https://www.nefarious.trading/legal/nefarious-alerts/intents#proof

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

No - no built-in per-user processing switch. There is no per-user opt-out command. Not invoking a command avoids that optional action, but does not stop configured filtering, accessible-message command checks, or moderation. Server administrators can restrict channel access, disable features, or remove the bot. Members can request access, correction, or deletion by emailing Business@nefarious.trading. Leaving does not automatically erase existing records.

Are you storing message content data off-platform?

Yes. Yes, in a limited way: we store staff-written sticky text, extracted $cashtag symbols plus the source Discord message ID, and (for slime) user IDs plus previous role IDs. Impersonation flags store member names, matched protected names, guild ID, and timestamps. This is not a full chat archive. Processed and pinged message IDs are stored without the message body. We do not keep ordinary member message text on disk. Discord itself retains channel history under its own policy.

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 the deployed bot's join/member-update events and full member-list scans.

- Invite attribution: on_member_join compares cached invite use counts and posts a staff join-log embed with member identity, available invite/inviter information, and account age. Attribution may be unavailable or ambiguous.
- Staff-impersonation detection: the bot chunks the guild member list for periodic scans and checks usernames, global display names, and server nicknames against protected staff names. Join/member-update events trigger additional checks. A match can automatically apply a pending-removal role, purge recent messages, and create a staff-review decision. Stored flags include user ID, name signature, matched name, guild ID and timestamp. Staff can review and reverse role restrictions.
- Moderation support: the member cache supports role snapshots and exemption checks. Individual REST fetches and role edits are not, by themselves, reasons to request this privileged intent.

The bot does not read Presence. The application requests Server Members for these deployed features, not merely to count users.

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

No - moderation has no per-user opt-out switch. Join attribution and impersonation checks are server moderation features. Members cannot disable them with a command. Administrators can change configuration or remove the bot. Affected members may ask staff to review a mistaken restriction and email Business@nefarious.trading for access, correction or deletion. Leaving the server does not erase existing records.

Live join-log channel: https://discord.com/channels/909011353342181426/909379483641987093. Slime decisions: https://discord.com/channels/909011353342181426/1519909922417021019.

• Storing API Data off-platform? Yes (sticky text + message ids, slime user/role ids, cashtags, Early Supporter Discord ids).
• 30 days or less? No. Ticker cashtag rows are pruned against a rolling 24-hour window when processing/resynchronization runs; an offline bot cannot execute pruning. Processed/pinged message IDs are capped by count, not a 30-day timer. Sticky text, slime decision records (target user ID, moderator ID, previous role IDs, status), Early Supporter Discord IDs mapped to promo codes, and impersonation flags have no automatic expiry and can remain until manually removed. Schedule state has separate recent-day pruning. Operational logs can include usernames, IDs, invite attribution and impersonation matches; host log retention has not been verified. Invite snapshots live in memory and are not written to the state file.
• 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 Presence unchecked. The client never sets intents.presences. No code reads online status, devices, or activities. N/A — we are not applying for Presence. No — we do not collect presence.

Guild 909011353342181426. Configured rooms (members only):

• Alert ping / Zoom filter: https://discord.com/channels/909011353342181426/1511418965249888377
• Ticker monitor: https://discord.com/channels/909011353342181426/1504278715125993512
• Apex link filter: https://discord.com/channels/909011353342181426/1483674425684529188
• Slime decisions: https://discord.com/channels/909011353342181426/1519909922417021019

The source-linked sticky command and bot response demonstrate message-text processing. Role pings alone do not require Message Content. Server Members is separately justified by join/member-update events and full-member impersonation scans; the sticky example does not prove that intent. Channel links above require appropriate Discord access and are navigation, not independent screenshots of each feature.