Privacy Policy for Hugo

Last updated: 05/04/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).
• XP, level, and invite count for leveling and leaderboard features.
• 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 (for activity tracking, not message content).

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, level-up messages, embed titles and footers, thread titles, bump reminders, captcha messages, kick/ban reasons, color role name formats, and saved message templates), that text is stored as part of the configuration.
• Scheduled tasks such as reminders, scheduled kicks, automessages, and warnings. These may include text you provide (e.g., reminder messages, kick/ban reasons).
• QOTD pitch questions submitted by users (stored with the question text, author ID, and timestamp).
• 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 (emoji-to-role mappings per message).
• Group definitions (group names, member user IDs, channel IDs, and permissions).
• 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 calculate XP, 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, 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

• XP and level data is used to calculate levels, enforce minimum level requirements on commands, and display leaderboards and rank information.
• Invite data is used to track which invite a new member used and to display invite counts and leaderboards.
• 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.
• 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, and scheduled QOTD posts.
• 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, level-up messages, etc.) is used to send configured messages when their corresponding events occur.
• QOTD pitch questions are used to populate the question of the day queue for server administrators to review and post.
• 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 react to configured messages.
• Group definitions are used to manage channel access permissions for sets of users.
• 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. 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