Privacy policy
This policy explains what personal data Moud handles when you use this website, the Moud mod's catalog features, published games and the forum. It follows the EU General Data Protection Regulation (GDPR) and the French Loi Informatique et Libertés.
Who is responsible#
The data controller is EPI STUDIO, 22 allée du Loiret, 31770 Colomiers, France, reachable at contact@epistudio.fr. Moud is a project of the association EPI STUDIO. The association has not appointed a data protection officer.
Game creators decide what their own games store about players through Moud's scripting features (scores, progress, inventories). For that data the creator of the game is responsible for what is stored, and Moud stores it on their behalf.
What we collect and why#
Your account#
When you sign in, the Moud mod asks Mojang's session server to confirm you own your Minecraft account. We receive and keep your Minecraft id (UUID) and Minecraft name, and we create a site account with a handle made from your name, a role (member, reviewer, staff), the date you joined, the date you confirmed you are old enough to use Moud and whether you said you are 13 or 14 or 15 and older, whether you opted out of analytics, and your post and topic counts. We also keep your skin address from Mojang, and our server fetches your avatar from a Minecraft avatar renderer and keeps a copy for a few hours, so your browser never contacts that renderer. We never receive your Microsoft password, email or Microsoft tokens.
If you link a Discord account through the Moud Discord bot we keep your Discord id and name to show your badges there.
Legal basis: performance of the contract (the terms), article 6(1)(b) GDPR.
Signing in#
We keep session tokens: one in a cookie on the website and one for the Moud mod. Both last 30 days. Short lived sign in and link codes last about ten minutes and are deleted once used.
Legal basis: contract.
Forum and profiles#
We keep the topics and posts you write, their dates, edits, likes, what topics you have read, what you watch, reports you file and pictures or videos you upload into posts. Your profile page is public and shows your Minecraft name and avatar, your role, your bio, your badges, your topics and replies, the games you published and the games you marked as favorites.
When a post links to another site, our server fetches that page once to build a link preview (title, description, picture). The other site sees our server's address, not yours.
Legal basis: contract. Moderation (reports, mutes, bans and the staff log) is our legitimate interest in keeping the forum safe and lawful, article 6(1)(f).
Games catalog and publishing#
When you publish a game we keep its files, name, description, pictures, the versions you sent, the automatic checks run on them, and the reviewers' decisions and reasons. Published games are public. We keep your votes and favorites on games.
Legal basis: contract.
Studios, keys and webhooks#
If you make or join a studio we keep its members, their roles and pending invites. A studio's name and the games it lists are public; who its members are is not.
If you create API keys we keep each key's name, a hash of the key (never the key itself), its first characters, scopes, game, expiry and when it was last used. If you set up webhooks we keep the address and secret, and the last 50 deliveries per webhook with their content (version numbers, refusal reasons, crash counts, fleet names, badge counts, and for player reports only the reason and report number). Webhooks send that content to the address you chose, which can be a third party service such as Discord.
Legal basis: contract.
Playing games, friends and parties#
When you play through Moud we record:
- visits: which game you joined, which server, when, and whether you came from the home page, search, a friend or a link
- play sessions: when you started and were last seen on a game, and whether you came back after one and after seven days
- game badges you earned
- custom events a game reports through its analytics script, which we count per hour per game, keeping a per player marker for three days so each player is only counted once
- friends, friend requests, parties and invites, and whether your Moud client is open (your friends see if you are online, which game you are playing and whether they can join you)
- game data that games save for you. Games keep the last 20 versions of each saved value for 30 days so a lost save can be restored; the game's owner and developers can view and restore them. On a single server, outside a fleet, the server's own save file keeps the same history. Games can also keep short lived shared values for at most 45 days
- whether you joined a game's beta
- the region your Moud client measured as closest, while your client is connected
- whether your Moud client can be started from a
moud://link (only "Prism Launcher" or nothing), so the website knows whether to open one - a waiting join when you press Play or Join on the website while Moud is closed: the game, server, friend or invite it was for, used for three minutes or until your client picks it up
- a held seat for about two minutes on the server you were on when your connection dropped, so you can reconnect
- the highest age rating of games you chose to see
- when a game sends you to another game, the data the first game passes along (at most 4 KB) and which game you came from, kept with the join ticket
Creators see their game's analytics as totals and counts only (visits, players, sessions, events). They do not see a list of who played.
You can opt out of analytics on your account page. Once you do, we stop keeping visits, play sessions, play history and per player event markers under your Minecraft account; anonymous counters without your id (visit counts and where they came from, event counts, players and servers online) still include you. It takes effect within a minute. A Minecraft account that never signed in to the website counts as opted in.
Notifications, follows and synced settings#
We keep your notifications (friend requests, invites, badges, releases from creators you follow, review and takedown decisions), whether you read them, the creators and studios you follow and since when, and, if settings sync is on, your Moud settings (keybinds, graphics quality, interface size, code editor settings). Follower counts are public; who follows whom is not. Your profile shows the games you played recently only if you turn that on, and the game badges you pinned to your showcase.
Legal basis: contract.
Safety and moderation#
To keep games and the forum safe we keep:
- the players you block, and when
- bans from a game or from all of Moud: the player, reason, end time and who banned them
- player reports you file or that are filed about you: reporter, reported player, game, server, reason, an optional note and who handled it
- a moderation log of every staff and creator action, and of players a game's scripts kicked: who did what to whom, in which game and server, why and when
Text you send in games and on the forum can be checked by an automatic filter. The text is only held in memory while it is checked, never stored by the filter.
Games can read the block lists of the players on their own servers, so they can hide chat from people you blocked. The person you blocked is not told.
Legal basis: legitimate interest in keeping players safe and enforcing the community rules, article 6(1)(f).
Copyright notices#
When you send a copyright notice we keep your name, company, postal address, email, signature, the description of the work and of the infringement, and your account if you were signed in. Your name and email are shown to the creator of the content so they can answer. A counter notice keeps the creator's name, address, email, statement and signature, which staff pass on to the person who sent the notice. See Copyright.
Legal basis: legal obligation as a hosting provider, article 6(1)(c), and legitimate interest, article 6(1)(f).
Legal basis for playing games, friends and parties: contract. Analytics are our legitimate interest, and that of game creators, in knowing how games are used, article 6(1)(f). You can object, see below.
Crash reports#
When the Moud mod or a game server crashes it can send a crash report: the error and stack trace, the Moud version, the operating system and Java version, the place and game, and a keyed hash (HMAC) of the sender's network address used to count how many machines hit the same crash. The address itself is not stored, and the hash cannot be turned back into it without our secret key. A crash log can contain your Minecraft name or file paths from your computer.
Only Moud staff can read client crash reports. A game's creator can read the crash reports sent by their own game's servers, never those from players' machines.
Legal basis: legitimate interest in finding and fixing bugs, article 6(1)(f).
Security and abuse#
To limit abuse (sign in attempts, uploads, crash reports) we keep counters keyed by your network address or account for up to an hour; old counters are cleared about a day later. Our hosts keep their own technical logs, which include addresses.
Legal basis: legitimate interest in keeping the services secure, article 6(1)(f).
Third party content your browser loads#
The site's fonts, the 3D skin viewer and player avatars are served from our own server. Your browser still contacts other services, which then see your network address, in these cases:
- youtube-nocookie.com and vimeo.com when a post embeds a video
- pictures and videos that forum posts or link previews show from other sites
We do not use advertising, tracking pixels or analytics scripts on the website, and we do not sell or rent your data to anyone.
Who processes your data#
- Vercel Inc. (United States) hosts the website and stores uploaded forum pictures (Vercel Blob)
- Hyperion Cloud SAS (France) hosts the database
- Hyperion Cloud SAS (France, Rouen and Paris) hosts the Moud catalog server, game files and game servers run by Moud
- Mojang / Microsoft confirm your Minecraft account at sign in and serve your skin
- visage.surgeplay.com draws Minecraft avatars for our server from your Minecraft id; it sees our server's address, not yours
- Discord, only if you use the Moud Discord bot
Some of these are outside the European Union. Transfers to the United States rely on the EU-US Data Privacy Framework where the provider is certified, or on the European Commission's standard contractual clauses.
How long we keep it#
| Data | Kept |
|---|---|
| Website and mod sessions | 30 days |
| Sign in and link codes | about 10 minutes |
| Abuse counters with network addresses | up to a day after they expire |
| Account, profile, Discord link | while your account exists |
| Forum posts | until you or staff delete them, or you delete your account; a deleted post's text is erased at once, the empty entry stays so threads keep their shape |
| Pictures and videos uploaded into posts | deleted with the post that shows them, or with your account |
| Cached avatars | a few hours |
| Forum reports | while the forum exists, to handle repeat abuse |
| Player reports | 180 days after they are handled, 365 days if never handled |
| Game and Moud bans | until they end; the moderation log keeps the record |
| Moderation log | 2 years |
| Blocks | until you unblock |
| Copyright notices and counter notices | 3 years after the case is settled |
| Number of copyright removals against an account | while the account exists, to apply the repeat infringer rule |
| Notifications | the newest 200, at most 90 days |
| Follows | until you unfollow |
| Synced settings | until you turn sync off or forget them |
| Beta membership | until you leave the beta or the game is deleted |
| Studio memberships and invites | until you leave, or with your account |
| API keys | until your account is deleted, revoked keys included |
| Webhooks and their last 50 deliveries | until the webhook is removed |
| Old versions of saved game data | 30 days, the last 20 per value |
| Shared short lived game values | until they expire, at most 45 days |
| Grouped crash statistics | like crash reports, 90 days |
| Record that an account was erased | kept, holding only a hash of the account id and dates |
| Games, versions, review decisions | while the game exists |
| Game files and pictures you upload | while a game uses them, within a per player quota (10 GB by default); files no game uses are removed after 7 days |
| Visits, per player play history and play sessions | 13 months (396 days) |
| Hourly game analytics | 35 days |
| Per player event markers | 3 days |
| Daily game stats and daily event counts | kept, they are totals without player ids |
| Game badges, game data | while the game exists |
| Join tickets, with any teleport data | 1 day after they expire |
| Waiting website joins | used or dropped after 3 minutes, deleted within 6 hours |
| Invites | deleted within 6 hours of expiring |
| Crash reports | 90 days |
| Status checks | 90 days |
| Friends and parties | until you remove them |
When a game is deleted, its analytics, visits, badges and saved data are deleted with it.
Your rights#
You have the right to access your data, to correct it, to have it deleted, to restrict or object to its use (in particular to analytics and crash reports, which rely on legitimate interest), and to get a copy of the data you gave us in a common format.
Your account page does most of this yourself: download all your data as a JSON file, opt out of analytics, or delete your account. Deleting it erases the text of your posts (the empty entries stay so threads keep their shape), your uploads, likes, votes, favorites, badges, friends, visits and play history, takes down your games (games owned by a studio stay with the studio), revokes your API keys, removes you from your studios, deletes your notifications, follows, synced settings and blocks, and unlinks your Minecraft account. It also wipes every value games saved under your Minecraft id in every game, with your leaderboard scores and badges, and tells the servers of those games so they can clean up data they keep elsewhere. Reports you filed and moderation log entries stay, no longer tied to your name. The download includes your saved game data, scores, badges, notifications, follows, synced settings and copyright notices.
For anything else write to contact@epistudio.fr and tell us your Minecraft name; we may ask you to prove the account is yours, for example by sending a code from the Moud mod. We answer within one month.
You can also complain to the French data protection authority, the CNIL (cnil.fr, 3 Place de Fontenoy, TSA 80715, 75334 Paris Cedex 07), or to the authority of the country where you live.
Children#
Moud is not meant for children under 13. Under 15, or under the age of digital consent where you live, you need a parent's permission. When you sign in on the website you confirm this, and we keep the date you did; we refuse the sign in otherwise. If you think a child's data is here without that permission, write to contact@epistudio.fr and we will delete it.
Cookies#
The website only sets what it needs to keep you signed in. See the cookie policy.
Changes#
We will post changes here and update the date at the top. Important changes are announced on the site.