GachaDad uses data to run the bot and dashboard. We do not sell user data. This page explains what is processed and how to contact us.
1. Data we collect
GachaDad receives information from Fluxer when you use the bot or when a server enables its features. Depending on how it is used, this can include:
- Identifiers and profile details: Fluxer user IDs, usernames and display names; server, channel, message and role IDs; server names and icons; and profile pictures when available. A player ID and username record may be created from an ordinary message even if it is not a command.
- Commands and game data: command text and inputs, names or IDs mentioned, user-supplied notes, aliases, image links and submissions, and Gacha game data such as collections, wishlists, currency, cooldowns and leaderboard-related statistics.
- Moderation and server settings: prefixes, blocked words, logging channels and settings, and records such as warnings, bans, role-based mutes and timeouts, including the people involved, reasons, times and durations. Role-based mutes also store the affected member's prior text-permission settings for restoration. Optional server logs can also include member joins and departures, moderation and audit events, and voice-channel joins, departures, moves and server mute or deafen changes.
- Message content and media: the bot reads message content to recognize commands and, when configured, check blocked words. If server logging is enabled, it may temporarily cache messages and post message edits, deletions, content and media links to the server's selected log channel. The caption feature processes submitted text and media. The
$phonecallcommand is a text chat between server channels, not a voice call: it relays text, usernames and avatar images to the other channel and can relay reactions. Messages in those channels may be captured by the server's regular logging if it is enabled. - Voice: GachaDad joins voice channels to play music; it does not record or log voice conversations. It uses voice-state information to manage playback. If a server enables moderation logging, the bot may post voice-channel activity such as joins and departures, but not the audio.
- Dashboard and website: Fluxer OAuth provides account details and the server list and permissions needed for sign-in. The server holds an OAuth access token and session information; a session cookie is stored in your browser. The dashboard does not receive your Fluxer password. Hosting, network or proxy providers may process IP addresses, request details and diagnostic logs when you visit.
2. How we use data
We use this information to authenticate dashboard users and check permissions; respond to commands; run games and preserve progress; save server settings; apply moderation and blocked-word rules; produce optional server logs; relay text chats between servers; provide media and music features; check votes; troubleshoot; and help prevent abuse. Server administrators control which optional moderation and logging features are enabled.
3. Storage and retention
- Bot data: settings, moderation records, game progress and submissions are stored in MySQL. They do not have a general automatic deletion deadline and may remain until changed or manually removed. Removing the bot from a server does not automatically erase all stored records. Some actions, such as removing a warning or ending a tracked ban, mute or timeout, clear their corresponding active record. Gacha progress is associated with a channel, but deleting that channel does not automatically delete its stored player records or other user data from the database.
- Messages and temporary files: message content is processed for bot features. In servers with logging enabled, up to 150 recent messages per channel may be held in memory for edit and deletion logs until displaced, removed or the process restarts; switching logging off does not necessarily clear messages already cached. Copies sent to a Fluxer log channel remain there under that server's and Fluxer's control. Caption processing uses temporary files that the bot attempts to remove after processing; interruptions may leave files behind.
- Dashboard sessions: sessions expire after eight hours. Session and OAuth access-token data are held in server memory until sign-out, restart or cleanup after expiry (normally within 15 minutes). The browser session cookie is used to maintain sign-in; it is HttpOnly and SameSite=Lax, and is marked Secure when HTTPS is configured.
- Logs and backups: service diagnostics can include identifiers or error details; host or proxy logs and any backups may have separate retention determined by their configuration. A deletion request may require reviewing those copies too.
5. Your choices and data requests
To request access to, correction of, or deletion of data held by GachaDad, join the GachaDad support server and contact the team there. Include your Fluxer user ID and, if relevant, the server and channel IDs and the kind of data involved. We may need to verify your identity or authority over a server before acting. Do not send passwords, access tokens or other secrets.
Server managers can change settings or turn off logging and the word filter in the dashboard. Data already posted in a server's Fluxer channels is controlled by that server and Fluxer; ask the server's administrators or Fluxer about those copies. Deleting a Gacha channel is not a reliable way to erase stored user data. Requests are handled manually; there is no self-service deletion command. Depending on your location, you may have additional rights and may contact your privacy regulator.
6. Changes to this policy
We may update this policy as GachaDad changes. The latest version and its update date will appear on this page.
Reach the GachaDad team in our support server.