Privacy Policy
Last updated 29 October 2026
The short version
- Chorus stores public leaderboard data from The Hive: gamertags, leaderboard positions and game stats.
- When you run a command, Discord sends Chorus what it needs to answer. Chorus doesn't keep a history of who ran what.
- If you hide yourself with
/privacy, Chorus stores your Discord ID next to the gamertag you hid. - In the Chorus Development server, Chorus also keeps XP and moderation records.
- No ads, no selling data, and no cookies or analytics on this website.
Who we are
Chorus ("Chorus", "we", "us") is a free Discord app that shows statistics and leaderboards from The Hive, a Minecraft: Bedrock Edition server. It's an independent project run by its developer, and it isn't affiliated with The Hive, Mojang, Microsoft or Discord.
This policy covers the Chorus Discord app, this website, the account verification page at hivechorus.duckdns.org, and the features Chorus runs in the Chorus Development Discord server.
Data from The Hive
What: for players who appear on The Hive's public all-time, monthly and seasonal leaderboards, Chorus stores:
- their gamertag, any previous gamertags Chorus has seen, and the player ID (UUID) The Hive's API uses
- their leaderboard positions
- the game stats published with those leaderboards: wins, games played, kills, deaths and final kills
- when Chorus first and last saw them on each leaderboard, and when their stats last changed
From this, Chorus calculates its own estimates, such as grinder level, activity and combat skill.
Where it comes from: The Hive's public API, plus an archive of older monthly leaderboards that were collected from the same public source.
Why: it's what Chorus's commands show. If you're in the EEA or UK, the legal basis is our legitimate interest in offering statistics about public game leaderboards. The data is already public, and it's limited to game stats.
Who can see it: anyone who uses Chorus's commands.
How long: leaderboard history is kept for as long as Chorus runs, because history is what
commands like /positions are for. You can ask for removal, see your choices.
When you use Chorus in Discord
When you run a command or press one of Chorus's buttons, Discord sends Chorus the interaction: your Discord user ID and username, where you used it (server, channel or DM), and the options you picked. Chorus uses this to answer you.
- To apply the short cooldown between commands, Chorus remembers your user ID and the time of your last command in memory for a few seconds. This is never written to disk.
- Chorus counts how many commands were run each day, as a single number that isn't linked to anyone. It's shown in the bot's status.
- Chorus's server writes technical logs to help fix problems. Some entries, such as a completed
/privacyverification, include a Discord user ID. Logs are rotated automatically and are only read to keep Chorus running. - While Chorus is in early access, the Discord user IDs of people who've been given access are kept in its settings.
Chorus doesn't read your messages in other servers, and it doesn't store which commands you ran.
The /privacy command
To check that a gamertag is yours, /privacy sends you to Discord to authorize Chorus with the
identify and connections permissions. If you've added Chorus to your apps, it also asks
to keep that install (applications.commands) so it isn't removed.
- Chorus reads your Discord user ID and your connected accounts once, to find the Xbox account linked to your Discord.
- The list of your connections and the access token Discord issues aren't stored. The token is discarded straight after the check and expires on its own.
- If you turn privacy on, Chorus stores the gamertag, its player ID, your Discord user ID and the date. This is kept until you turn privacy off.
- Verification links expire after 10 minutes. Requests in progress are only held in memory.
- The verification page at hivechorus.duckdns.org doesn't keep visitor logs.
Afterwards, Chorus is listed under Authorized Apps in your Discord settings. You can remove it there at any
time. This doesn't turn privacy off. Use /privacy for that.
In the Chorus Development server
These features only run in Chorus's own Discord server, not in servers you add Chorus to.
- Levels: your Discord user ID, XP, number of messages that earned XP, time spent in voice channels, display name and avatar link (for the level leaderboard), and whether you've left the server.
- Moderation: warnings and temporary bans, with the reason, the moderator and the time.
- Server logs: staff-only log channels may record joins and leaves, role, nickname and avatar changes, voice channel joins and leaves, server changes, and edited or deleted messages. Chorus remembers recent messages in memory (up to 5,000) so a log can show what a deleted or edited message said. That memory is cleared whenever Chorus restarts.
- Spam protection: posting in a channel reserved for catching hacked accounts gets the author removed automatically, along with their recent messages, and sent a message explaining how to rejoin.
XP is kept until it's reset or you ask for it to be deleted. Warnings are kept until staff clear them, and temporary bans until they expire. Log messages stay in the log channels until staff delete them.
This website
This website has no cookies, no analytics, no ads and no tracking scripts, and it doesn't load anything from other websites. It's hosted on Cloudflare Pages. Cloudflare processes technical data such as your IP address to deliver the site and protect it from attacks, as described in Cloudflare's privacy policy. We can see aggregated traffic numbers in Cloudflare's dashboard, but no personal visitor logs.
Who we share data with
We don't sell or rent data, and we don't use it for advertising. Data is processed by these services, only so Chorus can run:
- Discord, the platform Chorus runs on
- Oracle Cloud Infrastructure, which hosts the server Chorus and its data run on
- Cloudflare, which hosts this website
- DuckDNS, which provides the address of the verification page. It receives no personal data.
Chorus reads data from The Hive's public API, but it doesn't send any of your data to The Hive. We'll only disclose data to others if the law requires it.
Storage and security
Chorus's data is stored on a server operated by Oracle Cloud Infrastructure, and only the developer can access it. Passwords and keys are kept out of the code, connections to the website and the verification page are encrypted (HTTPS), and the data files are written so that a crash can't leave them half-saved. A small number of backup copies are kept on the same server before major maintenance.
Your choices and rights
- Hide yourself on today's daily leaderboards with
/privacy. - Ask for a copy of the data Chorus holds about you, or ask us to correct or delete it. You can also object
to Chorus processing it. Ask in the Chorus Development server. We may ask you to
prove that an account is yours first, for example with the same Xbox check
/privacyuses. We'll reply within 30 days. - If you're still on The Hive's public leaderboards, Chorus can pick your stats up again from later updates. If you want to stay out of Chorus for good, say so in your request and we'll do our best to exclude you.
- Remove Chorus from your apps or your server at any time. Discord then stops sending it anything from you.
If you're in the EEA or UK, you also have the right to restrict processing and to complain to your local data protection authority.
Children
Chorus is a Discord app, so you need to meet Discord's minimum age to use it: 13 in most countries, and older in some. We don't knowingly collect data from anyone younger. If you think we have, tell us and we'll delete it.
Changes to this policy
If this policy changes, we'll update the date at the top. Significant changes will also be announced in the Chorus Development server.
Contact
For questions or requests about your data, ask in the Chorus Development Discord server.