Discord applications · Review material
Dingus 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: 1537411077900603404. These drafts describe the operator’s relay workflow and the linked evidence. They do not certify uninspected hosting or storage settings.
On this page · 7 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.
Dingus Alerts 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.
02Application purpose
#Dingus Alerts relays authorized Dingus 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.
04Why Message Content is needed
#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.
05Policy links
#https://www.nefarious.trading/legal/dingus-alerts/privacy
https://www.nefarious.trading/legal/dingus-alerts/terms
06Data 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.