Server Sage — Discord bot for Quaver communities
This policy explains what data the Server Sage Discord bot (“the Bot”, “we”) collects, why, and how it is handled. By adding the Bot to a Discord server, or by linking your Quaver account to it, you agree to the practices described here.
Contact: contact@serversage.net
Server Sage is an independently operated, non-commercial Discord bot. It is not affiliated with, endorsed by, or operated by Quaver, the Quaver Team, or Discord Inc. It uses Quaver’s public API to read publicly available game data.
When you link your Quaver account (via /account), we store:
We do not collect or store your Discord password, email address, phone number, IP address, or payment information. We never ask for your Quaver password or any authentication token.
For linked accounts, the Bot periodically reads publicly available data from Quaver’s API and stores:
All of this originates from data you have already made public through Quaver’s own leaderboards and API.
Optional cosmetic settings you set yourself, such as session graph colors, a session background image URL, idle-time threshold, and timezone offset.
Per-server settings configured by server staff: channel IDs for bot features, role IDs (Keeper, Officer, clan ping, muted role, challenge medal roles), the server’s Quaver clan ID, and personal-score thread IDs. These identify channels and roles, not people.
Applies to servers where moderation features are enabled by server staff.
When a moderator uses moderation commands, the Bot stores a record containing: the target user’s Discord ID, the acting moderator’s Discord ID, the action taken, the stated reason, expiry time, and a timestamp. This forms the server’s moderation history, viewable by server staff via /history.
The Bot uses Discord’s Message Content intent to support message edit/delete logging.
Message content is not written to our database. When a message is deleted or edited in a server that has configured a message-log channel, the Bot relays the message’s text and metadata (author ID, channel, message ID, and — where Discord’s audit log makes it available — who deleted it) into that log channel as a Discord message. From that point the content lives in Discord, under the server’s own control and retention, not ours.
If a server has not configured a message-log channel, no logging occurs.
| Purpose | Data used |
|---|---|
| Link your Discord identity to your Quaver profile | Discord ID, Quaver ID |
| Post score, session, and rank-milestone updates | Gameplay and session data |
| Run clan challenges, points, streaks, and medal roles | Clan map scores, points, streaks |
| Route bot features to the right channels and roles | Server configuration |
| Enforce and review moderation actions | Moderation records |
| Provide server staff with edit/delete visibility | Message content (relayed, not stored) |
We do not sell, rent, or trade any data. We do not use it for advertising or profiling, and we do not share it with third parties except as described in Section 5.
Data is stored in a MongoDB database controlled by the Bot operator. Access is restricted to the operator. We take reasonable measures to protect stored data, but no system is perfectly secure, and we cannot guarantee absolute security.
The Bot interacts with:
api.quavergame.com) — the Bot sends your Quaver user ID and map identifiers to retrieve public game data. Subject to Quaver’s own terms and privacy practices.railway.app) — the cloud platform that runs the Bot and hosts its MongoDB database. Railway stores and processes data on our behalf, subject to its own privacy practices.To request deletion of your data, contact the operator at the address at the top of this policy. We will delete your linked account record and associated personal data on request. Note that moderation records exist for server-integrity purposes, and requests to delete them are evaluated together with the affected server’s staff. Data already posted into a Discord channel (for example, a score embed or a message log) is under that server’s control and must be deleted there.
The Bot is not directed at children under 13, or under the minimum digital-consent age in your jurisdiction. This matches Discord’s own minimum age requirement. We do not knowingly collect data from anyone below that age; if we learn we have, we will delete it.
We may update this policy as the Bot changes. Material changes will be announced through the Bot’s support server or its repository. Continued use after an update constitutes acceptance.