Privacy Policy

1. What We Collect

• Discord IDs (user, server, channel, role) needed to operate features.
• Basic Discord profile info (username, avatar) for anyone who logs into a dashboard with Discord - login only ever requests the minimal "identify" scope, never your full list of servers.
• Message-derived stats: XP/levels, and (separately, and unconditionally - not dependent on whether Leveling is even turned on) a running per-member message count used for the dashboard's activity analytics.
• Moderation records: warnings, mute/ban history, and their reasons/timestamps.
• Ticket data: ticket metadata (opener, type, timestamps), and for closed tickets, a saved transcript containing the full message content of that specific ticket channel.
• Ban appeal submissions, if a server has Ban Appeals enabled: the appeal text itself, plus the submitter's Discord username/avatar and its review status.
• Server configuration: settings configured via the Bot's commands or dashboard (channel/role IDs, feature toggles, custom messages, saved embed templates, etc).
• For Premium servers: a Stripe customer/subscription ID, used only to check subscription status - see "How Data Is Stored" below for how billing itself is handled.
• Recent moderation activity shown on the staff dashboard's Activity feed - kept on disk, capped at the 200 most recent entries per server (2000 for Premium servers); older ones are dropped automatically, and it can be cleared early with the "Clear Activity" button on that page.

2. What We Don't Collect

Reaper does not permanently store the content of regular server messages. Some optional features do need to read message content in the moment to do their job: auto-moderation scans messages for banned content, the translator (when enabled) sends message text to Google Translate to produce a translation, and the AI chat assistant (when enabled) sends message text to Google's Gemini API to generate a reply and keeps a short conversation history in memory per channel - that history lives only in the bot process's own memory, is never written to disk, and is lost on a bot restart (or cleared manually with /aichatreset). The one real exception to "we don't store message content" is ticket transcripts, which do capture and save the full message content of that specific ticket channel.

3. How Data Is Stored

Most of this data (server configuration, moderation records, tickets, XP, message counts, the activity feed) is stored locally, in plain files on the machine running the bot - not in any general-purpose third-party database, and never sold. A few specific features do send data to specific third-party services in order to work: Stripe handles Premium billing and payment details end-to-end (Reaper's own servers never see your card number), and Google's Gemini and Translate APIs process message text for the AI chat assistant and translator, but only for servers where those optional features are turned on.

4. Retention

• Warnings, giveaways, and starboard entries are automatically cleared after 30 days.
• Closed-ticket history keeps the 100 most recent closed tickets; older entries are dropped.
• Ticket transcripts are kept until the server owner deletes them.
• Leveling/XP and message-count data is kept until the server owner clears or resets it.
• Ban appeal submissions are kept until a staff member deletes them from the dashboard - there's currently no automatic expiry.

5. Who Can See What

• Every dashboard page requires logging in with Discord first, and only ever shows data for servers you're actually a member of - there's no page that's visible to just anyone with the link. (The separate marketing site is public, but shows no per-server data at all.)
• Overview and Leaderboard are visible to any logged-in member of the server.
• Tickets & Warnings and Activity require a staff/moderator role in that server.
• Settings and Premium require the Administrator permission in that server; the Embed Builder requires Administrator or Manage Channels.
• The local admin dashboard (a separate, older panel) is bound to the machine running the bot itself and isn't reachable from the open internet at all - there's no login on it, so anyone with access to that machine effectively has full admin access.

6. Children's Privacy

Reaper is not directed at children under 13, consistent with Discord's own Terms of Service.

7. Your Choices

Server members can ask the server's staff to remove or reset their data (warnings, XP, message counts, etc) at any time using the Bot's existing commands, and staff can delete an individual ban appeal submission from the dashboard on request.

8. Changes

This policy may be updated from time to time.

9. Contact

Questions about this policy can be directed to the Reaper team via our support server on Discord.

Read the Terms of Service