1. Scope
This policy applies when you use the Bozos website/dashboard, Bozos Forever, Bozos TTS, Bozos Unanswered, Bozos Relay, Bozos RoleSync, or the Bozos TTS Gaming Overlay desktop app. Different features need different information, and feature-specific data is used only as needed to operate, secure, troubleshoot and improve those systems.
2. Discord account and server information
The dashboard uses Discord authentication to identify the signed-in account and determine which servers that account is allowed to manage. Bozos stores Discord server identifiers and configuration values needed to remember each server's enabled systems and settings.
Some features also require Discord user, channel, role, message or thread identifiers. Examples include moderation cases, birthdays, AFK, voice-channel streaks, scheduled messages, Unanswered support cases, Relay synchronization and RoleSync role connections. These identifiers are used to connect the relevant Discord objects to the feature that needs them.
The Bozos TTS Gaming Overlay uses Discord OAuth with the identify scope to connect the desktop app to the correct Discord account. During sign-in, Discord provides a temporary OAuth access token to the Bozos backend so the account can be identified. That Discord OAuth access token is not stored by the desktop app. After sign-in, Bozos issues its own Overlay session token, which is stored locally on the device so the app can stay connected between launches and updates. Disconnecting Discord from the Overlay clears the locally stored Overlay session.
3. Messages and ordinary chat content
Bozos does not keep a general archive of ordinary Discord conversations. Message content can be processed temporarily when a feature needs it, such as moderation checks, TTS speech, Unanswered detection, Relay delivery, commands or Bozos Audit event handling.
The Scheduler is an exception because scheduled message text and its target channel must be kept while waiting to be sent. Successfully completed scheduled messages are removed from the pending schedule system.
Bozos Unanswered and Bozos Relay have additional feature-specific handling described below. Neither product is intended to become a permanent archive of ordinary server conversations.
4. Moderation information and Bozos Audit
Bozos Audit sends configured moderation, member, message, voice and server event logs directly to the Discord destinations selected by the server. It is separate from the persistent moderation case system.
Bozos Forever keeps moderation case information required for features such as /modlogs, warnings and warning management. A case can include the server, affected user, moderator, action type, reason and related moderation details.
5. Birthday and AFK features
When the Birthday System is enabled and a member chooses to set a birthday, Bozos stores the member's Discord user identifier together with the birthday day and month needed to provide birthday messages. A birth year is not required.
When a member uses AFK, Bozos stores the information needed to show that member's AFK state, such as server/user, reason and the time the status was set.
6. Voice-channel activity
The VC streak and leaderboard systems store the information required to calculate voice activity, including server/user identifiers, streak values, last active dates and voice time. The leaderboard cycle resets monthly.
7. Bozos TTS
Bozos TTS processes eligible Discord message text so it can generate speech in the active voice session. It can process mentions, emoji, URLs, numbers, dates and formatting to make speech natural. TTS is not intended to create a permanent archive of the conversation being read aloud.
For internal service monitoring, Bozos may keep limited operational metadata about an active TTS session, such as the Discord server and voice-channel identifiers/names, participant count, queue depth, shard/instance information, connection time and recent heartbeat. This operational view does not store or display the text being spoken.
The public Bozos TTS leaderboard keeps a cumulative processed-message count for tracked TTS servers. To provide the exact rolling last-24-hours view, Bozos temporarily stores the Discord message ID, server ID and timestamp for counted TTS messages. The rolling-history table does not store message content, the author's user ID or username, attachments or the spoken audio. Message timestamps are derived from Discord message IDs, and expired rolling-history rows are removed after the 24-hour window by scheduled cleanup.
Leaderboard usage is batch-synchronized at checkpoints such as hourly intervals, voice-session end and graceful shutdown rather than writing ordinary message content into a permanent conversation archive.
8. Bozos TTS Gaming Overlay
The Gaming Overlay connects to the Bozos TTS service in real time to find the voice channel associated with the signed-in Discord account and to display the information needed for Overlay features. While the Overlay is active, this can include the current Discord server and voice-channel identifiers/names, the active Bozos TTS instance, voice-channel member identifiers/display names/avatar URLs, and the current TTS speaker/text needed to render the on-screen HUD. This live information is used for the active session and is not stored as Overlay analytics.
The Overlay stores user preferences locally on the device, such as widget positions and sizes, visible widgets, subtitle options, Quick Speak phrases, global hotkeys, selected display, compact/performance preferences, and the list of registered games. Registered-game data can include a game name and executable path. The app also examines visible running applications, foreground window titles and executable paths on the device to detect games and decide when the Overlay should appear. This game/process detection is performed locally and game/process data is not sent as Overlay telemetry.
To measure real usage without storing raw Discord account identifiers in analytics, the Overlay sends an authenticated launch event to the Bozos backend containing the app version and operating-system platform. The backend validates the Overlay session and converts the Discord user ID into a deterministic HMAC-based pseudonymous identifier before storing analytics. The stored Overlay analytics are limited to that pseudonymous identifier, app version, platform, first-seen time, last-seen time and launch count. Overlay analytics do not store the raw Discord user ID, Discord OAuth token, machine name, hardware identifier, registered games/process data or TTS message text.
9. Bozos Unanswered
Bozos Unanswered watches only the support channels selected by server administrators. When a qualifying member message creates or updates an active unanswered case, the service can temporarily store the server, channel and user identifiers; the root/latest and recent message identifiers; a short message preview; message count; case timing; claim state; alert level; and identifiers for live alert messages. This information is used to determine whether somebody is still waiting and to keep the Discord alert card synchronized.
Unanswered operates as a live work queue rather than a permanent case-history archive. When a case is marked answered or ignored, its live case row is deleted after the bot has the information needed to render the final Discord state. Active case data can also be removed when the bot is deliberately purged from a server.
Server configuration can include monitored channel IDs, alert channel ID, support-role IDs, alert timing, escalation rules and optional business-hours settings. Free-tier usage information can include the current UTC usage month and a monthly new-case count. Configuration and current-month usage may remain after the bot is removed from a server so removing and re-adding the bot does not reset plan limits or saved setup.
10. Bozos Relay
Bozos Relay mirrors eligible messages between administrator-configured Discord channels and servers. During delivery it can temporarily process message text, display names, avatar URLs, embeds and attachment URLs so the destination webhook can reproduce the conversation. Relay does not store ordinary relayed message text, usernames, avatar images, attachment bodies or spoken/audio content in its synchronization database.
Relay stores configuration needed to operate each connection, including owner/member server IDs, channel IDs, direction, enabled features, plan state and health information. To synchronize later edits and deletes, Relay temporarily stores compact mappings containing source and destination Discord message/channel/server/thread identifiers and related technical delivery identifiers.
Message-map retention depends on the Relay plan: Starter — 7 days, Plus — 14 days, and Premium — 30 days. Expired mappings are pruned automatically. Thread mappings are created only when a supported public thread is actually relayed and are also kept for a bounded synchronization period. Private Discord threads are not relayed.
Relay suppresses mention parsing on mirrored messages to prevent a mirrored message from re-pinging users, roles or @everyone in another server. Relay-owned webhooks are ignored to prevent loops, and the current Relay runtime does not mirror arbitrary webhook or bot-authored messages.
11. Bozos RoleSync
Bozos RoleSync responds to Discord member joins, departures and role changes to synchronize configured role pairs between participating servers. Saved settings include owner/participating server IDs, selected role IDs, one-way or two-way direction, enabled status, removal options, and timestamps. Member IDs and current role memberships are temporarily processed to apply role changes; no ordinary chat messages or permanent member-role history are recorded by RoleSync.
The bot saves relevant role inventory and role-manageability information for dashboard setup. Subscription state, expiration and temporary payment identifiers may be kept as needed to provide Free (three connections) and Premium (unlimited subject to fair use) access. Extra connections can remain saved but paused when Premium expires. Removed bot installations can retain configuration while marking the guild inactive.
RoleSync does not read ordinary Discord channel messages, cannot add members to another server, and can only manage permitted roles below its own highest role. Role removals and source-departure removals are optional, with departure removal off by default.
12. Service safety and staff operations
Authorized Bozos staff may use a private control panel to monitor whether the bots are online, identify servers where the bots are installed, review active TTS session metadata, inspect bot permissions and Bozos configuration state, review Relay and RoleSync connection health, investigate operational problems or abuse, apply or revoke service restrictions, control the availability of individual Bozos systems, and review internal staff-action history.
The Staff Panel can also queue an official Bozos notice for delivery to a server through a Bozos bot installed there. The notice content is written by authorized staff and the delivery action is recorded for accountability. The inspector may keep operational server metadata such as server/channel/role identifiers or names, bot role and permission state, configured feature state and safe notice destinations; it does not provide staff with a general archive of server conversations, Unanswered conversation history after cases conclude, Relay message content or TTS message text.
Restriction records can include the affected Discord user or server ID, which Bozos service the restriction applies to, an internal case identifier, reason, duration, staff account responsible for the action, and revocation details. Staff access records and privileged staff actions are also recorded for security and accountability.
13. Website usage and network information
The public website uses limited site-performance and usage measurement. Bozos application features do not intentionally save visitors' raw IP addresses as normal bot, dashboard or Overlay analytics records. Network requests still require technical processing for pages, authentication, rate limiting, security and connected services to function. For example, authentication services can process an IP address temporarily in memory to rate-limit repeated requests.
14. Payments, subscriptions and donations
Some Bozos products can offer optional paid plans or digital services, while donations remain optional. For eligible paid checkouts, Bozos can use Paddle as Merchant of Record. Paddle may process billing details, payment-method information, tax information, fraud-prevention signals and transaction records under its own privacy terms. Information returned to Bozos from checkout is used as needed to create, verify and maintain the related purchase or subscription. Bozos does not ask users to provide passwords, card PINs or online-banking passwords to the project team.
Bozos may store limited payment entitlement information needed to activate or maintain a plan, such as the relevant Discord server, plan, entitlement period and provider transaction/subscription identifiers. Full card or bank credentials are not stored in the bot configuration tables.
15. Google AdSense, cookies and advertising technologies
Public content pages may use Google AdSense. When Google advertising services are used, Google and its advertising partners may receive information needed to serve, secure, measure and personalize or otherwise select ads. Depending on the visitor, region and consent choices, this can include the page URL, IP address, browser or device information, cookies, web beacons/pixels and other identifiers.
Third-party vendors, including Google, may place or read cookies on a visitor's browser or use similar technologies to collect information as a result of ad serving on this website. Google may use advertising cookies to show ads based on a visitor's prior visits to this website or other websites. Where required, consent choices can affect whether personalized or non-personalized advertising is used.
Google explains how it uses information from sites and apps that use its services at How Google uses information from sites or apps that use our services. More information about advertising technologies is available at Google Advertising Technologies. Visitors can manage Google ad personalization through My Ad Center.
16. Security
Bozos uses protected authentication and server-side controls for sensitive website, bot, payment-entitlement and Overlay actions. Users should never send Discord passwords, bot tokens, session cookies, OAuth tokens, Overlay session tokens or payment secrets to anyone claiming to provide support.
17. Age requirements
Bozos is designed for Discord users who meet the minimum age required by Discord in their country or region.
18. Privacy contact
For a privacy-related question, contact hermionegrangerr_7 on Discord (User ID 1458470088759054525) or use the official Bozos support server. Avoid posting sensitive information in a public channel.
19. Policy updates
This policy can be updated when Bozos features, payment options or legal requirements change. The date at the top identifies the current revision.