JCACTrades Radio (Crypto) intent review

JCACTrades Radio (Crypto) relays authorized JCAC analyst messages to configured Discord destinations. This application covers crypto updates and is separate from the JCAC Forex application 1138015704898093097. In the operator-described workflow, an analyst submits an ordinary message for relaying as a branded embed with available attachments and configured mentions. The retrieved evidence verifies a delivered message only. Any illustrated sender, preview or send control is a reconstruction, not a captured source message or accepted send interaction. This gives destination members the same update without requiring the analyst to repeat it in every server. The routing provider and deployed runtime have not been independently verified. Current source/destination routing and host behavior must be checked for this exact application.

Application/bot ID: 1021946613482143764. Attached analyst: JCAC / wafaduck, Discord user ID 268669647455387648. Original sender channel not verified. No accepted send interaction was retrieved. The operator identifies JCAC / wafaduck, user 268669647455387648, as the authorized analyst. Discord profile lookup confirms username jcactrades. A configured allowlist, original sender message and accepted send interaction were not retrieved; those controls are not independently verified.

The described relay reads ordinary source messages, including their text, embeds and attachments, to prepare and deliver the analyst update. Those fields are restricted by Message Content across Gateway and REST responses, except for Discord's documented exceptions. The source message generally does not mention this bot.

The intended workflow handles analyst messages as they are submitted, rather than requiring a separate interaction for every destination. A message-context or attachment slash command is a possible redesign and should be evaluated; we do not claim migration is technically impossible. The evidence distinguishes retrieved source messages, bot previews, delivery reports and destination messages. Output alone cannot establish which application reads the source. Server Members and Presence are unnecessary for the described relay function.

https://www.nefarious.trading/legal/jcac-crypto/privacy

https://www.nefarious.trading/legal/jcac-crypto/terms