Privacy Policy

Effective date: 9 August 2026

Mod Team Stats is a private, self-hosted tool operated by the administration team of a single Discord server. This policy describes what the bot and its dashboard collect, why, and how that data is handled. The guiding principle is data minimisation: the service stores structured counts and identifiers, not content.

1. What is collected, and why

The service tracks members of the server's staff team (holders of the two configured staff roles). For those staff members it stores:

• Moderation activity — action type (ban, warn, timeout, ...), timestamp, a success flag, the acting moderator's Discord ID, and the numeric ID of the actioned user, parsed from the server's existing moderation-log channel.
• Role tenure — when staff roles were granted or revoked, from the server's role-log channel, gateway events, and the audit log.
• Engagement counters — per-message records containing only numeric IDs and boolean flags (had media, was a reply, reply target ID), voice-channel join/leave timestamps, and reactions given or received (emoji plus message ID).
• Identity — the staff member's Discord user ID, username, display name, and server join date.

This data exists solely so the server's administrators can evaluate moderation-team performance and workload.

2. What is not collected

• No message content. Message text, embeds, and attachments are parsed transiently in memory to extract the structured facts above and are never stored — including moderation reason text and target usernames.
• No presence data. The bot does not use Discord's presence intent; online status and activities are never read.
• No data about regular members. Non-staff members appear only as incidental numeric IDs (for example, the target of a moderation action). No profile, message, or activity data is kept about them.

3. Dashboard sign-in

The dashboard uses Discord OAuth (identify and guilds.members.read scopes) to confirm who you are and which roles you hold on the operating server. Successful logins are recorded (user ID, username, timestamp) as an access audit trail. The dashboard sets two cookies: a signed session cookie that expires after one hour and a short-lived state cookie during the OAuth flow. There are no analytics, advertising, or third-party tracking cookies.

4. Storage, retention, and sharing

All data is stored in a self-hosted database controlled exclusively by the server's administration team. It is retained indefinitely to support all-time statistics, and is never sold, shared with third parties, or used for any purpose beyond internal team management. Access requires an explicit per-user or per-role grant issued by an administrator.

5. Your rights

Staff members (current or former) can ask the server's administration team on Discord what data is stored about them, and can request correction or deletion. Deletion requests are honoured except where a minimal record is needed to keep aggregate team statistics consistent.

6. Changes and contact

Material changes to this policy are announced in the operating server; the effective date above reflects the latest revision. Questions can be raised with the server's administration team directly on Discord.