Clien
← Back to home

Privacy Policy

Last updated: October 25, 2026

1. Overview

This Privacy Policy explains how the Clien Discord bot ("Clien", "the bot", "we", "us") collects, uses, stores and deletes information when you add the bot to a Discord server or interact with it.

Clien is operated by the Clien team. We are an independent project and are not affiliated with, endorsed by, or sponsored by Discord Inc.

Short version: we store Discord IDs, server settings and the data needed to run each feature. We do not sell data, do not use it for advertising, and do not use message content to train AI models.

2. Scope

This policy applies to the Clien bot application and to this website. It does not apply to Discord itself or to other bots and services. Discord's own privacy policy governs the platform data Discord collects.

3. Data we collect

We collect only the data needed to provide the features a server has enabled.

CategoryExamplesWhy
Server data Guild ID, guild name, icon, owner ID, channel and role IDs Identify the server and apply its configuration
User data User ID, username and display name where needed, avatar URL for display, role IDs Run commands, show profiles, assign roles
Configuration Prefixes, module settings, automod rules, welcome and autorole settings, ticket panels, level and invite settings Remember how each server wants the bot to behave
Moderation data Case ID, target user ID, moderator user ID, action, reason, timestamps Provide moderation history and accountability
Leveling and activity Message counts, XP, level, invite attribution, giveaway entries Run leveling, invite and giveaway features
Support data Ticket metadata, claim state, staff application answers Operate tickets and staff applications
Premium data Entitlement status, plan, expiry date, guild or user ID Provide paid features. We do not receive or store full payment card details
Technical data Error logs, command name, timestamps, latency Debug failures and keep the bot reliable

We do not ask for or intentionally collect passwords, payment card numbers, government identifiers, or other sensitive personal data.

4. Message and moderation data

Some features need to evaluate messages that are not commands. When a server enables automod, honeypot channels, ghost-ping detection or similar protections, the bot processes the content and embeds of messages in the protected channels in real time to decide whether a rule was violated.

  • Message content is processed in memory to make a moderation decision.
  • The bot does not keep a separate persistent archive of message content.
  • When a rule triggers, a moderation log entry may be sent to the log channel configured by the server. That log lives in Discord and is controlled by the server's administrators.
  • A short in-memory cache may hold recently deleted messages so the snipe feature can show them. This cache is cleared automatically and is not written to persistent storage.

We do not read messages to train AI models, build advertising profiles, or sell data.

5. Presence data

If a server enables staff duty tracking or activity roles, the bot receives presence updates for members in that server. For duty tracking we store only the user ID, the status transition (for example online to offline) and start and end timestamps. For activity roles we use the activity name only for as long as needed to assign or remove the role.

We do not store presence history, custom status text, client platform, or activity data beyond what a configured feature needs. Staff members can opt out of duty tracking where the feature provides an opt-out command.

6. AI features

If a server enables an AI chat feature, the text needed to generate a reply may be sent to the AI provider configured for the bot. The bot does not use that text to train models. Servers that do not enable the feature are not affected.

7. How we use data

  • Provide, configure and operate the bot's features.
  • Enforce server rules and security protections such as anti-nuke and automod.
  • Respond to support requests and investigate abuse.
  • Maintain reliability, fix bugs and prevent misuse.
  • Manage premium entitlements where applicable.
  • Comply with legal obligations.

We do not sell personal data. We do not use data for advertising or profiling, and we do not use message content for AI or machine-learning training.

8. Legal bases

Where data protection law requires a legal basis, we rely on:

  • Contract: to provide the bot features a server has enabled.
  • Legitimate interests: to keep the bot secure, prevent abuse and improve reliability.
  • Consent: where a feature explicitly asks for it, such as optional duty tracking.
  • Legal obligation: where we must retain or disclose data by law.

9. Retention

We keep data only as long as needed for the feature that uses it.

  • Server configuration is kept while the bot remains in the server.
  • Moderation cases, leveling data, invite data and ticket metadata are kept for the period configured by the server, or until deleted on request.
  • Duty sessions are deleted automatically after the configured retention period, which defaults to 90 days.
  • Error logs are kept for a short period for debugging.
  • When the bot is removed from a server, the server's configuration and related records are deleted or scheduled for deletion, except where retention is required for security or legal reasons.

10. Sharing

We share data only with:

  • Discord, as the platform that delivers events and stores messages and channels.
  • Hosting and infrastructure providers that run the bot and its database, under confidentiality and security obligations.
  • Payment providers, if premium purchases are offered. They process payment details directly; we receive only entitlement status.
  • AI providers, only if a server enables an AI feature.
  • Authorities, where required by law or necessary to investigate abuse.

We do not sell or rent personal data.

11. Security

We use reasonable technical and organisational measures, including encryption in transit, access controls, least-privilege permissions and restricted database access. No system is perfectly secure, so we cannot guarantee absolute security.

12. Your rights

Depending on your location, you may have the right to access, correct, delete, restrict or object to the processing of your data, and to request a portable copy. To make a request, contact us in the support server and include your Discord user ID and the server ID.

You can also ask a server administrator to remove the bot or disable the feature that holds your data.

13. Server administrator controls

Server administrators control which features are enabled, which channels are monitored, which roles are tracked, and how long data is kept where the feature allows configuration. Removing the bot from a server stops further collection for that server.

14. Children

Clien is not directed at children under 13, or under the minimum age required by Discord or local law. We do not knowingly collect data from children below that age. If you believe a child has provided data, contact us and we will delete it.

15. International transfers

The bot and its database may be hosted in a country different from yours. Where required, we use appropriate safeguards for international transfers.

16. Changes

We may update this policy to reflect new features or legal requirements. The date at the top shows the latest version. Material changes will be announced in the support server.

17. Contact

For privacy questions or data requests, join the Clien support server and open a ticket, or contact the bot owner on Discord.

Please do not send passwords, tokens or payment details in a support ticket.