Discord applications · Privacy Policy
Enick utility bot Privacy Policy
Effective September 12, 2026 · Last updated September 15, 2026
Application identity pending. This policy covers the operator-described relay. Its exact application ID, active routing and deployed storage practices still require verification; it is not an attestation that a working bot was observed.
Nefarious Digital operates Enick utility bot. This policy explains the data used to deliver Enick alerts and how to request access, correction or deletion. Contact Business@nefarious.trading.
A source channel can be restricted to an analyst or staff. A destination can have a different audience. Do not assume that posting in a source channel keeps the content within that channel.
01Information used by the relay
- Message text, embeds, images and other attachments selected for relaying, including any personal information in that material.
- Discord author identifiers and available display names or avatars used for attribution; message, server, channel and role identifiers; timestamps and configured mentions.
- Routing configuration, delivery state and operational records needed to send alerts, diagnose failures and respond to support requests.
- Information you send directly to our support contact, including the message links needed to locate copies.
02Purpose and recipients
We use this information to operate the requested relay, attribute messages, prevent duplicate delivery, resolve failures and handle rights requests. Content is sent to Discord and becomes visible to people with access to each configured destination. Authorized operators and hosting or configuration providers process the information needed to operate the service. Routing is managed through the CryptoCalls service identified by the operator.
We do not sell Discord API data, disclose it to advertising networks or data brokers, or use message content to train AI or machine-learning models. Processing and storage can occur outside your country. Discord and any linked external sites also have their own privacy policies.
03Access and your choices
The described relay feature requires Message Content for ordinary source messages. It does not require a full member list or presence updates. Access should be limited to the channels needed for its operation. A role mention in an alert does not mean the relay needs to enumerate everyone with that role.
Ask the operator to stop forwarding your contributions or remove a route. Server administrators can revoke channel access or remove the bot or webhook. We do not promise an automatic per-user exclusion command: support-assisted exclusion and deletion depend on the active routing configuration. Stopping use does not itself delete older copies.
04Storage and retention
Messages delivered to Discord remain there until deleted under the destination’s settings and Discord’s policies. These are on-platform copies. The service also processes payloads on its host and keeps routing and delivery records off-platform.
No uniform 30-day deletion schedule has been verified for the deployed relay services. Routing records can remain while a route operates, and copies or operational records may persist until removed. Contact us for the records associated with your message or account. We will remove personal data we control when it is no longer needed or when a valid deletion request requires it, subject to applicable legal obligations.
Source deletion may not propagate to all destinations. We cannot erase independent screenshots or copies held by third parties, but we can identify destinations we operate and act on reachable copies.
05Security and service providers
Access to routing credentials and operational records must be restricted to authorized operators. Do not send bot tokens, account passwords or financial account credentials through relay messages or support requests. A public policy is not a security certification. If unauthorized access to Discord API data occurs, we will notify Discord and affected people as required by Discord’s terms and applicable law.
06Access, correction and deletion
Email Business@nefarious.trading with the bot name, your Discord user ID where relevant, and the source or destination message link. State whether you want a copy, correction, deletion or future forwarding stopped. We may ask for proportionate verification of your connection to the record, but never your Discord password or token.
We will respond within the period required by applicable law. Depending on your location, you may also have rights to object, restrict processing, receive a portable copy, withdraw consent or complain to a privacy regulator. We do not discriminate against people for exercising privacy rights. Where required, processing relies on providing a requested service, consent for optional redistribution, legitimate operational interests or legal obligations, as appropriate to the activity.
07Children and policy updates
The relay is not directed at people below Discord’s minimum age or the higher minimum required by local law. Contact us if a message includes their data. Material changes will be reflected here with an updated date and appropriate notice.
Also see our Enick utility bot, Terms of Service, Privacy Policy, and Intent review.