Privacy Policy
Effective date: 31 October 2026
- Lelune mostly stores server settings: which channels and roles to use, and your texts.
- It stores a few user IDs and names where a feature needs them, for example Tripwire counters and who made the last change.
- Lelune does not read or save the content of chat messages. The only exception is a message an admin writes on purpose to the Lelune team with Contact Lelune team.
- A short technical log for fixing errors is deleted after at most 7 days.
- Data stays on Lelune's host. We never sell it or share it for ads.
- Ask us and we delete your server's data.
This policy can change
We can change this policy, and Lelune's features, data handling and rules, at any time. When we do, we update the effective date at the top of this page. If you keep using Lelune after a change, you accept the new version. See Changes to this policy.
Contents
1. Who we are
Lelune is a Discord bot run by the Lelune team ("we", "us"). This policy explains what data Lelune stores when it is added to a Discord server, and why.
2. What Lelune stores
Lelune saves data for each server separately, linked to the server's ID. It only stores data for the features an admin uses.
| Feature | What is stored |
|---|---|
| Verification | On or off, the chosen verify channel and role IDs, the check level, the rules text, the ID of the verify message. While the server is locked: the time, the name of the admin who locked it, and the earlier permission settings of each changed channel, so Unlock can put them back. |
| Welcome and leave | On or off, the channel ID and the message text written by an admin. |
| Auto roles | On or off and the IDs of the chosen roles. |
| Tripwire | On or off, the trap channel and log channel IDs, kick or ban, the rejoin limit, total kick and ban counts, and for kicks: the user IDs of kicked members with how often each was kicked (the list of recent kicks keeps at most 50 people). |
| Server stats | On or off, the chosen stats, the IDs of the stats category, channels and message, and when each stats channel was last renamed. |
| Backups, templates and undo | Copies of the server's layout: role names, colors and permissions, channel and category names, types, topics, order and role permissions. No messages and no members. The backup schedule and the time of the last backup. For 24 hours after a rebuild, an undo copy of the layout before it. |
| System protection | A copy of each protected channel or role (name, type, topic, position, settings and permission overwrites, which can include role and user IDs), the times it was restored, and if it was removed on purpose: when and by whom (Discord name). For protected system messages of Lelune (Tripwire warning, Verify message, stats message): only the message ID, the channel ID and the channel name, never the content. |
| Technical log | To find and fix errors, Lelune writes a short technical log on its host. For each button, menu or command used in the panel it notes the time, the button or command ID and the Discord name of the person who used it. It also notes server and channel names in some entries (for example automatic backups and server locks) and error messages. It never contains chat messages, verification codes or tokens. |
| Last action | Only the most recent change per server: a short description, the Discord name of the admin who made it, and the time. |
| Status counts for the Lelune team | Every minute Lelune sends counts to the Lelune team panel: the number of servers and members in total, how long the bot has been running, its version, how often each kind of error happened, how often the panel was opened, and on how many servers each feature is on. No server IDs, user IDs, names or messages. |
| Lelune team panel | For members of the Lelune team who log in: their Discord user ID, name and avatar, their login sessions, and a log of what they did in the panel. |
| Contact Lelune team (tickets) | When an admin writes to the Lelune team: the server ID, server name and member count, the Discord user ID and name of each admin who writes in the ticket, the topic, the messages of the admins and the team with their times, who claimed and who closed the ticket, and if the message came from an error card the error ID and a short error text. An invite link only if the admin ticks the box; it works once and ends after 7 days. When the ticket is closed, a transcript (a copy of the whole conversation) is kept with it. |
| Ticket channels on the server | On the bot's host, per ticket: the ticket number, topic, status, dates, the ID of the private ticket channel and of the card in it, the ID of the admin who sent it, and the ID and key of the webhook Lelune uses to post team replies there. No message text. |
| Contact blacklist | Server ID, server name, the reason, whether the reason is shown to the server, the date, and which team member added it. |
| Error IDs | When an error card is shown, Lelune keeps a short error text with a random error ID in memory for 24 hours, so an admin can send it to the team. It is not saved to disk. |
3. What Lelune does not store
- The content of chat messages. Lelune does not ask Discord for message content. If someone writes in the Tripwire channel, Lelune deletes that message without saving it. The only exception is text an admin writes on purpose in the Contact Lelune team form or with Reply to the team. Text typed straight into a ticket channel is not read.
- Verification codes. They only live in memory for a short time and are never written to disk.
- Emails, IP addresses, passwords, payment details or your location.
- Member lists. Lelune counts members for Server stats but does not save who they are.
Lelune does not use cookies, ads or trackers. This website does not either.
4. What Lelune posts or sends
Some features post messages in your server or send direct messages. Those messages are then stored by Discord under Discord's Privacy Policy, not by us:
- Welcome and leave messages mention the member's name.
- The Tripwire log channel shows the name and ID of members who were kicked or banned. The member gets a direct message, which can include a one-time rejoin link.
- System protection reads the server's audit log to find who deleted a protected channel, role or system message, and sends that person a direct message. If that does not work, the server owner gets it.
- If an admin turns on the off-site copy, every backup is also sent to the server owner as a file by direct message.
- When an admin sends a message to the Lelune team, Lelune creates a private ticket channel at the bottom of the server. Only admins of the server can see it. Lelune posts an explaining card there, the admins' replies, and the team's replies (through a webhook that shows the team member's name and Discord picture with "Lelune team"). The channel is deleted when the ticket is closed.
- The admin who sent the message gets short direct messages: when it was sent and when a new reply arrived. When the ticket is closed, every admin who wrote in it gets the transcript as a direct message. Nobody else on the server gets it.
- If an admin ticks the invite box, Lelune creates one invite link to the server for the team. It works once and ends after 7 days.
5. Why we use the data
Only to make Lelune's features work: to remember your settings, to verify members, to count Tripwire kicks so the rejoin limit works, to keep stats up to date, to restore your layout from a backup, to put back deleted system channels, roles and system messages, and to show admins what changed last. We also use it to answer admins who contact the Lelune team, and to stop misuse of the contact feature. We do not use the data for ads, profiling or anything else.
6. Where data is kept and who sees it
The data is kept in files on the computer that runs Lelune (its host). Only the people who run Lelune can access these files. Admins of a server see their own server's data in the panel.
Status counts, messages to the Lelune team, transcripts, the contact blacklist and the team panel data are stored with Cloudflare (Cloudflare Workers and D1), which processes them for us. Cloudflare may process data outside the EU. Only members of the Lelune team can see them, after logging in with Discord. A team member can read a ticket only while nobody else has claimed it, or when the claiming team member added them.
We do not sell, rent or share the data with anyone. We would only hand it over if the law requires it.
7. How long data is kept
- Settings stay saved until an admin changes them. Turning a feature off keeps its settings, so you can turn it back on later.
- Backups: Lelune keeps the last 10 manual and the last 10 automatic backups per server. Older ones are deleted when new ones are made.
- Last action: only the newest entry is kept. Each change replaces the one before.
- Tripwire counters stay until an admin clears them in the panel.
- Undo: can be used for 24 hours after a rebuild and is replaced by the next one.
- Technical log: deleted automatically after at most 7 days. Only the people who run Lelune can read it.
- Status counts: deleted after 30 days.
- Team panel: the log of team actions is deleted after 180 days. Logins end after 12 hours, or 2 hours without use.
- Tickets, their messages and transcripts: deleted 90 days after the ticket was closed. A ticket without a new message for 14 days is closed automatically. Until it is deleted, admins of the server can download the transcript in
/leluneunder Contact Lelune team. - Invite links: removed from the ticket when they end (at most 7 days) or when the ticket is closed.
- Ticket channels and their webhooks: deleted when the ticket is closed. The ticket number, status and IDs on the bot's host: deleted 90 days after closing.
- Error IDs: kept in memory for 24 hours, never saved.
- Contact blacklist: until a team member removes the entry.
- When Lelune is removed from a server, the saved data is not deleted automatically right now. It stays until you ask us to delete it.
8. How to delete your data
Server owners and admins can ask us to delete all data Lelune stores for their server. Members can ask us to delete data linked to their user ID, such as Tripwire counters. To ask, email us at lelunebot@outlook.com.
Please include the server ID (and your user ID if it is about you). We may ask you to show that you are an admin of that server. Admins can also clear Tripwire counters themselves in the panel.
To have a ticket deleted before the 90 days end, email lelunebot@outlook.com with the server ID and the ticket number.
9. Children
Lelune is meant for people who are old enough to use Discord under Discord's own rules (at least 13, or older where the law in your country says so). We do not knowingly store data about anyone younger. If you think we do, please contact us and we will delete it.
10. Changes to this policy
We can change this policy, and Lelune's features, data handling and rules, at any time and without asking first. When we change this policy, we update the effective date at the top of this page. If you keep using Lelune after a change, that means you accept the new version. If you do not agree, please stop using Lelune and remove it from your server.
11. Contact
Questions about your data or this policy? Email us at lelunebot@outlook.com.