Nefarious Backup Privacy Policy

The bot collects history from configured Nefarious text channels it can access. Collection can include messages posted before the latest backup run. Some channels and categories are excluded; these exclusions do not erase previously saved data.

The bot does not back up direct-message history or voice audio. It can receive messages directed to it, including operator commands; command access is controlled by a user-ID allowlist. It does not use presence or online activities for backup.

• Message text, message and channel IDs, creation and edit timestamps, pinned status, and embed payloads such as titles, descriptions, links and fields.
• Author Discord ID, username, display name, bot flag and avatar URL, including historical author information captured at collection time.
• Supported photo/video filenames and URLs, and downloaded files within the configured size limit. Downloaded media must match supported actual file types; unsupported files are skipped and their filenames may be recorded.
• Guild and channel names and identifiers; role definitions, including names, colors and permissions; banned user IDs, usernames and recorded ban reasons.
• Available member rows. Complete member enumeration is currently disabled. The current fallback derives author IDs, usernames and possible nicknames from saved messages and has no member role assignments. If complete member backup is enabled, records include nickname and assigned role IDs for members with a nickname or non-default roles.
• Operational mappings, webhook identifiers, last-copied message IDs, run times, counts, failure reports and command/request information needed to operate the service and respond to requests.

We use the records for disaster recovery, resuming interrupted backups, operator review of backup failures, restoring supported data to the backup server, and handling privacy or abuse reports. We do not sell this information or use message content for advertising, profiling or AI model training.

Ordinary message history requires Message Content access. Complete member enumeration would additionally require Server Members. Presence is unnecessary. The intent explanation describes the enabled and optional features.

Messages can contain personal or sensitive information provided by their authors. Do not post credentials, account secrets or other sensitive records in channels that are backed up.

Operator-controlled storage holds the historical database, JSON exports, downloaded supported media, snapshots and operational records. A separate backup Discord server holds webhook copies that can show the original author’s display name and avatar. Mention delivery is disabled when reposting.

Access is intended for authorized operators and recovery administration. Anyone granted access to a destination channel can view copies in that channel. Operators must maintain appropriate storage and destination-server permissions; the bot itself does not establish a guarantee of confidentiality.

Discord processes the source and destination messages under its Privacy Policy. Hosting providers or people administering our infrastructure may process stored records where necessary to operate the service. We may disclose information where legally required or to address a substantiated security or abuse incident.

• Historical archive: the database and recovery exports have no automated age-based expiry. They may retain messages older than 30 days, including years-old source history, until operators remove them.
• Successful snapshots: rotation is configured to keep the latest four successful snapshots. Runs are scheduled daily and can also be started manually. This is a count of completed copies, not a four-week retention period or a limit on the age of messages inside them.
• Partial and legacy copies: incomplete snapshots and migration copies are not covered by the successful-snapshot rotation and require separate operator handling.
• Limited channels: selected high-volume scans use a 250-message window, but the current recovery setting preserves existing archive history instead of pruning older stored rows. Historical snapshots can also contain earlier messages.
• Backup Discord and operational records: these remain until removed by operators or otherwise deleted through the relevant service. The mirror is not automatically wiped weekly.

Email Business@nefarious.trading with your Discord user ID and relevant message links, channel names or approximate dates. Do not send your Discord password or token. We may ask for reasonable information to verify that the request concerns you.

There is no automated per-user opt-out or deletion command. Requests require manual review across the archive database, exports, image files, successful and incomplete snapshots, legacy copies and backup Discord messages. We will respond to applicable requests and explain any verified limitations or legally required retention.

Source edits and deletions are not automatically applied to existing copies. Leaving the server does not erase earlier records. Preventing a removed record from being collected again also requires addressing accessible source history or restricting the relevant collection. Channel exclusions affect future collection and do not by themselves erase historical copies.

You may request access, correction, deletion or a restriction on processing, and any other rights available under applicable law. Where applicable, you may contact your privacy regulator. This policy does not limit statutory rights or require you to give up privacy rights to remain in the community.

Backup and restore commands, including /backup interactions, are restricted to allow-listed user IDs in the configured source or backup guild. Load/setup/cleanup require explicit confirmation. The Archive this message action stores the selected record and attachment links without advancing the history cursor; it does not download the referenced files or constitute a complete channel backup. Storage access and destination Discord permissions require separate administration. No online service or storage system can promise absolute security.

The application writes ordinary database, JSON and image files. The primary archive and current snapshots use encrypted bot storage. Legacy copies and container logs remain unencrypted; encryption does not cover all retained data. Report suspected unauthorized access or a privacy issue to Business@nefarious.trading.

The service is not directed to children below Discord’s minimum age or a higher minimum required by applicable law. Contact Business@nefarious.trading if you believe records relating to an ineligible child were collected.

Updates will be published at this address with a revised date. Material changes to collection, use or retention will be described here. Questions, privacy requests and abuse reports: Business@nefarious.trading.