ProBotDiscord application

Privacy Policy

How ProBot, the Discord bot and dashboard built for the Pro Modz community, handles the personal data of the server's members.

Last updated
4 November 2026
Operator
MorganDesigns
Application ID
1567575605061484685

01Who we are

MorganDesigns ("we", "us") operates ProBot (the "Bot"), a Discord application with the application ID 1567575605061484685, and its companion web dashboard at probot.morgan-lee.dev (the "Dashboard"). The Bot is built for one Discord server, the Pro Modz community (the "Server"), at the request of that Server's owner. It is not a public bot and cannot be added to other servers.
We are the data controller for the personal data described in this policy. The Server's owner and staff decide which features are switched on and how they are configured, and they can see the data described below through the Dashboard. Discord processes your data separately under its own Privacy Policy.
This policy covers the Bot and the Dashboard only. It does not cover Discord itself, YouTube, or any website linked from the Server.

02The data we process

ProBot only processes data that Discord makes available to bots in the Server, plus what you type into the Bot's own forms, such as a ticket. We never ask for your email address, payment details or any data from outside Discord.

Identity

What
Your Discord user ID, username, display name and avatar, and whether the account is a bot.
Why
To show who did what in logs, tickets, giveaways and the Dashboard without calling Discord every time.
Kept for
While you are in the Server, and removed within 90 days of you leaving.

Membership events

What
When you joined or left, when your account was created, and which invite link you used and who created it.
Why
Verification, welcome messages, raid detection and the invite log.
Kept for
Invite attributions for 90 days. Joins and leaves are kept only as daily totals.

Messages

What
Message text is scanned as it is posted to detect spam, scam links and raids. It is not stored, except: messages inside ticket channels, the short excerpt of a message that triggered an automatic action, and, where staff enable logging, the previous text of an edited or deleted message, which is posted to a staff-only log channel on Discord.
Why
Keeping the Server safe and giving staff a record of tickets.
Kept for
Ticket messages until the ticket is deleted. Excerpts for 90 days. Log-channel posts are stored by Discord under the Server's control.

Moderation and security

What
Timeouts, kicks, bans and quarantines with the reason, the moderator and the time; repeat-offence counts; anti-raid and anti-nuke incidents; and the roles removed from a quarantined member so they can be restored.
Why
Enforcing the Server's rules and protecting it from raids and hijacked accounts.
Kept for
For as long as the Bot serves the Server, because bans and repeat-offence checks depend on it.

Tickets

What
The subject and details you enter, every message and attachment link in the ticket channel, who claimed and closed it, and the HTML transcript.
Why
Support and purchase enquiries handled by Server staff.
Kept for
Until Server staff delete the ticket from the Dashboard, or you ask us to remove it.

Giveaways

What
Which giveaways you entered, whether you won, and whether you claimed the prize.
Why
Picking winners fairly and removing duplicate entries.
Kept for
30 days after the giveaway ends.

Roles and verification

What
The verify button and the role menus change your roles on Discord. The Bot stores nothing beyond the Discord role change itself.
Why
Letting you into the Server and choosing platform, region and notification roles.
Kept for
Not stored by the Bot.

Presence and statistics

What
A count of members who are online, boosting or bots, and daily totals of members, joins, leaves and messages. No individual presence or activity is stored.
Why
The statistics channels and the Dashboard overview.
Kept for
Daily totals indefinitely, as numbers only. Counters are live and not stored.

Activity feed and error logs

What
One-line summaries of events such as "X joined" or "Y was timed out by Z", and technical error reports that may include the IDs of the user, channel or message involved.
Why
Giving staff a live view of the Server and helping us fix bugs.
Kept for
30 days.

Dashboard login

What
When staff sign in with Discord we receive the Discord user ID, username, avatar and the list of servers that account is in, and we check which roles it holds in the Server. A session cookie keeps you signed in.
Why
Deciding who may use the Dashboard.
Kept for
The session cookie expires after seven days or when you sign out. Nothing else is stored from a login.

03How we use it

We use the data above for these purposes and nothing else:
  • Running the Server's verification, welcome messages and role menus.
  • Detecting and acting on spam, phishing links, raids and attempts to damage the Server.
  • Running tickets, giveaways, statistics channels and YouTube upload announcements.
  • Giving the Server's staff a Dashboard to configure the Bot and review what it did.
  • Keeping the Bot reliable by diagnosing errors and preventing abuse.
We do not use your data for advertising or profiling, and we do not sell, rent or trade it with anyone.

05Automated actions

The Bot acts on its own in a few situations. It can delete a message and time you out for spam or scam links, quarantine or remove accounts during a raid, and remove the roles of an account that performs mass destructive actions. These are safety measures. Every one of them is posted to a staff channel with an undo button, so a person can review it.
If you think the Bot acted wrongly, open a ticket or contact Server staff and they can reverse the action.

06Who we share it with

  • Discord. Everything the Bot posts, every role it changes and every direct message it sends goes through Discord's API. Discord's own policies apply to that data.
  • Our hosting provider. The Bot and its database run on a server rented from OVH Ltd, London, United Kingdom. The provider supplies the infrastructure and does not access the data.
  • Nobody else. We do not use analytics, advertising or tracking services in the Bot or the Dashboard. The lists of known phishing domains the Bot downloads are public lists, and your messages are checked against them on our server and never sent out. YouTube announcements use YouTube's public feed, and no member data is sent to YouTube.
  • If the law requires it. We may disclose data to comply with a legal obligation or to protect the rights and safety of members.
All data stays in the United Kingdom. If that ever changes we will update this policy first.

07How we keep it safe

  • The Dashboard and all traffic to Discord use encrypted connections.
  • The database is reachable only by the Bot and the Dashboard, never from the internet.
  • Credentials are kept outside the code and rotated if we suspect exposure.
  • Nightly backups are kept for 14 days and then deleted.
  • Dashboard access needs a Discord login and a staff role granted by the Server's owner. Staff see only what the owner lets them see.
No system is perfectly secure. If a breach puts you at risk we will tell affected members and the Information Commissioner's Office, as the law requires.

08How long we keep it

30 days
Activity feed, error logs, and giveaway entries after the giveaway ends.
90 days
Your identity snapshot after you leave the Server, invite attributions, and excerpts of messages that triggered an automatic action.
Until deleted
Tickets and transcripts, which Server staff can delete from the Dashboard and which we delete on request.
While the Bot serves the Server
Moderation and security records, because bans and repeat-offence checks depend on them.
Indefinitely
Daily statistics, which are totals and contain no personal data.
14 days
Backups, which roll over and are then overwritten.
If the Bot stops serving the Server we delete its database within 30 days. Backups expire on their own schedule.

09Your rights

You have the right to access the personal data we hold about you, to have it corrected or deleted, to restrict or object to our processing of it, and to receive a copy in a portable format. You can also withdraw consent at any time for the features that rely on it.
To exercise any of these rights, email MorganMoonLee@gmail.com or message morgan.m on Discord from the account the request is about, so we can confirm it is you. We answer within one month. We may keep moderation and security records where we need them to enforce a ban or protect the Server, and we will tell you if that applies to your request.
If you are unhappy with how we handle your data you can complain to the UK Information Commissioner's Office at ico.org.uk, or to the data protection authority in your own country.

10Children

Discord requires its users to be at least 13 years old, or older where local law sets a higher minimum age. The Bot is not aimed at children and we do not knowingly process data about anyone under that age. If you believe we hold data about a child, contact us and we will delete it.

11Changes to this policy

We will post any changes on this page and update the date at the top. If a change materially affects how we use your data we will also announce it in the Server before it takes effect.

12Contact

MorganDesigns is responsible for this policy and for ProBot. Email MorganMoonLee@gmail.com, or message morgan.m on Discord. Please mention ProBot so your request reaches the right place.