Legal / Discord application review
Enick's Bot privileged intents
Effective September 15, 2026 · Last updated September 15, 2026
Request Message Content for the operator-described source-message relay. Real bot-authored messages verify outgoing alerts; they do not independently prove the live client configuration, retention settings or which process reads the source.
01Recommended intents
- Message Content: request for the source reader. The described relay reads ordinary analyst messages, including their text, embeds and attachments, before forwarding them. Message Content is needed for source messages that do not mention the app. Sending messages alone does not need this intent.
- Server Members: not required. Forwarding channel messages does not require a member roster, member-join events or role synchronization.
- Presence: not required. Forwarding alerts does not depend on online status, activities or streaming presence.
02What does your application do?
Enick's Bot forwards Enick's analyst alerts from configured Discord source channels to selected destination channels and servers. Operators configure the relay through the CryptoCalls workflow. Recipients receive the alert text and available embeds or images without the analyst manually reposting each update. This application is identified by bot user ID 899173979728773140 and is separate from Enick utility bot. Real bot-authored examples and their original Discord links are available on our intents page.
03Why Message Content?
Our relay workflow reads ordinary analyst posts in configured source channels and forwards their text, embeds and attachments to selected destinations. These posts are not necessarily commands or messages mentioning the app. Message Content provides the content fields needed to reproduce those alerts. Slash commands would require the analyst to submit each existing post again and would change this workflow. The intent is needed by the source-message reader; it is not needed merely to publish outgoing alerts. Server Members and Presence are not required for this relay function.
Ordinary Gateway subscriptions such as Guilds and Guild Messages are separate from privileged approval. Read Message History, Send Messages, Embed Links and Attach Files are channel permissions; grant only those the deployed relay actually needs.
04Public policy URLs
Privacy Policy: https://www.nefarious.trading/legal/enick-bot/privacy Terms of Service: https://www.nefarious.trading/legal/enick-bot/terms
05Opt-out and deletion
Email Business@nefarious.trading with the channel or message link. Server administrators can remove the app or its source-channel access. No automatic per-user opt-out command has been verified; deleting a source post may not remove existing forwarded copies.
06Confirm storage fields before submission
The relay processes content outside Discord to forward it, and destination messages remain in Discord. Persistent message storage, caches, logs, backups and CryptoCalls retention have not been independently verified. Do not answer No solely because the final message appears in Discord.
Verify actual routing records, message caches, logs and backup expiry before selecting a retention answer. A fixed deletion deadline has not been established by this review.
Confirm encryption for each actual store and backup before answering this field.
07Real message evidence
Also see our Privacy Policy, Terms, and All-bot intents.