Privacy Policy
Last updated:
This page describes what we do with data when you use a Discord server where a Modern Bots bot is installed, or when you visit modernbots.app. It is written to be read, not to be waved at you.
The data controller is the Creators Area group. For any question, or to exercise your rights: [email protected]
What our bots process on a Discord server
Discord identifiers
We store numeric Discord identifiers: the server, the channel, the message, and the user involved in one of the bot’s features.
We store no username, no avatar, and no message content. An identifier on its own says nothing about you outside Discord.
Server configuration
The settings administrators choose for each feature enabled on their server.
Moderation history
When the bot applies a sanction, it records: the server, the user, the feature that triggered it, its nature (none, timeout, kick, ban), its duration, a short reason, and whether it was reverted, by whom and when.
What the website processes
Audience measurement
The website uses Google Analytics, deployed through Google Tag Manager, to count page views. Nothing else is done with it: no advertising, no profiling, no resale.
What is sent to Google: the pages you view, the date and time, your language and device type, an approximate location derived from your IP address, and a random identifier stored in a cookie so repeat visits can be recognised. Google does not keep your full IP address.
The cookies set are Google Analytics ones (_ga and _ga_*), valid for 13 months. Event data is kept by Google for 14 months. You can refuse them by blocking third party cookies in your browser, or by installing Google’s opt-out add-on: the site works exactly the same.
Language choice
The site remembers your language in your browser’s local storage, under the key modernbots.locale. A second key, modernbots.redirected, is kept in session storage and disappears when you close the tab. These are display preferences, they never leave your device and feed no measurement.
Dashboard
Signing in to the dashboard uses your Discord account. We then read your public profile and the list of your servers, to know which ones you can administer.
We keep no Discord token, neither access token nor refresh token: they are used once, at sign-in, then discarded. The session is then carried by a technical cookie, with a limited lifetime, unreadable by the page’s scripts. That cookie is strictly necessary: without it, you cannot stay signed in.
Why we process this data
On the basis of our legitimate interest in giving server administrators the tools they chose to install and in making them work properly, and in measuring our website’s audience to improve it.
We sell no data. We do no targeted advertising.
Who has access
Our technical providers, each for their own part:
| Provider | Role | What it receives |
|---|---|---|
| Discord | The platform itself | Everything passing through it, under its own policy |
| Cloudflare | Website hosting, asset storage, network protection | The site’s content, the stored assets, connection data |
| OVH | Server running the bots, the dashboard and their databases | The data described above |
| Website audience measurement | The browsing data described above |
We may also hand over data where the law requires it.
How long we keep it
| Data | Duration |
|---|---|
| Server configuration | Until you ask for its deletion |
| Moderation history | No limit, and not erased on request, see below |
| Assets | Until they are removed, with no preset duration |
| Detailed usage statistics | 90 days, then kept as totals with no identifier |
| Database backups | 7 daily and 4 weekly backups |
| Audience measurement cookies | 13 months |
What a deletion request does not erase
The data that holds a moderation sanction in place is not deleted: the sanction history and the temporary bans waiting to be lifted.
The reason is concrete. If asking for your data to be erased were enough to erase your sanction, asking would be all it takes to get around a server’s moderation. A temporary ban whose lifting date is erased becomes either permanent or non existent, and both are wrong.
We rely here on our legitimate interest, and on that of the servers we protect, in moderation decisions staying enforceable and verifiable. That interest outweighs, in our view, a person’s interest in making a sanction against them disappear. This data stays minimal: numeric identifiers, a sanction, a duration, a short reason.
You keep the right to contest a sanction. With the server’s administrators first, who can lift it themselves. With us next, at [email protected].
Your rights
The GDPR gives you the right to access your data, to have it corrected, to have it deleted, to restrict or object to its processing, and to obtain a copy of it.
To exercise them, write to [email protected] from the email address of your Discord account: that is what lets us find the data concerning you. We answer within one month.
The right to erasure has the limit set out just above: the data that holds a moderation sanction in place is not deleted. We answer you by stating precisely what was erased and what was not.
Transfers outside the European Union
The server running the bots, the dashboard and their databases is hosted in the European Union: that data does not leave it.
Cloudflare and Google, on the other hand, are American companies. The data entrusted to them may be processed outside the European Union, under the European Commission’s standard contractual clauses and the EU / US Data Privacy Framework.
Changes
We may update this page. The date at the top always shows the last change. A significant change will be announced on the support server.
Complaints
Our publisher being governed by Belgian law, the competent authority is the Data Protection Authority (APD/GBA), Rue de la Presse 35, 1000 Brussels. You can lodge a complaint there at any time, though we would be grateful if you wrote to us first.