Enju Privacy Policy
This Privacy Policy describes information Enju processes when you use the Enju Discord bot, website, dashboard, reaction-image features, public API, and related administrative tools; why that information is used; and how you can request deletion or correction.
1. Information Enju May Process
Depending on the features you use, Enju may process Discord-provided identifiers and account or server information necessary to operate the Service, including Discord user IDs, guild/server IDs, channel IDs, usernames or display information, guild membership and permission information, and OAuth information used to authenticate dashboard sessions.
Enju may also process feature-specific data such as server configuration, command settings, XP and leveling records, virtual currency balances, reputation data, greeting and goodbye settings, scheduled commands or messages, expressions, announcements, moderation settings, role or channel configuration, and other records created through use of Enju.
2. Reaction Images and User-Submitted Content
When you submit a reaction image or other content, Enju may process the uploaded file, reaction category, Discord user ID of the submitter, submission time, review status, moderation notes or reasons, image metadata needed to store or serve the file, and related approval, rejection, removal, or history records.
Approved reaction images may be made publicly available through Enju’s reaction-image features, public gallery, or public API. Do not submit an image if you do not want an approved version to be publicly accessible through those features.
3. Submission Blacklist and Moderation Records
To manage abuse of the reaction-image submission system, Enju may maintain a submission-specific moderation list containing a Discord user ID, moderation reason, optional private owner note, the Discord user ID of the administrator who added or changed the entry, timestamps, expiration information for temporary restrictions, and moderation history such as prior reasons or changes.
These records are used to determine whether new reaction-image submissions should be accepted and to preserve moderation accountability. A submission restriction is separate from a general ban from unrelated Enju features unless another restriction also applies.
4. Commands, Expressions, Analytics, and Operational Records
Enju may collect operational analytics needed to administer, secure, diagnose, and improve the Service. Depending on the feature, these records may include command names, execution status, blocked or failed execution events, duration or latency, module information, timestamps, server context, Global Expression identifiers or triggers, usage counts, unique-server reach, last-used server or channel identifiers, and similar operational statistics.
Enju may also maintain owner or administrator audit records for actions performed through protected dashboard tools. Audit records may include the acting Discord user ID, action name, success or failure status, timestamp, notes, and limited technical details about the action.
Unless a feature specifically requires storing message or response content, operational analytics are intended to record metadata about use and performance rather than create a general archive of private Discord conversations.
5. Network, Security, and Rate-Limit Information
Enju may process network and security information such as IP addresses, request timing, request paths, headers needed for secure proxy operation, rate-limit counters, authentication state, error information, and security events when reasonably necessary to protect the Service, prevent abuse, troubleshoot requests, or enforce rate limits.
6. How Information Is Used
Information is used to provide Enju features, authenticate users, determine whether a user is authorized to manage a Discord server, deliver bot and dashboard functionality, store requested configuration, moderate user submissions, operate reaction-image and API features, enforce restrictions and rate limits, generate diagnostics, maintain auditability, troubleshoot failures, secure the Service, perform backups or recovery, and comply with applicable legal or platform requirements.
7. Dashboard Authentication and Sessions
The Enju dashboard uses Discord OAuth to identify the signed-in Discord account and obtain the guild information required for dashboard functionality. Authentication or session cookies may be used to keep you signed in and protect access to dashboard functions.
8. Public and Administrative Information
Some Enju information is intentionally public, such as approved reaction images served through public endpoints or gallery pages. Other information is intended for authorized administration only, including private moderation notes, submission-blacklist history, owner audit logs, protected diagnostics, and recovery controls.
Diagnostic or recovery exports should be treated as administrative files. Enju is designed not to intentionally include bridge keys, host-helper keys, passwords, or similar secrets in owner diagnostics bundles, but administrators should still review and protect exported files before sharing them.
9. Information Sharing and Service Providers
Enju does not sell personal information. Information may be transmitted to Discord as necessary to provide Discord-integrated functionality. Information may also be processed by hosting, networking, security, content-delivery, storage, or other infrastructure providers when reasonably necessary to operate or protect Enju, or disclosed when required by law.
Third-party infrastructure providers may independently process connection or security information under their own privacy practices.
10. Data Retention
Information is retained for as long as reasonably necessary to provide Enju’s functionality, maintain security and integrity, preserve legitimate moderation and audit history, operate backups or recovery, meet legal obligations, or resolve disputes. Different categories of data may have different retention periods.
Approved public reaction images may remain available until removed through Enju’s moderation or administrative processes. Moderation or audit records may be retained after related content is removed when reasonably necessary for abuse prevention, security, accountability, or dispute resolution.
11. Data Deletion and Correction Requests
You may request deletion or correction of data associated with you by contacting Enju through the Support page. Please provide enough information to identify the relevant Discord account, server, submission, or record. Additional verification may be required to prevent unauthorized deletion or modification of another person’s data.
Some information may be retained when reasonably necessary for security, abuse prevention, legal compliance, dispute resolution, backup integrity, or legitimate moderation history. Where appropriate, information may instead be anonymized or detached from an identifiable account.
12. Security
Reasonable technical and administrative safeguards are used to protect information processed by Enju, including access controls for owner-only and server-management functions. No internet-connected service can guarantee absolute security.
13. Children
Enju is intended for users who are permitted to use Discord under Discord’s requirements and applicable law. Enju is not intended to independently collect personal information from children outside the operation of Discord-integrated functionality.
14. Third-Party Services
Discord and other third-party services used with Enju maintain their own privacy practices. This Privacy Policy applies to Enju’s processing and does not replace the privacy policies of those services.
15. Changes to This Policy
This Privacy Policy may be updated when Enju’s functionality, moderation systems, analytics, infrastructure, data practices, legal obligations, or platform requirements change. The current version and updated date will be posted on this page.
16. Contact
For privacy questions, correction requests, deletion requests, or questions about a reaction-image moderation record, use the Enju Support page.