Premier Utils — Privacy Policy

Last Updated: January 29, 2026

This Privacy Policy explains how Premier Utils (the “Bot”) collects, uses, discloses, and retains information when you interact with the Bot or related services (collectively, the “Services”). “We,” “us,” and “our” refer to the operator(s) of Premier Utils.

By using the Services, you acknowledge this Privacy Policy. If you do not agree, do not use the Services.

1. Scope

This Privacy Policy applies to:

• Interactions with the Premier Utils Discord bot
• Any related dashboards, websites, support servers, documentation, and integrations that reference this Privacy Policy

This Privacy Policy does not cover Discord’s own practices. Discord is a separate platform with its own policies and controls.

2. Key Principles

• Data minimization: We aim to collect only what we need to operate features you use.
• Purpose limitation: We use data primarily to provide, secure, and improve the Services.
• Access control: We restrict internal access to operational needs.
• No sale of personal data: We do not sell personal data.

3. Definitions

• “Personal Data”: Information that identifies or can reasonably be linked to an individual (e.g., Discord user ID).
• “Server”: A Discord server (guild) where the Bot is installed.
• “Server Admin”: Server owner and/or users with administrative permissions to configure the Bot.
• “Processing”: Any operation on data (collection, storage, use, disclosure, deletion).

4. Information We Collect

4.1 Discord Identifiers and Metadata (Typical)

When you use the Bot, we may collect and process:

• User ID, Server ID, Channel ID, Role ID
• Username/display name (as provided by Discord at runtime; may not be stored)
• Message IDs, interaction IDs, timestamps
• Command usage metadata (e.g., which command was run and when)
• Bot configuration data (server-specific settings, enabled modules, prefixes, language preferences)

4.2 Content Data (Feature-Dependent)

Depending on the features enabled and how you use the Bot, we may process:

• Command content (the text of your command and parameters)
• Message content only when required for a feature (e.g., moderation filters, logging, automations)
• Attachments or links only when required for a feature (e.g., scanning a URL for an embed preview)

Important: Many bot functions can operate without storing message content. If a feature requires content retention (e.g., audit logs), retention is controlled by that feature’s design and server configuration.

4.3 Moderation and Safety Data (If Enabled)

If your server uses moderation utilities, we may store:

• Warnings, notes, infractions, timeout/mute records, ban/kick action metadata
• Reason fields entered by moderators
• Moderator ID and timestamp for traceability

4.4 Technical and Diagnostic Data

We may collect:

• Error reports, stack traces, performance metrics
• Rate-limit events and system health logs
• Basic request metadata necessary to prevent abuse (e.g., suspicious usage patterns)

4.5 Payments Data (If Premium Is Offered)

If you purchase Premium Features:

• We may store entitlement status (e.g., premium active/inactive), server/user association, and billing identifiers.
• Payment card details are not stored by us if handled by a third-party payment processor (typical). Those processors handle sensitive payment details under their own policies.

5. How We Use Information

We use information to:

1. Provide the Services

   • Execute commands and deliver responses
   • Store server configuration and preferences
   • Maintain premium entitlements (if applicable)

2. Moderation and Server Administration

   • Apply configured filters/automations
   • Record moderation actions where enabled
   • Provide audit trails for admin accountability

3. Safety, Security, and Abuse Prevention

   • Detect and mitigate spam, raids, and abusive patterns
   • Enforce rate limits and protect system integrity
   • Investigate suspicious or prohibited usage

4. Maintenance and Improvement

   • Debug issues and improve reliability
   • Analyze aggregate usage patterns to improve features (where feasible, using non-identifying or minimized data)

5. Legal and Compliance

   • Comply with lawful requests where required
   • Enforce our Terms of Service and protect rights and safety

6. Legal Bases (Where Applicable)

Depending on your jurisdiction, our processing may rely on:

• Contractual necessity (to provide the Services you request)
• Legitimate interests (security, abuse prevention, service improvement)
• Consent (where a feature explicitly requires it; servers opt in by enabling features)
• Legal obligation (compliance with applicable law)

Server admins act as controllers for certain server-level choices (e.g., enabling logging). If you are a server admin, you are responsible for ensuring your server’s use of the Bot aligns with applicable laws and Discord policies.

7. How We Share Information

We do not sell personal data. We may share information in limited cases:

7.1 Service Providers

We may share data with vendors that help operate the Services (e.g., hosting providers, databases, monitoring/logging tools, payment processors). They may process data only to provide services to us and are expected to protect it.

7.2 Legal Requests and Safety

We may disclose information if we believe in good faith that disclosure is necessary to:

• Comply with law, regulation, or valid legal process
• Protect the rights, property, or safety of users, servers, the public, or the Services
• Prevent fraud or security incidents

7.3 Business Transfers

If we undergo a merger, acquisition, reorganization, or sale of assets, information may be transferred as part of that transaction, subject to applicable law.

7.4 Within a Server (Expected Functionality)

Some Bot outputs inherently share information within a server context (e.g., a moderation log message posted to a configured channel). This is controlled by server configuration and permissions.

8. Data Retention

We retain information only as long as reasonably necessary for the purposes described above.

Typical retention patterns (may vary by feature and configuration):

• Server configuration: retained while the Bot is in the server; may be retained for a limited time after removal to support restoration.
• Moderation records/logs: retained as long as your server keeps them or the feature requires; may be configurable.
• Diagnostic logs: retained for a limited time for debugging and security.
• Backups: data may persist in encrypted backups for a limited period before deletion through normal rotation.

We may delete or anonymize data at our discretion unless retention is required for security, compliance, or dispute handling.

9. Your Choices and Controls

9.1 Server Admin Controls

Server admins can typically:

• Enable/disable modules (including logging/moderation features)
• Configure log channels and what gets recorded
• Remove the Bot from the server to stop future processing in that server

9.2 User Controls

Users can:

• Stop interacting with the Bot
• Ask server admins what features are enabled in the server
• Use Discord’s tools (e.g., message deletion) where applicable

9.3 Data Access / Deletion Requests

Where reasonably possible and subject to verification and legal/security constraints, we may honor requests to:

• Provide a summary of stored data associated with a Discord ID/server ID
• Delete certain stored data

Important limitations:

• We may be unable to delete data that is embedded in server logs controlled by server admins.
• We may retain certain data for security, abuse prevention, legal compliance, or dispute resolution.

If no official request channel exists, the most reliable way to stop processing for a server is to remove the Bot.

10. Children’s Privacy

The Services are not intended for children under the minimum age required to use Discord in your jurisdiction. We do not knowingly collect personal data from children below that threshold. If you believe a child has provided personal data through the Services, contact us (or remove the Bot) so we can take appropriate action.

11. Security

We use reasonable administrative, technical, and organizational measures intended to protect information. However:

• No method of transmission or storage is 100% secure.
• We cannot guarantee absolute security against all threats.

You are responsible for securing your Discord account and server permissions.

12. International Data Transfers

The Services may be hosted and processed in countries other than where you live. By using the Services, you understand your data may be transferred and processed in jurisdictions with different data protection laws. Where required, we take steps intended to provide appropriate safeguards.

13. Third-Party Links and Integrations

The Services may link to or integrate with third-party services (e.g., dashboards, APIs, payment processors). Their practices are governed by their own privacy policies, and we are not responsible for them.

14. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. The “Last Updated” date indicates the latest version. Continued use of the Services after changes become effective means you accept the updated Privacy Policy.

15. Contact

For privacy questions, requests, or concerns, contact the Premier Utils operator via the official support method published with the Bot (e.g., support server, website, or documentation). If no contact method is provided, removing the Bot from your server is the primary way to stop further processing.

16. Short Notice for Server Admins (Optional Template)

Server admins may post the following notice to members:

Premier Utils Notice: This server uses the Premier Utils bot. The bot processes Discord IDs, command usage, and server configuration to operate. If moderation/logging features are enabled, certain actions and related metadata may be recorded in log channels.