Beta Counting Premium is freshly released and still in beta — a few rough edges are expected. See what's new →
Counting Premium logo Counting Premium

Legal

Privacy Policy

Last updated

Counting Premium is a Discord bot built and maintained by a single developer. This page is a short, honest description of what data the bot stores and what it doesn't.

What is stored

  • The server ID and the IDs of channels registered with /setup.
  • The user IDs of members who have counted at least once — used for cooldowns, streaks, and milestones.
  • The numeric value of each count attempt, so the bot can tell if it was correct. Other message content is not read or stored.
  • Per-server configuration: the active theme, an optional custom background URL, and milestone targets.
  • If a user votes for the bot on top.gg, the bot receives their user ID and the vote time so the in-bot vote reward can be credited. Nothing else is received from top.gg.

What is not stored

  • No email addresses, real names, IP addresses, or device IDs.
  • No message content from non-counting messages, edits, or deletions.
  • No voice, video, or DM data. The bot does not respond in DMs.
  • No advertising, analytics, or third-party trackers.

How the data is used

Strictly to run the bot: accept or reject count attempts, maintain streaks and milestones, apply the chosen theme and background, and credit top.gg vote rewards. Data is not sold, rented, or shared with advertisers, and is not used to train any AI model.

Removal

All data for a server is kept in a single record, and per-user stats (streaks, daily counts, milestone hits) live inside that record — there is no separate per-user entry. To have a server's data cleared, use either of the two supported paths:

  • Run /reset in the server. Requires the Manage Channels permission. Wipes the server's full record (channel setup, current count, theme, background, and every per-user stat) and removes the counting embed from Discord.
  • Remove the bot from the server. The record stops being used. Backups are rotated on a regular cycle, so anything still in them is gone shortly after.

Changes

The "Last updated" date at the top of this page reflects the most recent revision. Major changes will also be mentioned on the changelog page.