UnifiedBot privacy
Privacy policy written by the person who built UnifiedBot
I operate UnifiedBot as a solo builder and take data stewardship seriously. This page spells out, in plain language,
what I collect, how I use it, and the choices you have across the Discord bot, dashboard, and landing site.
Last updated: November 6, 2025
What I collect
Discord account basics
When you or your moderators use the bot I store the Discord user ID, username, discriminator, and avatar hash so I can show who made a change
and map permissions. I do not store email addresses or anything Discord does not already expose through the API.
Server settings
Guild configuration data
I keep the modules, role IDs, channel IDs, ticket options, and automation preferences you set in the dashboard so UnifiedBot can run without reconfiguration.
This data never leaves my infrastructure and is only used to power features inside your guilds.
Operational signals
Audit events & logs
I store moderation events, ticket activity, and high-level audit trails so you have a history and I can troubleshoot incidents.
These logs exclude message bodies unless you explicitly enable transcripts and even then they are scoped to the ticket channel involved.
Website telemetry
Limited analytics
The marketing site collects basic request logs (IP, user agent, referrer) so I can keep the service secure and understand aggregate traffic.
I do not run invasive cookies, advertising pixels, or third-party trackers.
Need something clarified?
Reach me any time at support@unifiedbot.net or via the UnifiedBot support server linked in the dashboard.
When you contact me I will confirm ownership before sharing guild data.