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.
On this page · 8 sections
01Reconsideration and fallback functionality
#Prepared October 26, 2026. Message Content only, for the configured ordinary-message source reader. This is review material, not a submission receipt or approval.
Enick's Bot distributes an analyst's existing Discord update to configured destinations. The source is an ordinary message, potentially containing formatted text, embeds and attached charts. The requested access is for reading that source to prepare the preview, not for sending the outgoing message or setting a role mention. A later send button supplies the selected interaction, not the protected content of an unrelated earlier source message. Without access to that source, the current application cannot construct the same preview from the original post. The operator's intended experience is to write the update once in the normal analyst channel and review the prepared distribution. Asking the analyst to submit or select every post separately introduces another step between the channel conversation and the preview. For follow-up updates, the operational concern is missing an update or manually re-entering content differently across channels. These are workflow risks described by the operator, not measured latency or error-rate claims. Alternatives considered An attachment/text slash command or message-context command can implement a manual submission path and should remain available as a fallback. They supply only the deliberately submitted or selected message; they do not observe every ordinary source-channel post. Mentions and DMs similarly require changing how the source is addressed. We acknowledge that an interaction-based redesign is technically possible. The request is to retain automatic source detection within the authorized source scope while keeping operator send controls.
Continuity while access is reviewed
Provider-managed relay source is not available in the inspected local projects. Command/context fallback deployment for this exact application has not been verified.
Use only evidence tied to this application ID. Confirm its source-reader identity, channel/author authorization, provider and actual data practices. A delivered embed alone does not establish which app read the source. Approval is not implied by another analyst app being approved.
02Recommended 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.
03What 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.
04Why 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.
05Public policy URLs
#Privacy Policy: https://www.nefarious.trading/legal/enick-bot/privacy Terms of Service: https://www.nefarious.trading/legal/enick-bot/terms
06Opt-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.
07Confirm 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.