Nefarious Success Privacy Policy

With Message Content available, the bot detects eligible image attachments in the configured success channel, ignores bot authors and creates a preview. An author-confirmed X post earns one point. Without that access, members can use /success with an image and caption or the Submit success message action on their own channel message. Both require confirmation before X upload.

Available interactions: /success, Submit success (message action), /success_delete, /sp, /leaderboard, /scl, /sclm, /sclw, /scly. Publication and deletion commands are restricted to the configured success channel. Points and leaderboard interactions can be used elsewhere in the configured server. Existing prefix commands (!sp, !scl, !sclm, !sclw, !scly) may process delivered messages in other accessible channels and DMs while Message Content is available. The bot cannot access private conversations between other users.

No persistent per-user exclusion from automatic preview processing is implemented. Declining publication is different from stopping all processing. Administrators can restrict the bot's access; contact Business@nefarious.trading for broader requests.

• Content. Attachment filename, size, type and URL; image bytes; optional caption; and author display name. Content is processed in memory for previews and delivery. The code does not create a separate local body or image archive. The Discord library may temporarily cache messages. Confirmation views expire after ten minutes; that timeout does not erase Discord messages or other platform copies.
• Points. Discord user IDs, display names, point timestamps and X post IDs support totals and rankings. Monthly or weekly filtering does not delete older point entries.
• Delivery and deletion records. Processed source IDs and, for new confirmed posts, a persistent relationship between the source or interaction, author, channel, X post and Discord receipt. This prevents duplicates and supports deletion after a restart. Failed or uncertain external requests may leave a claim pending for operator reconciliation.
• Permissions. Interaction or reaction user IDs, roles and administrator permissions are checked for author/moderator deletion. Individual member lookups do not create a server-member directory.
• Operations and support. Connection information, configured channel identifiers, error categories and platform responses may appear in logs. Earlier logs may contain usernames, message/media IDs and post links. Support requests contain the information you provide to identify records and verify your request.

We process these records to prepare previews, publish confirmed contributions, award points, show rankings, prevent duplicate delivery, verify deletion authority and resolve failures. The bot does not train AI models, build advertising profiles, sell Discord API data or monitor presence.

• X and public viewers. Confirmation sends your image, caption and display name to the public X account. Other people may copy or redistribute the post. Deletion cannot recall copies held by others.
• Discord viewers. Normal-message previews, receipts and leaderboards are visible where posted. Slash and context previews are private to the invoking user. A confirmed /success submission also publishes its image and caption in the success channel.
• Operators and infrastructure. Authorized operators and hosting providers process the information needed to run the service, maintain records and respond to support or lawful requests.

See Discord's Privacy Policy and X's Privacy Policy. These platforms may process information internationally. The bot does not redact screenshots; remove account numbers and other sensitive details before sharing.

• No automatic 30-day expiry. Points, account rows, dedup markers and post mappings may remain longer than 30 days. No scheduled purge of these records is implemented. Public X posts remain until removed.
• Delete a new X post. The author, an administrator or a configured moderator can use /success_delete with the post ID, or the trash reaction on a mapped receipt. The bot attempts to remove the X post and its point and delete the receipt. The original Discord message remains under its author's control. API errors or missing permissions can cause partial completion.
• Restart support and older posts. New mappings are retained on disk. Posts created before the mapping update may still require operator assistance. Deleting a source message or leaving Discord does not automatically remove its X post or points.
• Full erasure. Deleting a post does not erase its user row, dedup marker or retained mapping. Contact support for a broader request covering these records, backups, historical snapshots and logs. A complete erase-all-user-data command is not implemented.

Email Business@nefarious.trading with your Discord user ID and relevant message/X links, identifying whether you want the post, leaderboard data or all applicable records removed. We may verify account control. Do not send credentials. We handle verified requests under applicable law, including response deadlines and lawful retention exceptions; third-party copies remain subject to their operators.

Selected historical messages, IDs, timestamps, avatars and media may appear on the public evidence page. They can be viewed without joining Discord and have no automatic 30-day expiry. Contact Business@nefarious.trading for correction or removal from pages, downloads and retained copies under our control. Evidence is not used to train AI models.

Discord and X API connections use encrypted transport. On October 26, active points, dedup records, new post mappings and runtime configuration were copied to a verified encrypted host dataset. Original plaintext stack copies, unencrypted Docker logs and historical shared snapshots remain. This policy does not certify that every retained copy is encrypted.

Public reposts and demonstrations are intentionally visible. The bot does not review or blur screenshots. Report suspected exposure to Business@nefarious.trading so the operator can investigate and make required notifications.

Depending on applicable law, you may have rights to access, correct, erase or obtain a copy of your information, restrict or object to processing, withdraw consent where applicable, and complain to a privacy regulator. Contact Business@nefarious.trading to exercise those rights or ask about the basis for processing. Declining future publication does not affect your ability to request deletion.

This bot serves an adult trading community and is intended for people 18 or older. Contact us if a child's information has been processed.

We update this page when practices change. An updated policy does not itself obtain permission for a new use. Questions or requests: Business@nefarious.trading. The intent explanation describes the ordinary-message workflow and interaction fallback.