Skip to content

Privacy policy

Effective 20 November 2026

This policy explains how Clanzy collects and processes personal data when you use the Clanzy bot on Discord, the clanzy.app website and the app.clanzy.app dashboard. We comply with Vietnam's Personal Data Protection Decree (Decree No. 13/2023/ND-CP, the "PDPD"). Questions: [email protected].

1. Who is responsible

Clanzy is run by an individual business owner in Vietnam ("we", "us"). We are the controller and processor of personal data under the PDPD. Send any personal data request to [email protected].

2. Data we store

When Clanzy is in a Discord server, we store:

  • The server's ID, name and icon.
  • Server settings chosen by admins: channels, roles, the welcome message, the game list, the room name template and the bot language.
  • Discord user IDs of the members Clanzy interacts with (people it welcomes, people who answer the intro questions, temp voice room owners).
  • Intro answers: the gender option ("Prefer not to say" is offered) and the games the member picked.
  • Temp voice room records: the channel ID, the owner's ID and timestamps (created, owner changed, deleted).
  • When Clanzy welcomed a member, so it never welcomes them twice.
  • Install and uninstall events, with their time.
  • Voice sessions: the member's ID, the voice channel's ID, and when they joined and left. Never audio or what was said.
  • When members join and leave the server, for the weekly report.
  • Daily message counts per text channel (numbers only, no content, not linked to who sent them), for the Pro weekly report.
  • Shield incidents (Pro): the member's ID, the channel's ID, reason codes (for example a fake link), what was done and the mods' decision. The blocked message itself is not stored.
  • Moderation cases: the ID of the member acted on, the moderator's ID (or Clanzy for automatic actions), the action (warn, timeout, kick, ban, unban), the reason the moderator wrote, the timeout length, whether a DM was sent, timestamps and revocations. Never the member's messages.
  • Levels: each member's XP, level, counted voice time and counted messages, when their last counted message was, and weekly XP and voice time for the leaderboards. Numbers only, no message content.
  • Self-role panels: the channel and message ID of each posted panel (the panel itself is part of the server settings).
  • Voice lookup (Pro): when a mod attaches a result to a moderation case, Clanzy stores the snapshot: the time range, member IDs, voice channel IDs and names, when each person joined and left, and the ID of the mod who made it.
  • LFG posts (Need players): the room and owner IDs, the room's game, the post's channel and message ID, whether a role was pinged, how many people were in the room, and when it was posted and closed. The owner's note is not stored.
  • XP seasons (Pro): the season number, start and end, each member's season XP in the running season, and the top members of each ended season.
  • Game role survey (Pro): the games a member tapped as still played, with the time, and what each round's cleanup did.
  • Saved room presets (Pro): the name, user limit, lock state and the IDs of the members a room owner allowed into their room.
  • When Clanzy introduced a newcomer to the players of their game (Pro), so it happens only once.
  • Voice hours per game and per hour of the day (server-wide counts only), for the Pro weekly report.
  • When the Shield quarantines a member: the quarantine role and the roles taken away for now, to give back exactly those when a mod presses Remove timeout.
  • Payments for paid plans: the server, the plan, the amounts, the dates (purchase, renewal, cancellation, end, refund), the order, subscription and customer IDs our payment partner gives us, and the Clanzy account that paid.
  • If a server uses its own bot: the application ID, the bot's name and avatar, and the bot token an admin pasted. The token is encrypted at rest and never shown again.
  • Install source: where Clanzy was added from (for example a link posted on social media with its campaign parameters, the website page where the button was pressed and the visit's anonymous identifier), or an admin's answer to "Where did you hear about Clanzy?".

When you sign in to the dashboard with a Google or Discord account, we store your Clanzy account: the name, email address and avatar of the account you chose, the sign-in accounts you linked, and your login sessions. For a linked Discord account we also store your Discord user ID and the OAuth tokens used to list the servers you manage. The tokens are encrypted at rest.

When you send feedback from the dashboard, we store its type, what you wrote, the screenshots you attached (with hidden image data such as location and camera details removed) and what is sent along: the page you were on, the selected server and its plan, the dashboard version, browser, operating system, screen size, theme, language, and your account and email.

On the website and the dashboard we collect usage analytics (pages viewed, buttons pressed, how you arrived, such as a link or a referring page, device and browser type, approximate country) tied to an anonymous identifier. When you sign in to the dashboard, that identifier is linked to your Clanzy account so we can tell which visits led to an install.

The bot sends product events (for example, a server ran /setup all, a member answered the intro questions, a temp voice room was created) with the server ID. Members in these events are identified only by a one-way hash, never by their Discord ID, and never with message content or names.

When something breaks, we record error details (error type, where in the code, the page or command involved, the version) to fix it. Error reports never contain message content.

We do not store the content of messages in your server in our database. When an admin turns on anti-spam, the bot reads each new message in memory (links, how many people it mentions, repeats) and then discards it; to spot floods it only remembers a hash of each message for a few dozen seconds. When an admin turns on message logs, the bot holds that server's recent messages in memory, at most 500 messages for 6 hours, only to post what a deleted or edited message said into that server's own log channel; this memory is never written to disk and is cleared when the bot restarts. Levels only count messages, never read them. When an admin turns on the Shield (Pro), the bot reads each new message in memory to look for signs of a scam and then discards it. Only a message already flagged as suspicious but not certain may be sent to an automatic AI check for a second opinion; it only answers whether the message is a scam, and the content is not stored there or by us.

We do not store the phone number or password of your Google or Discord account. When you pay, you enter your card on our payment partner's checkout page; card details never reach Clanzy, and we never receive or store card numbers.

3. How we use data

  • To run the features you use: welcoming newcomers, giving game roles, creating and managing temp voice rooms, LFG posts, voice history and voice lookup for mods, moderation, anti-spam, anti-raid, server logs, role panels, levels, the weekly report, the Shield and your own bot.
  • To sell paid plans: opening the checkout, turning plans on, renewing and ending them, telling you when a renewal payment fails, refunds, and keeping records as accounting and tax law require.
  • To let admins see and change settings on the dashboard, and to make sure only people with Manage Server can do so.
  • To keep the service safe, find bugs and prevent abuse.
  • To read the feedback you send, fix the bugs you report and answer you when needed.
  • To learn which features help, using anonymous numbers, so we can improve the product.

We do not sell personal data and do not use it for advertising.

4. Legal basis

We process data based on your consent: admins consent when they add Clanzy to a server, members consent when they answer the intro questions or use temp voice rooms, and you consent when you log in to the dashboard. You can withdraw consent at any time (see Your rights).

Payment data is processed to perform the purchase contract between you and us and to meet accounting and tax obligations. Anti-spam, message logs and the Shield process messages in memory to keep the server safe and help its mods, as configured by the server's admins.

5. How long we keep data

  • A server's data (settings, intro answers, temp voice room records, welcome times, moderation cases, XP, seasons, LFG posts, room presets, game survey answers) is deleted 30 days after Clanzy is removed from that server.
  • Voice sessions are kept 7 days on Free and 90 days on Pro and Own bot, then deleted automatically.
  • Daily counts (messages per channel, members joining and leaving) are kept 120 days for reports and week-to-week comparisons, then deleted automatically.
  • Shield incidents are kept 365 days after they happen, then deleted automatically.
  • Moderation cases are kept 365 days after they are created, then deleted automatically.
  • Weekly XP and voice time are kept 120 days, then deleted automatically. A member's total XP and level are kept while Clanzy stays in the server.
  • Voice lookup snapshots attached to cases are kept 365 days after they are created, then deleted automatically.
  • LFG posts are kept 90 days for the stats, then deleted automatically.
  • Game role survey answers are kept 120 days, then deleted automatically.
  • Members' season XP is deleted when the season ends; only the season's top is kept as history, while Clanzy stays in the server. Saved room presets are kept while Clanzy stays in the server.
  • Feedback (what you wrote, screenshots and what was sent along) is kept 365 days after it was sent, then deleted automatically.
  • When a member joined, left and was welcomed is kept while Clanzy stays in the server, so nobody is welcomed twice.
  • Payment data is kept for as long as accounting and tax law requires, even after the bot is removed.
  • An own-bot token is deleted as soon as an admin removes the own bot in the dashboard, 30 days after the Own bot plan ends, or with the server's data when Clanzy is removed.
  • When a member answers again with /roles, the new answers replace the old ones.
  • Dashboard sessions expire after 30 days, or as soon as you log out.
  • To have data deleted sooner, email a deletion request to [email protected].

6. Sharing and transfers

We share data only with infrastructure providers that process it on our behalf (server hosting, content delivery, usage analytics, the automatic AI check for suspicious messages, the internal messaging app the team uses to receive feedback), under contract and only as far as needed. Payments are handled by our payment partner as the merchant of record: it receives the buyer's card details, email and country to take the payment, charge tax and prevent fraud, under its own policies; we only get the result back. Discord receives and processes data under its own policies.

Data may be stored and processed outside Vietnam, including in the European Union and the United States. We carry out these transfers as the PDPD requires.

We disclose data to authorities only when the law requires it.

7. Your rights

Under the PDPD you have the right to:

  • Be informed about the processing of your personal data.
  • Give or withdraw consent.
  • Access your data and ask for corrections.
  • Ask us to delete your data, restrict processing, or object to processing.
  • Receive a copy of your data.
  • Complain, report, take legal action and claim damages as provided by law.

Send your request to [email protected] with your sign-in email or Discord user ID (or your server ID if you are an admin). We answer within the time the law sets, usually within 72 hours.

Some things you can do yourself: members can answer again with /roles or leave the server; admins can change settings on the dashboard or remove Clanzy from the server.

8. Security

All connections to Clanzy are encrypted. OAuth tokens and own-bot tokens are encrypted at rest, and only Clanzy's operator can access the systems. If a data breach happens, we will notify the competent authority and the people affected within the time the PDPD requires.

9. Children

Clanzy is not meant for anyone below the minimum age Discord allows. If you are a parent or guardian and believe your child gave Clanzy personal data, contact [email protected] and we will delete it.

10. Browser storage

The website saves your light or dark theme choice in your browser. On the official site, the analytics tool uses a cookie and an anonymous identifier to count visits. The dashboard uses a cookie to keep you logged in.

11. Changes to this policy

When this policy changes we update this page and the effective date at the top. For important changes we will say so clearly on the website before they apply.

12. Contact

Any privacy question: [email protected].