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. Discord does not deliver that text, those embeds, or those attachments without Message Content.
• Server Members — YES. on_member_join does not fire without Server Members. The join log diffs invite use-counts and posts who invited the new member. Slime/unslime must list and edit a member’s roles (strip to pending-removal, store previous_role_ids, restore on unslime or ⚠️). Those are role snapshots, not presence.
• 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.

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?

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

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. Discord does not deliver that content without this intent.
- 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 bot does not scan every channel for chat, does not read DMs as a product feature (it only sends a promo DM when the member runs !ThankYouES), and does not use message text to train machine-learning or AI models. Without this intent, stickies, slime, ticker digest, link filters, and prefix commands cannot work.

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?

Yes. Yes, for ordinary member chat. The bot does not archive the whole server. Members opt out of commands by not running them. Link-filter and ticker-monitor channels are always watched; those rooms are configured for other bots and staff filters, not general conversation. Staff-only commands (sticky, slime) are role-gated. A member can leave the server or email Business@nefarious.trading to ask us to delete stored IDs, sticky text they wrote, or a slime snapshot about them.

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 — 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 two features in NefariousAlerts.py, not for welcome cards or leveling.

- Join logging: on_member_join only fires with this privileged intent. The bot snapshots guild invites, diffs use counts, and posts a “Member Joined” embed (member mention/ID, invite code, inviter, account age) to a staff join-log channel.
- Slime / unslime: the bot reads member.roles, replaces them with a pending-removal role (keeping managed roles such as Nitro Booster), stores previous_role_ids, restores that list on unslime or a ⚠️ reaction, and checks staff / immune / decider roles. fetch_member and role edits are part of that path.

The bot does not assign ranks, does not send welcome DMs, and does not read presence. Invite tracking is staff-facing attribution, not a public invite-leaderboard product.

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

Yes. Yes. A person opts out of join logging by not joining the server. Slime is a staff moderation action, not something members enable. Anyone can email Business@nefarious.trading to ask us to delete a join-log post we still control or a slime decision row (user ID + previous role IDs).

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 after 24 hours. 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 Trump-schedule message IDs are kept while that feature is in use or until we delete them on request. Invite snapshots live in memory and are not written to the state file.
• 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 host volume that holds alerts_state.json / es_codes.json is actually encrypted (for example BitLocker, LUKS, or NAS dataset encryption). Do not check Yes if those files sit unencrypted on disk.

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

1. Role ping after a watched-bot alert (Message Content)

Discord only delivers the watched bot’s new message (so we know it is not a Zoom link and can reply) if Message Content is on. The reply is a single role mention — no embed.

2. !stick (Message Content)

Prefix commands are ordinary messages. Without Message Content the bot cannot see !stick or the sticky body. It stores the text and message id, then deletes and reposts after later chatter.

3. slime @user (Message Content + Server Members)

The unprefixed phrase needs Message Content. Reading and rewriting member.roles and firing on_member_join for the join log need Server Members. Presence is not involved.