Privacy
Privacy Policy
Plain language, no surprises. This explains what LavaBot stores, why it needs it, how long it sticks around, and how to get it deleted.
Last updated: June 22, 2026
Who runs this
The short version.
LavaBot is a self-hosted Discord bot and dashboard run by one person, PolloSpellato. Your data lives in PolloSpellato's own database. It is not sold, rented, or handed to advertisers, and there is no third-party analytics or tracking baked into the site.
What we collect
Only what the features actually use.
- Website account: your email, a hashed password (we never store the plain one), the display name you pick, an optional headline and bio, your role, and sign-in timestamps.
- Sign-in audit: IP address and browser user-agent for login, register, and logout events, kept so the account stays defensible against break-in attempts.
- Discord link: if you connect your Discord account, we store your Discord user ID so the bot can match premium status to you.
- Server configuration: for servers where LavaBot is added, the settings a server admin chooses (anti-raid, chat filter, automod, logging, welcomes, reaction roles, feature toggles) plus role and channel IDs those settings reference.
- Moderation and event logs: when a server enables logging or automated moderation, we record the events it is configured to record (joins, leaves, bans, edits, deletes, and so on), including the target user ID, the acting moderator ID, a reason, and a timestamp.
- Server backups: on request, a snapshot of a server's structure (roles, categories, channels, permission overwrites). Backups do not contain message history.
Message content
The honest part everyone should read.
Chat filtering, automod, and message logging need to read message content to do their job. That reading happens in memory, in the moment, to check a message against the rules a server admin turned on.
We do not keep a copy of every message. Content is only written down when a server has logging enabled and an event fires that is configured to capture it (for example, the previous text of an edited message or the body of a deleted one). If a server never enables those features, no message content is stored at all.
Support tickets are the exception: the full conversation is kept for a limited time so the request can be handled, see Support tickets below.
Support tickets
What we keep when you ask for help.
When you open a support ticket, we keep the conversation so the request can actually be handled.
- Full transcript: every message in the ticket, who sent it, when, and the text, stored in order so staff can read the conversation back.
- Attachments: any files you send in the ticket are stored privately so staff can review them.
Why: to handle and follow up on your support request, and to keep a short record of what was asked and answered.
How long: a ticket is temporary. The transcript and any attachments are deleted automatically 30 days after they are created. Attachment files are permanently removed from storage; after that the dashboard shows them as expired instead of offering a dead link. Only the basic ticket record (its number, server, subject, and open and close times) is kept beyond that.
Who can see it: the moderators and admins of the server the ticket belongs to, verified by their real Discord permissions in that server, and only for that server. A moderator of one server can never read another server's tickets. Attachments are never reachable through a public link: they can only be opened through this access control. PolloSpellato, who runs LavaBot, can also access tickets, for support and diagnostics, as explained right below.
PolloSpellato's access to tickets
The honest part about support.
LavaBot is run by one person, PolloSpellato. To be able to actually help when something goes wrong, PolloSpellato can open and read the contents of a support ticket, including its messages and attachments, on any server where LavaBot is installed. This is what makes it possible to investigate a bug, recover a stuck ticket, or follow up on a support request that a server's own staff escalated.
This access exists only for support and diagnostics. Ticket content is not browsed, monitored, or used for anything else.
Every time PolloSpellato opens a ticket, that access is recorded: which ticket, which server, and when. So there is an auditable trail of when that access happened.
This is the one exception to the rule above. A server's own moderators only ever see that server's tickets, checked against their real Discord permissions, and never across servers. PolloSpellato's wider access is the single broader case, and it is the one that gets logged.
How long we keep it
Logs expire on their own.
- Moderation logs, anti-raid events, chat-filter events, and sign-in audit events expire automatically after a set retention window (90 days by default) and are removed by the database.
- Support ticket transcripts and any attachments are deleted automatically 30 days after they are created.
- Account data and server settings are kept while the account or the server configuration exists, and are removed when you delete them.
- Server backups are kept until you delete them or they roll off the per-server backup limit.
Your choices
You are in control of your data.
- See it: signed-in users can export a copy of the data tied to their account from the dashboard.
- Delete it: you can delete your website account, which removes your profile, unlinks your Discord ID, and clears your sign-in history.
- On Discord: the
!forgetmecommand unlinks your Discord ID from its LavaBot website account, and!mydatashows what is stored. - Per server: server admins can turn any logging or moderation feature off, which stops new data from being recorded.
How it is protected
Reasonable, current safeguards.
Passwords are stored using a strong one-way hash. Sensitive payment metadata, where it exists, is encrypted at rest. The dashboard rate-limits requests, locks out repeated failed logins, sets hardened session cookies, and is served over HTTPS in production. No system is perfect, but the goal is to keep your data boring and uninteresting to attackers.
Third parties and children
Two quick notes.
The only outside service in the normal flow is Discord itself, which you already use, and its content delivery network for avatars. We do not share your data with anyone else.
LavaBot is not directed at children. Discord requires users to be at least 13 (or older where local law sets a higher age), and the same applies here.
Changes and contact
How to reach a human.
If this policy changes in a meaningful way, the date at the top will move and the change will show up in the changelog. For privacy questions, data exports, or deletion requests that the in-app tools do not cover, reach PolloSpellato through the support server linked from the dashboard.