Privacy Policy
Last updated: October 30, 2026
This Privacy Policy explains what information Beru (the "Bot") collects, why, and how it is handled. It is written to match what the Bot actually does. By using Beru you agree to this policy. We never sell your data, and we do not use it for advertising.
1. Information the Bot receives from Discord
Like every Discord bot, Beru receives information from Discord about the servers it is in: server, channel and role details, member lists (user IDs, usernames, roles, join dates), messages in channels it can see, voice state changes, and audit log entries. Most of this is processed live and is not stored.
2. Message content
Beru reads messages to detect commands and, when a server has enabled them, to run automod filters (spam, links, invites, bad words, mass mentions and similar), autoresponders, auto-reactions, sticky messages, media-only channels and AFK mentions. Message content is processed in memory and is not saved to the Bot's database, with these exceptions:
- Snipe: the last 25 deleted or edited messages per channel (author, text, attachment links, time) are kept in temporary memory so moderators can use the
snipecommand. They are never written to disk and are cleared whenever the Bot restarts. - Text you ask the Bot to save: for example reminder text, AFK reasons, your profile bio, blacklisted words, autoresponder triggers and replies, greeting/leave messages, saved embeds and sticky messages.
- Logs and transcripts set up by a server: if a server enables logging, the Bot posts events (such as deleted or edited messages, member joins/leaves, role and channel changes) into that server's own log channels. Ticket transcripts are generated as an HTML file and posted in the server's channels. These live in the server's Discord channels, not in the Bot's database.
3. Information the Bot stores
To work, Beru saves settings in a data file on the computer that hosts the Bot. This mostly contains Discord IDs (numbers that identify users, roles, channels and servers) and the settings you configure:
| Data | Why |
|---|---|
| Server settings: prefixes, Extra Owners, Trusted Users, main roles, fake permissions | Permission system and custom prefix |
| Antinuke, panic mode and automod configuration (whitelists, limits, filters, log channels, blacklisted words) | Security features |
| Short-lived protection data: channel/role layout and role permissions captured during an attack or lockdown | Undoing nuke damage and restoring after panic mode. Most of it is kept only in memory. |
| Moderation records: quarantined members (with the roles to give back), chat/voice bans, temporary bans/mutes and their end times | Moderation commands |
| Tickets: support roles, ticket types, open tickets (channel and opener ID), ticket counter | Ticket system |
| Giveaways: prize, host, end time, winner and entrant IDs | Running and rerolling giveaways |
| AFK status and reason, reminders (user ID, text, time), custom roles | Utility features |
| Greetings, leave, join DM and boost messages, embeds, logging settings, autoroles, reaction roles, auto delete/react/responder, sticky, media-only, VC role, vanity/guild tag rewards, verification settings | Server features you configure |
| YouTube channel IDs and the last video seen, for upload alerts | YouTube notifier |
| Profile bio, badges, no-prefix access, music playlists and preferred music source (per user, not per server) | Profile and music features |
The Bot does not collect email addresses, passwords, phone numbers, IP addresses, payment details or your private DMs with other people.
4. How the information is used
Only to provide Beru's features in your server: checking permissions, protecting the server, running moderation and automation, and showing your settings back to you. The data is not sold, rented or shared for marketing.
5. Third-party services
Some commands contact outside services to fetch content. Only what is needed for the request is sent (for example a search term or a YouTube channel ID), never your messages or account details:
- YouTube (upload alerts via public RSS feeds, and music search/playback when music is enabled)
- Meme, GIF and lyrics services used by fun and music commands (meme-api.com, nekos.best, lrclib.net) and Spotify link previews
- The website that hosts the Bot's help menu icons
Your use of Discord itself is covered by Discord's Privacy Policy.
6. Storage, security and retention
Data is stored in the Bot's data file on its hosting server, which only the developer can access. Settings are kept for as long as they are needed to provide the features, and are removed when a server admin resets or turns off the matching feature (most modules have a reset command). When Beru is removed from a server, that server's saved settings are not deleted automatically; you can ask for them to be deleted at any time (see below). No system is perfectly secure, but we take reasonable care to protect the data.
7. Your choices and data deletion
- Server admins can view, change or reset the Bot's settings with its commands at any time.
- You can remove your own bio, AFK status and reminders with the Bot's commands.
- To request a copy or deletion of data stored about you or your server, contact the developer in our support server with your user or server ID. We will handle it as soon as reasonably possible.
8. Children
Beru is meant for people who meet Discord's minimum age requirement. We do not knowingly collect information from anyone below that age.
9. Changes to this policy
We may update this policy as Beru changes. The date at the top shows the latest version.
10. Contact
For privacy questions or requests, contact the developer in our support server.