Discord application · Evidence
Drippy Alerts evidence
Effective September 19, 2026 · Last updated September 19, 2026
Inspect this bot’s workflow, identity and supporting records. Each example distinguishes retrieved messages, observed operation and illustrations.
01Workflow and supporting records
Bot identity and authorized use
- Discord bot
- Drippy Alerts
1511591818901459035 - Attached analyst / source author
- drippy
911357687491620924 - Sender channel
- #drippy-sender
1509023850875060244 - Authorized user observed using Send
- teever
262674782171037698
The recorded component interaction was accepted for this user. The complete configured allowlist and rejection of unauthorized users have not been inspected.
Verified message records · 2026-09-19
Message Content lets the relay read the analyst’s original message and attachments before delivering it to configured channels. Sending the bot’s own output does not itself require that intent.
Source, preview and receipt were retrieved read-only through the bot on September 19, 2026. Reply references and component-interaction metadata connect the workflow. A destination message was not separately retrieved; the receipt is a bot-reported result, not independent delivery verification. Drippy submitted the source; teever clicked send. The preview differs from the source text, demonstrating an edited preview; no edit interaction was retrieved. The receipt reports delivery to drippy-sender, not cross-server distribution.
Reconstructed from real Discord messages, with the original text, timestamps and available images, except for explicitly labeled redactions. Layout is simplified; decorative or unavailable media may be omitted. These are website renderings, not screenshots of the Discord client. Source links require access to the channel.
Watch the workflow
Reconstruction from real records · illustrative typing and timing · no live messages
#drippy-sender · drippy
Illustrative composition of the recorded source message
The saved Discord record proves the sent message, not the original keystrokes.
Inspect all 3 original message records
DrippyDrippy | Funding Predicts
Recorded controls, disabled in this reconstruction.
DrippySent with role mention!
Drippy | Funding Predicts
02Public evidence and removal
These selected examples are public, including any displayed Discord IDs, messages, timestamps, avatars, media and aggregate operational results. Visitors do not need access to the original channel. Credentials, private trading account details and raw message archives are excluded.
Evidence files and deployment copies have no automatic 30-day expiry. Email Business@nefarious.trading with this bot’s name and the relevant example to request correction or removal. Removal must address active pages, downloads, cached media and retained copies under our control. Evidence is not used to train AI models.