Skip to content
Chryyptix

Privacy Policy

Last updated: 16 October 2026

This policy explains what the Chryyptix Discord bot and web dashboard store, why, for how long, and who else handles it. Chryyptix (“we”, “us”) operates the service. It applies together with the Terms of Service.

1. What we collect

Your account

When you sign in to the dashboard with Discord, we ask Discord for the identify, email and guilds permissions. We store your Discord user id, username, display name, avatar, email address and the time you last signed in. We use your server list to show the servers you can manage; it is not stored in our database.

Server configuration

Settings that server admins save for their server, such as channels, roles, messages and which features are on.

Message content

Message text is saved in our database in one case only: tickets. Every message sent in an open ticket channel is saved with its text, attachment links, author and time, so staff can review the ticket after it closes. Edits update the saved copy.

The bot also reads message text, without saving it in our database, for features a server turns on:

  • Message logs: the before and after text of an edited message, or the text of a deleted one, is posted to that server’s own Discord log channel. Our log viewer keeps only a one-line entry (who, which channel, when).
  • Automod: messages are checked against the server’s rules; when a rule acts, an excerpt of the message can be posted to the server’s log channel.
  • Starboard: a message that reaches the star threshold is reposted, with its text, in the server’s starboard channel.

Server activity

For the log events a server turns on, we store a one-line summary with the user and channel ids involved, for example a member joining or leaving, a ban and its reason, a nickname or role change, or a channel or role update. The join and leave log embeds posted to the server’s log channel also show the member’s account age, the member count and, on leave, the roles they held. We do not store full member lists.

Feature data

Depending on the features a server uses, we also store:

  • moderation warnings and moderation cases;
  • leveling XP;
  • economy balances and transactions;
  • reminders;
  • streamer availability;
  • recruitment applications and answers;
  • poll votes and giveaway entries;
  • server settings for each feature.

Payments

Payments are processed by PayMongo. Card and wallet details go to PayMongo, not to us. We store the server the pass is for, who bought it, the amount and currency, the pass length, the payment status, PayMongo’s payment and checkout ids, our reference number, and when it was paid or refunded.

2. Why we use it

  • To sign you in and check which servers you can manage.
  • To run the features a server has turned on.
  • To let staff review closed tickets and recent server activity.
  • To apply Premium to the right server and keep a payment record.
  • To keep the service secure and fix problems.

3. How long we keep it

  • Server log entries: 7 days on Free, 90 days on Premium. Older entries are deleted by a daily job. Log messages the bot posted in a server’s own Discord channel stay there; we do not delete them.
  • Ticket transcripts: 30 days on Free, 365 days on Premium, counted from when the ticket closed.
  • Your server list is cached for 60 seconds to avoid repeated calls to Discord.
  • When the bot leaves a server, that server’s data is deleted 30 days later. If the bot is added back before then, the data is kept.
  • Other data is kept while the server or your account uses the service.

Database backups may still contain deleted data until those backups are themselves removed.

4. Where it is stored and who processes it

  • Amazon Web Services (AWS) hosts the service. The database and cache run on the same server.
  • Discord provides sign-in and delivers the server events the bot works with.
  • PayMongo processes payments.
  • Twitch and YouTube are queried for the public channels a server sets up stream or upload alerts for.
  • RSSHub is used to fetch public X and TikTok feeds for alerts. Only the public account being followed is requested; no data about you is sent.

AI providers are not used today. If that changes, this policy will be updated.

5. Cookies

  • __Secure-authjs.session-token keeps you signed in. It is encrypted, cannot be read by the page’s scripts, and holds the Discord sign-in tokens our server uses to load your servers.
  • Short-lived cookies set during sign-in protect the Discord login and remember where to send you afterwards.
  • chryyptix-theme remembers whether you picked the light or dark theme, for one year.

We do not use analytics, advertising or tracking cookies.

6. Your rights

You can ask us for a copy of the data we hold about you, to correct it, or to delete it. Server admins can also remove the bot from their server, which starts the deletion described above. You can export or delete your own data yourself with /privacy export and /privacy delete in any server where the bot is installed, or send requests to the contact below. You can also change what Discord shares with us from Discord’s Authorized Apps settings.

7. Children

Chryyptix is for people who meet Discord’s minimum age in their country (13, or older where local law requires it). If you believe someone under that age has given us their data, contact us so it can be deleted.

8. Changes to this policy

We may update this policy. When we do, we change the “Last updated” date on this page.

9. Contact

Privacy questions and requests go to the operator, Chryyptix.

Operator identity, governing law and a contact address will be added before launch.