Legal · Discord apps
Nefarious Success Privacy Policy
Effective September 12, 2026 · Last updated September 19, 2026
This policy explains how Nefarious Digital, operating as Nefarious, handles information through Nefarious Success (application ID 966614821174915092). Privacy, access and deletion requests: Business@nefarious.trading.
This bot publishes content to a public X account. Discord and X also process information under their own policies. Our website privacy policy covers the website separately.
01Verified storage and retention status
Bot storage checked September 19, 2026. The inspected bot's persistent data is stored without encryption at rest.
The bot's logs have no configured size or file-count limits. No automatic expiry was established for those logs. Do not select “Yes” for encryption of all stored API data or promise a 30-day deletion limit on the basis of this page.
The retention and deletion rules below describe each data category. A removal request must also address logs and backups containing the requested data. Storage migration, bounded logs and a verified deletion procedure remain required operational work.
02When the bot processes information
The repost feature is limited to the configured success channel. A supported image triggers publication and a leaderboard point. Messages without supported image attachments do not create X posts.
The command handler checks messages Discord delivers to the bot for !sp, !scl, !sclm, !sclw, !scly. That can include other channels the bot can access and direct messages sent to it. Server permissions determine channel access. The bot does not access conversations between other users in their private DMs.
To avoid new reposts, do not post image attachments in the success channel. Not using the commands avoids requesting points or leaderboards; it does not itself erase existing records or stop all event delivery. Contact Business@nefarious.trading to request deletion.
03Information used and stored
- Success content. Image attachment filename, type and URL; downloaded image bytes; optional message caption; and the author’s Discord display name. The first supported image is uploaded to X with the caption and a line identifying the display name. No separate local media archive or message-body file is created by the repost code. Delivered messages may also be cached temporarily in memory by the Discord library.
- Leaderboard records. Discord user ID, display name, and earned-point entries containing a timestamp and X post ID. These are stored on the bot host and used for personal totals and all-time, weekly, monthly and yearly rankings. A shorter leaderboard window filters existing entries; it does not delete older entries.
- Delivery and deletion metadata. Configured channel ID, processed Discord message IDs used to prevent duplicate reposting, and an in-memory relationship between a bot reply, its X post, the original author and the original message.
- Reactions and permissions. Reaction emoji, reacting user ID and, when needed, member roles and administrator permissions to check whether a deletion request comes from the author, an administrator or a designated moderator. This individual member lookup does not build a server member directory.
- Operational logs. The process outputs usernames, channel/message/media IDs, X post URLs and errors for troubleshooting. Error messages may include details returned by Discord or X. The runtime code does not set a host-log retention period.
- Support requests. Information you send to the contact address, including your reply address and the identifiers needed to locate a record or verify a deletion request.
04Purposes
- Publish success images and captions to the public X account and return a link in Discord.
- Award and display leaderboard points, calculate ranks, and correct records.
- Prevent duplicate reposts, check deletion permissions, investigate failures and respond to support requests.
The bot does not implement AI training, advertising profiles, sale of personal data, presence monitoring or collection of members’ brokerage credentials. Do not put financial account identifiers or other sensitive information in a screenshot or caption. The bot does not redact them before publication.
06Retention and deletion
- Points and identifiers. The current bot has no automatic expiry for account rows, earned-point entries or processed-message markers. They can remain beyond 30 days and require operator action for full erasure. Removing one earned point does not remove the user ID/name record or processed-message marker.
- X posts. No automatic expiry is configured. Posts remain until deleted through the bot, the operator’s X account or X itself. Deleting your original Discord message or leaving the server does not automatically delete its X repost or points.
- Reaction deletion. A trash reaction on the bot reply requests X deletion and point removal, followed by deletion of the bot reply and original Discord message. It is available to the original author, administrators and designated moderators while the bot has the mapping. That mapping is lost on restart. API failures or missing Discord permissions can leave a request partly completed.
- Transient data and logs. Image handling and reply-to-post mappings use process memory. The application does not define a fixed expiry for host logs or backups; a request should identify those copies for operator review as well.
For complete deletion or an old post whose trash reaction no longer works, email Business@nefarious.trading with your Discord user ID, relevant message links and X post links. We may ask you to confirm control of your Discord account. Tell us whether you want the public repost, leaderboard record, or both removed. Do not send passwords, tokens or brokerage credentials.
We handle verified requests under applicable law, including any required response deadlines and lawful retention exceptions. Discord, X and third parties control their own copies; we can remove only records and posts under our control.
07Security
The bot communicates with Discord and X using their encrypted network endpoints. Leaderboard and deduplication records are stored on the operator’s host. The application itself does not encrypt those files; protection at rest depends on the hosting configuration. This policy does not claim that disk encryption, backup encryption or a particular log-expiry schedule has been verified.
Public reposts are intentionally visible to others. The bot does not review or blur screenshots before upload. Report a suspected exposure to Business@nefarious.trading so the operator can investigate and make required notifications.
08Your choices and rights
Depending on applicable law, you may have rights to access, correct, erase or obtain a copy of personal data, object to or restrict processing, withdraw consent where processing relies on consent, and complain to a privacy regulator. Contact Business@nefarious.trading to exercise those rights or ask about the legal basis for a particular use. Declining future reposts does not require giving up a deletion request.
This bot serves an adult trading community and is intended for people 18 or older. If information from a child has been processed, contact us to request its removal.
09Discord access
The bot uses Message Content for ordinary server-image reposts and prefix commands. It does not enable the privileged Server Members or Presence intents. See the intent explanation for the distinction between Gateway events, individual member permission checks and ordinary server permissions.
10Changes and contact
We update this page and its revision date when practices change. A policy update does not itself obtain permission for a new use of personal information. Questions or requests: Business@nefarious.trading.
Also see our Terms of Service, Privileged intents, and Site Privacy Policy.