Drippy Alerts privileged intents

• Message Content — YES. The bot must read the source alert’s text, embeds, and attachments so it can forward that same content to destination servers. Discord does not deliver those fields without Message Content.
• Server Members — NO. The bot does not welcome members, assign or inspect roles, track invites, or listen for join, leave, or member-update events. Forwarding a public alert does not require Server Members.
• Presence — NO. The bot never reads online, idle, DND, device, or streaming status.

Drippy Alerts is an analyst-alert relay operated with the CryptoCalls config manager (https://crypto-calls.vercel.app/dashboard). It watches one operator-configured Discord channel where the analyst Drippy posts analyst alerts, reads those messages, and forwards the same text, embeds, and attachments to destination Discord servers (or webhooks) so members there see the alert without waiting for a human to copy it.

The bot does not welcome members, assign roles, track invites, run a leveling or XP system, auto-moderate chat, detect keywords for custom commands, or read anyone’s online or streaming status. It is not a MEE6 Custom Bot and it does not mirror MEE6 features. It only relays public alert-channel messages that an operator chose to fan out.

Source channel (Nefarious guild): https://discord.com/channels/909011353342181426/1520964590853165086

This relay is free. Nefarious Digital does not charge a fee, subscription, or per-alert price to add or run this bot.

• Do you have a public Privacy Policy? → Yes
• Where is it available? → Official Nefarious website (nefarious.trading) and this application’s Discord profile.
• Link → https://www.nefarious.trading/legal/drippy-alerts/privacy

Message Content is required because this app is a relay, not a welcome or leveling bot.

- The source alert is an ordinary Discord message: ticker text, optional embeds (fills, charts), and image attachments. Discord does not deliver that payload to a bot without the Message Content privileged intent.
- The bot copies that payload into destination servers so members there see the same Drippy analyst alert quickly. Without the text and attachments, there is nothing to forward.
- The bot does not scan unrelated channels for auto-moderation, XP, starboards, or keyword automations.

Without this intent the relay cannot function. We are not applying for Server Members or Presence.

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

Yes. Yes. The bot only reads the operator-configured source alert channel (and only so it can forward those alerts). People who are not posting in that channel are not scanned. An analyst opts out by not posting there; a destination server opts out by removing the bot or the destination webhook.

Are you storing message content data off-platform?

Yes.

Yes, in two limited ways: (1) the bot copies the source message into destination Discord channels or webhooks — those copies live on Discord in the destination servers; (2) the CryptoCalls config manager stores routing configuration (bot token, source and destination channel or webhook IDs, and a delivery cursor such as last-seen message IDs). We do not use relayed text to train machine-learning or AI models, and we do not sell it.

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

No.

Leave both boxes unchecked. If a reviewer asks why you are not applying: the bot does not welcome members, assign roles, track invites, or read online / streaming status. Relaying a public alert is a message-copy job.

• Presence opt-out field: N/A — we are not applying for Presence
• Store presence off-platform: No — we do not collect presence

• Storing any API Data off-platform? → Yes
• Storing API Data for 30 days or less? → No
• Deletion contact → Business@nefarious.trading

Routing config and destination copies persist until an operator deletes the mapping, removes the bot, or deletes the destination messages. That is typically longer than 30 days.

Discord requires encryption at rest if you store API Data. Select Yes only if the operator host, any CryptoCalls host, and any local token files are actually encrypted. Do not check Yes if tokens sit in plaintext on disk.

Drippy Alerts uses the same CryptoCalls relay as the other analyst bots. The drippy-alerts channel is in the Nefarious dump (id 1520964590853165086). The only message in that dump through August 2026 is a subscribe / role instruction, not a reconstructed trade card — so the mockup below shows the relay layout with that attested room text, not a filled ticker ticket.

• https://discord.com/channels/909011353342181426/1520964590853165086
• https://discord.com/channels/909011353342181426/1520964590853165086/1520966583013474355
• https://www.nefarious.trading/legal/drippy-alerts/intents
• https://crypto-calls.vercel.app/dashboard

Application ID is not in this workspace’s env files. Copy it from the Developer Portal into the install URL https://discord.com/oauth2/authorize?client_id=CLIENT_ID&scope=bot+applications.commands before you set Discord’s required install link. Questions: Business@nefarious.trading.