Nefarious
← All bots

Discord applications · Review material

Wex Alerts intent review

Effective September 12, 2026 · Last updated September 19, 2026

Message Content: needed if this application reads the ordinary source messages. Server Members: no. Presence: no.

Match the application ID before submitting: 1511597709834977320. These drafts describe the operator’s relay workflow and the linked evidence. They do not certify uninspected hosting or storage settings.

01Application purpose

Suggested answer
Wex Alerts relays authorized OneTradeWex analyst messages to configured Discord destinations. An analyst submits an ordinary message; the relay prepares a branded embed and delivers its text and available attachments, with configured role mentions. The verified sender examples include previews with send and edit controls; they should not be described as unconditional automatic broadcasting. This gives destination members the same update without requiring the analyst to repeat it in every server. The operator identifies CryptoCalls as the configuration dashboard. Current source/destination routing and host behavior must be checked for this exact application.

02Bot, analyst and authorized user

Suggested answer
Application/bot ID: 1511597709834977320. Attached analyst: $OneTradeWex, Discord user ID 1235358794146381877. Sender channel: #wex-sender (1509024131910471680). The recorded send interaction was accepted for $OneTradeWex (1235358794146381877). The recorded component interaction was accepted for this user. The complete configured allowlist and rejection of unauthorized users have not been inspected.

03Why Message Content is needed

Suggested answer
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.

04Policy links

Privacy Policy URL
https://www.nefarious.trading/legal/wex-alerts/privacy
Terms of Service URL
https://www.nefarious.trading/legal/wex-alerts/terms

05Data handling and retention

Message-content opt-out: Administrators can revoke source access, disable a route or remove the bot/webhook. Contributors can request exclusion through support. A working automatic per-user opt-out has not been verified; do not answer Yes solely because someone can avoid posting.

Discord destination messages are on-platform copies. Payloads are processed on the relay host; durable content logging, caching and backup behavior for the deployed relay must be checked before selecting Yes or No for off-platform message-content storage. Routing IDs and delivery state are a separate API-data category.

Routing and delivery records may remain while the service operates. No uniform automatic 30-day expiry has been verified. Disclose the actual retention of logs, caches and backups; do not promise a shorter period without implementing it.

Encryption at rest has not been verified for the deployed relay’s storage or backups.

AI training: No. Discord data is not used to train machine-learning or AI models. Deletion contact: Business@nefarious.trading.

06Verified examples and evidence limits

View this bot’s evidence →

Also see our Wex Alerts, Terms of Service, Privacy Policy, and Intent review.