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.
• Curated AI knowledge deliberately submitted with remember: in a configured private knowledge channel, together with the contributor's Discord ID/name and submission time.
• Voice incident reports, only when a server administrator has enabled the feature and a member in the monitored voice channel submits a report: a short mixed WAV audio clip, the reporter's ID/name, the voice channel's ID/name, participant IDs/names, join/leave events, optional report context, timestamps, and review status.
• Voice auto-moderation detections, only when a server administrator separately enables that feature: the detected speaker's Discord ID/name, a short locally generated transcript, the configured term that matched, a confidence estimate, the selected moderation action and its result, and a short evidence clip.

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). If the server owner configures a private AI knowledge channel, messages explicitly prefixed with remember: are stored locally as curated knowledge until an authorized trainer removes them with forget:; other messages in that channel are not stored as knowledge. Ticket transcripts are the other exception: they capture and save the full message content of that specific ticket channel.

When voice incident reporting is enabled, decoded voice audio is held temporarily in an in-memory rolling buffer while Reaper monitors an active voice channel. Audio that ages out of the buffer is discarded, and nothing from that buffer is written to disk unless a member submits a voice report or the separately enabled voice auto-moderation feature detects a configured term. Ordinary incident reporting does not transcribe audio. When voice auto-moderation is enabled, Reaper processes short per-speaker windows with a speech-recognition model running locally on the bot's host; audio is not sent to an external AI or speech-to-text provider.

3. How Data Is Stored

Most of this data (server configuration, moderation records, tickets, XP, message counts, the activity feed, deliberately saved AI knowledge, submitted voice-report metadata and clips, and voice auto-moderation detections) is stored locally, in plain files on the machine running the bot - not in any general-purpose third-party database, and never sold. A submitted or automatically generated voice evidence clip may also be attached to the server's configured Discord review channel when it is small enough for Discord's upload limit; access to that copy and its retention are then also governed by that channel's permissions and Discord's services. A few other specific features send data to 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.
• Unreported voice audio remains only in the rolling memory buffer (configured from 15 to 180 seconds) and is discarded as it ages out, when monitoring stops, or when the bot restarts.
• Submitted voice reports and voice auto-moderation detections, including their local WAV clips and detection transcripts, share a cap of the 200 most recent reports per server. When a new report exceeds that cap, Reaper deletes the oldest local report and clip. A clip or detection attached to a Discord review-channel message may remain there until that message, channel, or server is deleted.

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.
• Voice reports and local clip playback require a logged-in server moderator with Administrator, Kick Members, Ban Members, or Moderate Members permission. Anyone able to view the configured Discord review channel may also be able to access a clip attached there, according to that channel's Discord permissions.
• Settings and Premium require the Administrator permission in that server; the Embed Builder requires Administrator or Manage Channels.
• The operator of the machine hosting Reaper can access locally stored data, including submitted voice-report clips. The local admin dashboard (a separate, older panel) is bound to that machine and isn't reachable from the open internet.

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. Server administrators can disable voice auto-moderation without disabling incident reports, or disable voice incident reporting entirely to stop monitoring and disconnect Reaper from voice. Requests concerning a stored voice report, an automated detection, or other personal data can be directed to the server's staff or to the Reaper team through the support server below.

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