Privacy Policy for Hugo

Last updated: 06/11/2026

1. Data We Collect

Hugo collects and stores the following data in a local database to provide its features:

Per-User Data (stored per server)

• Discord user ID, username, and display name.
• Username and display name history (up to 20 previous names per user per server).
• Chat XP/chat level, voice XP/voice level, reputation count, invite count, and who invited you (inviter's user ID) for leaderboards, awards, and logging features.
• Per-period award counters such as messages sent, chat XP, voice XP, and reputation earned during the current awards period.
• Birthday settings if you use /birthday: whether birthday announcements are enabled for you, your birth month/day, optional birth year, and the last date your birthday was announced.
• Your level alert preference (whether Hugo should show your level-up/reward alerts).
• CAPTCHA attempt counts, verification status, and jail status.
• A cached list of your roles (updated on role changes, used in leave/kick/ban log embeds).
• Last message activity timestamp and server join timestamp.

Server Data

• Server IDs, channel IDs, and role IDs needed for configuration.
• All server settings you configure through Hugo's commands or dashboard. Where a feature allows custom text (such as announcement messages, autoresponse triggers and responses, automessages, sticky messages, role DMs, level-up messages, birthday messages, awards text, reputation feedback, embed titles and footers, thread titles, Twitch/YouTube alerts, bump reminders, captcha messages, kick/ban reasons, voice generator name templates, color role name formats, and saved message templates), that text is stored as part of the configuration.
• Scheduled tasks such as reminders, scheduled kicks/bans/unbans, timeout-expiry notices, automessages, warnings, QOTD posts, birthday announcements, and awards. These may include text you provide (e.g., reminder messages, kick/ban reasons).
• QOTD data, including pending pitch questions (with question text, author ID, username, and timestamp), approved queue entries, skip lists, and recent posted-question history (up to 20 recent questions with timestamps).
• Flair role details: custom role names, colors, and icon URLs you provide.
• Per-command blocked user ID lists.
• Confessions and suggestions metadata: the author's user ID, timestamp, and the Discord message ID (up to 1,000 each per server). The text itself is only posted to Discord, not stored by Hugo. Server moderators may be able to reveal the author of a confession.
• Starboard entry metadata: the original message ID, starboard message ID, and author's user ID. The message content is re-posted to the starboard channel on Discord, not stored by Hugo.
• Moderation warnings (including reason text, moderator ID, and expiry date).
• A cache of server invite codes (invite code, inviter user ID, use count, max uses, and expiry) for invite tracking.
• A cache of pinned message IDs and author IDs per channel for pin/unpin logging.
• Reaction role bindings for emoji, button, and dropdown role menus (message IDs, channel IDs, and role mappings).
• Group definitions (group names, member user IDs, channel IDs, and permissions).
• Voice generator settings and active spawned-channel metadata (generator channel IDs, spawned channel IDs, naming templates, and owner user IDs).
• Role DM rules (role IDs and the DM text to send when that role is granted).
• Twitch and YouTube subscription settings, including watched streamer/channel IDs or names and the last notified stream/video ID to avoid duplicate alerts.
• Pending age-alert entries when "wait until verified" is enabled (user ID, inviter ID, and join timestamp).
• Patron subscription status and trial dates per server owner.

Dashboard Data

• If you use the web dashboard, Hugo stores a session containing your Discord OAuth2 tokens (access and refresh tokens) to authenticate you. These are stored locally in session files.

2. Data We Do NOT Collect

• Regular message content — Hugo reads messages to process commands and features such as chat XP, autoresponses, sticky messages, autothreads, reputation, starboard keywords, and honeypot moderation, but does not store the content of regular chat messages. Text you explicitly submit through Hugo's features (reminders, autoresponses, announcements, QOTD pitches, automessages, saved templates, flair names, Twitch/YouTube subscriptions, and moderation reasons) is stored as described above. If logging is enabled, Hugo posts embeds to your server's log channels for a wide range of server events (message edits/deletes, thread and channel changes, role changes, member joins/leaves, and more). Logged message embeds may include message content and re-uploaded attachments. This data is sent to Discord and is not stored by Hugo.
• Direct messages — Hugo does not log or store DM content.
• Voice or audio data — Hugo does not listen to or record voice channels.
• Email addresses or IP addresses.

3. How Data is Used

• Chat XP, voice XP, level, and reputation data is used to calculate levels, enforce minimum level requirements on commands, display leaderboards/rank information, and determine awards.
• Invite data is used to track which invite a new member used, to display invite counts and leaderboards, and to show who invited a user in leave, kick, and ban log embeds.
• Username and display name history is used to show previous names in log embeds when a user changes their name.
• CAPTCHA and verification data is used to manage the verification process, track failed attempts, and enforce timeouts.
• The role cache is used to display a user's roles in leave, kick, and ban log embeds after the user is no longer in the server.
• Activity timestamps are used to track active and inactive members.
• Birthday data is used to post birthday announcements, optionally include age, and prevent duplicate birthday posts on the same date.
• Per-period award counters are used to determine winners for scheduled awards and are reset when an award period ends.
• Warning data is used to track moderation history and enforce automated punishments at configured thresholds.
• Scheduled tasks are used to execute timed actions such as reminders, CAPTCHA timeout kicks, automessages, scheduled QOTD posts, birthday announcements, awards, timeout-expiry notices, and temporary unbans.
• The pinned message cache is used to detect pin and unpin events for logging.
• Confession and suggestion metadata is used to link anonymous posts back to authors for moderation purposes.
• Server settings text (announcements, autoresponses, automessages, role DMs, level-up messages, birthday messages, Twitch/YouTube alerts, etc.) is used to send configured messages when their corresponding events occur.
• QOTD pitch questions, approved queues, skip lists, and history are used to review, schedule, avoid repeats, and post Question of the Day content.
• Flair details are used to create, restore, and manage personal color roles for users.
• Per-command blocked user IDs are used to prevent specific users from accessing specific commands.
• Starboard metadata is used to track which messages have been starred and prevent duplicate starboard entries.
• Reaction role bindings are used to assign or remove roles when users interact with configured reaction, button, or dropdown role messages.
• Group definitions are used to manage channel access permissions for sets of users.
• Voice generator metadata is used to create, track, rename, and clean up temporary voice channels.
• Role DM rules are used to send configured direct messages when a user gains a matching role.
• Twitch and YouTube subscription data is used to poll for new live streams/uploads and avoid duplicate notifications.
• Pending age-alert entries are used to delay "new account" alerts until a user becomes verified when that option is enabled.
• Patron data is used to determine access to premium features.
• Dashboard OAuth tokens are used to authenticate users on the web dashboard.

4. Data Sharing

• Your data is never sold to third parties.
• Hugo communicates with the Discord API to function. If Twitch or YouTube notifications are enabled, Hugo also queries Twitch and YouTube using the configured streamer/channel identifiers to check live or upload status. Bot metadata (such as command list and server count) may be shared with Top.gg for bot listing purposes. No user data is sent to third-party analytics, tracking, or advertising services.
• Data may be disclosed if required by law.

5. Data Retention & Deletion

• All user data is scoped to the server it was collected in.
• When Hugo is removed from a server, cached data for that server is cleared.
• Confessions and suggestions are automatically pruned when a server exceeds 1,000 entries.
• Scheduled tasks are deleted once executed or manually cancelled.
• You may request deletion of your server's data by contacting Hugo's owner.

6. Security

Data is stored in a local SQLite database with no external database services. Reasonable measures are taken to protect stored data, but no system is 100% secure.

7. Contact

For privacy concerns, contact: glefs on Discord