Privacy & Data Storage

At a glance

Jobs Lifetime synchronization

Jobs Lifetime synchronization is optional and is disabled by default. When enabled, the Suite server stores:

• Your Minecraft UUID and current player name
• The data-contract version and account creation and update timestamps
• A normalized server or realm key and your aggregate lifetime job earnings for that server
• For later earnings updates, a randomly generated event ID, server key, update amount, and server-received timestamp

The event ID lets the server recognize a retried update and avoid adding the same earnings twice. Consecutive local earnings may be combined into one pending update, so these records are synchronization events rather than a complete history of individual jobs.

The first time synchronization is enabled, existing client totals are uploaded only if the server has no Jobs Lifetime record for that Minecraft UUID. If a server record already exists, the server's totals are treated as authoritative and are loaded by the client.

This feature does not send the job type, job experience, play duration, raw chat or action-bar message, coordinates, inventory, or account balance. Jobs Lifetime totals are not broadcast through the live multiplayer relay or shown to other Suite clients. However, the highest totals are shown on the public website scoreboard; see Public scoreboard.

Disabling synchronization stops fetching totals and sending new updates. It does not delete the server-side account, totals, or previously accepted update records. Unsent updates remain in the local configuration and may be uploaded if synchronization is enabled again.

Local Jobs Lifetime storage

The client also keeps lifetime totals, the synchronization preference, and any unsent update IDs, server keys, and amounts in the Minecraft instance's Suite configuration. This local information remains when synchronization is disabled unless the user removes or resets the local configuration.

Shop Stats

Shop Stats is optional and is disabled by default. It reads the chat shop plugin's own trade messages: trades you make at another player's shop, and the notices you receive when someone trades with your shop (including notices delivered when you log in after trades made while you were offline). It also reads the auction house plugin's own messages: items you buy there, and the notice you receive when someone buys one of your listings while you are online. Messages typed by players are never read as trades. When Shop Stats is enabled, the Suite server stores, for each trade:

• Your Minecraft UUID and current player name
• A randomly generated event ID, the normalized server key, and whether you sold or bought, at another player's shop, at yours, or on the auction house
• The other player's name as shown in the message (the shop owner, the player who traded with your shop, or the player who bought your auction listing), when the message names one
• The item name, quantity, and total price as shown in the message
• When your client saw the message, when the server received it, and the network address it came from

With Shop Stats enabled, the client also sends the auction house's messages about your own listings: an item you list (with its asking price) and an item you take back. For each, the Suite server stores your Minecraft UUID and current player name, a randomly generated event ID, the normalized server key, whether it was listed or taken back, the item name, quantity, and asking price as shown in the message, when your client saw it, when the server received it, and the network address it came from. Listings are not trades: they are never added to your totals or shown on a leaderboard. They are kept so that typical prices can be worked out later, and are visible only to Suite administrators.

The server keeps running totals per server and per kind of trade (trades, items, money) and returns them to your client. When both players of a trade use Shop Stats, the two records are linked, and the trade counts as verified in both players' totals. Shop Stats money is kept separate from Jobs Lifetime and is never added to it.

Shop earnings and spending are shown on the public website leaderboards; see Public scoreboard. The other player's name stored with a trade is never shown publicly; it is visible only to Suite administrators reviewing records.

Disabling Shop Stats stops sending trades and takes every account that sent trades from that computer off the shop leaderboards. It does not delete trades or totals already stored. The client keeps the totals it has counted in its own shops.json file in the Minecraft instance's configuration folder, whether or not Shop Stats is enabled. Individual trades (including the other player's name) and auction listings are kept there only while Shop Stats is enabled and only until they are sent; trades and listings seen while it is disabled are never uploaded, and listings are not kept at all.

Player Stats

Player Stats is optional and is disabled by default. When it is enabled, the client periodically asks the server for your Minecraft statistics (the same numbers as Esc → Statistics, which the server keeps for you whether or not you use the mod) and sends the claim plugin's /claimlist command on its own, hiding that command's reply from chat. The Suite server stores:

• Your Minecraft UUID and current player name
• The normalized server key
• Your general statistics on that server, each above zero (for example distance walked, flown and ridden, jumps, time played, mob kills, deaths), plus the total number of blocks you have placed and mined there
• Your claim blocks earned from play, bonus claim blocks, and their total as /claimlist shows them
• At most once an hour per server, a history record of the headline numbers (time played, distance, blocks placed and mined, claim blocks) with the time the server received it and the network address it came from

It does not send your coordinates, claim locations, inventory, chat, or balance. Statistics per item (other than the placed and mined totals) and per mob are not sent. Uploads that look impossible (for example more distance than the play time allows) are recorded and flagged for an administrator to review; they are not refused.

Distance traveled, blocks placed and mined, time played, and claim blocks from play are shown on the public website leaderboards; see Public scoreboard. /bsuite stats shows your own numbers in game, and works once without Player Stats enabled; those numbers are then not sent.

Disabling Player Stats stops reading and sending statistics, and takes every account that sent statistics from that computer off the leaderboards. It does not delete statistics already stored.

Job Levels & Overflow XP

Job Levels & Overflow XP is optional and is disabled by default. Whether or not it is enabled, the client reads the Jobs plugin's /jobs stats now and then (and when you run it yourself), hiding the automatic reply from chat, and counts the XP you earn in a job that is at the max level (200) as Overflow XP on your computer. When it is enabled, the Suite server stores:

• Your Minecraft UUID and current player name
• The normalized server key
• For each job: your level, your XP and the XP needed for the next level, whether the job is at the max level, and when the server received it
• Your Overflow XP per job: the total you earned on 1.0.0 (nothing is read from other mods; everyone starts at zero)
• Each batch of Overflow XP the client sends (a random batch ID, the job, the XP, and when the server received it), so a batch sent twice is counted once and a day's total can be worked out

It does not send your balance, coordinates, inventory, chat, or jobs money. A job that rises more than 25 levels between readings, more than 5,000,000 Overflow XP in a day, or a brought-over total of 50,000,000 or more is recorded on your account and flagged for an administrator to review; it is not refused.

Your job levels added up, and your Overflow XP, are shown on the public website leaderboards; see Public scoreboard.

Disabling Job Levels & Overflow XP stops sending levels and Overflow XP, and takes every account that sent them from that computer off those leaderboards. It does not delete what is already stored; your Overflow XP keeps counting on your computer.

HUD Cloud Save

HUD Cloud Save is optional and is disabled by default. It keeps your HUD Builder layout with your account so every PC you play on has the same HUDs. When it is enabled, your layout is saved to the Suite server when you leave the HUD Builder or change your HUDs another way (moving them, or a HUD switch), and each time you join a server the client compares your saved copy with the one on your PC and brings the older one up to date. If both changed, the newer one is kept, and the cloud copy that was replaced is kept on your PC as a backup file. When your PC's HUDs replace the saved copy or the saved copy replaces them, the HUDs that were on your PC are also kept as a backup file. An automatic save only replaces the copy your PC last saw: if another PC saved in the meantime, the two are compared again instead. The first time a PC syncs (or another account syncs on it), if the two copies differ, you are asked which to keep when you next open the HUD Builder; until you choose (Decide Later asks again when you next join a server), nothing is saved automatically. A copy saved by a newer version of the mod is never replaced automatically. Failed saves are tried again a minute later (five minutes when the PC isn't signed in yet or too many tries were made). HUD Cloud Save needs your account to be signed in (see Signing in), and pauses on a PC while your account is signed in on another one. The Save to Cloud and Load from Cloud buttons in the HUD Builder's Share tab do the same on demand, whether or not HUD Cloud Save is enabled. With HUD Cloud Save enabled, or once you have used one of those buttons on that PC, opening the Share tab while on a server asks, once per game session (or again a minute later if that check fails), whether you have a saved copy and when it was saved. Each of these requests sends your UUID, player name and player key, as the other online features do, plus the sign-in session when there is one. The Suite server stores:

• Your Minecraft UUID and current player name, the mod version, and the time saved
• Your HUD Builder layout: every profile and HUD, their lines, colours, positions and image file names, and which built-in HUDs are switched on

Image files you use on a HUD are never uploaded; the layout only names them. The network address a request comes from is used to limit how often saving can be tried and isn't kept with your layout (requests are logged as described in Security records and logs). Disabling HUD Cloud Save stops the automatic saving and loading but keeps the saved copy. To have it removed, contact Suite support (see below); with HUD Cloud Save still enabled, your next change to your HUDs saves a new copy, and so does a PC that has never synced when it next joins a server.

Public scoreboard

The SuiteCore website shows public leaderboards for each suite:

• Job earnings, from Jobs Lifetime synchronization records. If you have enabled Jobs Lifetime synchronization and your total is among the highest, you may appear on it.
• Distance traveled, blocks placed, blocks mined, time played, and claim blocks from play, for players with Player Stats enabled.
• Shop earnings and shop spending, and auction house earnings and spending, for players with Shop Stats enabled.
• Job levels (every job's level added up) and Overflow XP, for players with Job Levels & Overflow XP enabled.

For each listed player, a leaderboard publicly shows:

• Your current Minecraft player name
• Your rank and total for each server or realm key, and a combined total across them
• The server or realm key the total belongs to

The leaderboards do not show your Minecraft UUID, update history, timestamps, individual trades, the other players in your trades, job type, balance, or any other stored data. They are read from the records described above; no additional player data is collected to produce them. Results are refreshed about once a minute.

For the Player Stats, Shop Stats, and job levels and Overflow XP leaderboards, the server looks up the name that belongs to your Minecraft UUID with Mojang's public profile service, and shows that name rather than one sent by a client. The lookup sends only your UUID to Mojang. The result, its status, and when it was checked are stored, and it is checked again about once a week.

To appear on those leaderboards, your account must also be confirmed as yours, once. Signing in (see Signing in) does this. If signing in hasn't worked, while Jobs Lifetime, Shop Stats, Player Stats, or Job Levels & Overflow XP is enabled, the mod does what the game does when you join any server: it receives a random server ID from the Suite server, tells Mojang's session service that your logged-in account is joining that ID, and the Suite server then asks Mojang which account joined it. Your Minecraft login is only ever sent to Mojang, never to the Suite server. The Suite server stores your UUID, the name Mojang returned, when it was confirmed, and the network address the confirmation came from.

Disabling Player Stats, Shop Stats, or Job Levels & Overflow XP takes you off those leaderboards. Disabling Jobs Lifetime synchronization stops new updates but does not delete your stored total, so it does not by itself remove you from the job earnings scoreboard. To be removed from it, contact Suite support through the official Discord link below.

Emotes and cosmetics

Emote preference synchronization is optional. Cosmetics & Wardrobe is a separate consent category: accepting it is required to use those features. When a category is enabled, the corresponding selected information is saved in the Suite database.

Emotes

• Minecraft UUID and current Minecraft player name
• Default forward movement style, backward movement style, and flying style
• Favorite emote IDs
• Contract version and last-updated timestamp

Only the latest configuration is kept; there is no history of preference changes in this backup.

Cosmetics & Wardrobe

• Minecraft UUID and current Minecraft player name
• Contract version and last-updated timestamp
• Up to 512 collected cosmetic entries
• Equipped cosmetic layers and whether equipped armor is hidden
• Global tool cosmetic defaults and specific held-item replacement rules

Each collected entry can include its cosmetic ID, armor or tool category, source item identity, display name, render anchor, and a serialized Minecraft ItemStack. That stack may contain its base item type, custom item ID (including ExecutableItems identifiers), custom model data, item model, display name, lore, enchantments, attribute modifiers, custom components, and metadata added by server plugins.

Wardrobe Vault

When Cosmetics & Wardrobe is enabled and a player assigns a Wardrobe Vault, the Suite server stores:

• Minecraft UUID and current player name
• Realm key and dimension identifier
• The exact block coordinates of both halves of the assigned double chest
• Creation and last-update timestamps
• Up to 54 cosmetic IDs currently observed in the wardrobe

The server stores cosmetic identifiers for the wardrobe contents, not the chest's complete ItemStack data or item quantities. Complete serialized item information may separately exist in the player's collected-cosmetics backup as described above.

To identify and protect claimed wardrobes, authenticated Suite clients requesting wardrobe information for the same realm and dimension can receive claimed chest coordinates together with the owner's Minecraft UUID and player name.

Moving a wardrobe replaces the previous assignment and usable-item list. Unassigning it deletes the assignment and associated cosmetic-ID list.

Read the Vaults guide →

Live multiplayer relay

Other connected Suite clients need temporary state to show your emotes and equipped cosmetics. Emote relay authentication can occur while all three server-backed categories are disabled. Active cosmetic relay data applies when Cosmetics & Wardrobe is enabled.

• Minecraft UUID and current player name
• Current realm or server key
• Currently playing emote
• Active cosmetic loadout and hidden-armor selections
• Tool replacement rules
• While Show My Suite Tag (Settings → Visuals → Suite Look) is on, which it is by default: that you use the mod, and the name style you chose (its colours, mode, speed, bold and italic), so other Suite players can show them in their Tab list and over your head; and, while Show My Lifetime is also on (also by default), the API adds your Jobs lifetime on the server you're on (the number already on the leaderboard, never if an admin hid you from the leaderboards) so it can show under your name

Turning Show My Suite Tag off stops sharing that and removes it from other players' Tab lists and name tags; turning Show My Lifetime off keeps only the lifetime back. This state stays in server memory and is removed when you disconnect. It is broadcast only to other connected Suite clients in the same configured realm. Your complete cosmetic collection is not broadcast; only active cosmetic stacks and replacements are sent.

Emote usage counts

When an emote is played manually, an aggregate counter records the emote ID, total play count, and first- and last-played timestamps. The counter does not contain Minecraft UUIDs, player names, IP addresses, or individual play histories. Walking, running, and flying styles do not contribute to these counts.

Player authentication

The live relay and player configuration endpoints use an authentication key for each Minecraft UUID. The server stores the UUID, a SHA-256 hash of the key, and its creation and last-used timestamps. It does not store the raw key.

The raw key is kept on your computer outside the Minecraft instance, so reinstalling an instance does not normally remove it. On Windows, the file is %APPDATA%\BlossomSuite\player-auth.json for both BlossomSuite and MysticSuite. Keys are separated by suite and Minecraft UUID so multiple accounts can be used.

Authentication enrollment currently occurs when the client connects to the live emote WebSocket, even if all three optional server-backed categories are disabled.

Signing in

While HUD Cloud Save, Jobs Lifetime, Shop Stats, or Player Stats is enabled (or once you have used the HUD Cloud Save buttons on that PC), or when you use /bsuite signin, the mod signs your account in when you're on a server: about once each time you start the game, and again every 12 hours. It does what the game does when you join any server: it receives a random server ID from the Suite server, tells Mojang's session service that your logged-in account is joining that ID, and the Suite server then asks Mojang which account joined it. Your Minecraft login is only ever sent to Mojang, never to the Suite server. When Mojang confirms the account, the Suite server:

• Marks this PC's authentication key as confirmed for your account, with the time (adding it as one of your account's PCs when the account already has a key). Keys are never removed by signing in.
• Issues a session: a random token the mod keeps in memory only and sends with its requests for 12 hours. The server stores your UUID, a SHA-256 hash of the token (never the token itself), the hash of the key it belongs to, and when it was created, last used, and runs out.
• Stores the account confirmation and the name Mojang returned, as described under Public scoreboard.
• Records the sign-in in your account's history: the time, the start of the key's hash, whether another PC's session ended, and the network address and client (user-agent) it came from.

Your account has one session at a time: signing in on one PC ends the session on any other. If Mojang doesn't confirm the account (another account joined, or none did), the attempt is recorded as a security event (see Security records and logs). If Mojang's service isn't answering, nothing is stored in the database (the service journal may note the failed check with your UUID, as described in Security records and logs), and your PC carries on with its key. The random server ID is only kept in memory, for at most two minutes.

Security records and logs

If someone submits an invalid UUID or incorrect authentication key, the Suite database records the event timestamp and type, API route, claimed UUID and player name, direct source IP address, X-Forwarded-For value, and user-agent string. Valid requests are not written to this security-events table.

Separately, the reverse proxy, hosting provider, or service journal may log ordinary requests and IP addresses depending on its deployment configuration. Those logs are outside the application database.

The Suite service also keeps its own log of requests for 14 days: the time, the route, the network address, the client, and the player a request names. Suite administrators use it to investigate problems and abuse, including to see when more than one account is used from the same network address (for example, to check on alternate accounts or to contact the players involved). Only requests whose player key was accepted are compared, and the comparison is never shown publicly.

Visits to this website are counted from the web server's own log, with no cookies or tracking scripts: how many times each page was viewed, the site a visit came from, and how many people visited each day. To tell visitors apart within a day, the server keeps a scrambled code made from the network address and browser (never the address itself). The codes are deleted after a few days, and only the daily totals are kept.

Other Suite data

The Suite service also keeps data unrelated to the three server-backed categories.

Dungeon reporting BlossomSuite only

• Reporter UUID and name; player UUID and name; party member names; and names of players who lost lives
• Server and dungeon, start and end times, duration, completion status, cooldown times and reasons
• Client run IDs, merge keys, nonces, and received timestamps

Donation reports No longer collected

Versions before 0.9.10 detected in-game payments to the mod author and reported them. Current versions don't detect or send donations. Reports received before then are kept and contain:

• Player UUID and name, realm, and donation amount
• Raw detected message and whether a command was used
• Nonce and received timestamp

Cooldown requests

Sent only when you use /bsuite cooldown request and press Send Request, to ask for a cooldown timer on an item that doesn't have one. The request is reviewed by the mod author, and /bsuite cooldown requests shows you its status and any reply.

• Your UUID and player name, the server you were on, the mod version, and the time sent
• The held item as the mod saw it: its item ID, ExecutableItems ID, count, name, tooltip text, and full item data (its components, which can include any custom data the server put on it)
• Which actions on the item already had a cooldown, and your answers: the action, the cooldown length, where the item is when used, how you know the cooldown, and your notes
• The IP address the request came from, used only to limit how many requests can wait from one address
• The review: its outcome, time, the reply shown to you, and the cooldown rule added if it was approved

Linked-account cooldown relay

• Link ID, realm, alternate-account name, and cooldown payloads
• Update and expiration timestamps and last nonce

Stale cooldown records are automatically removed after seven days or after their maximum expiration plus a six-hour grace period.

Vote-party state

• Server key and display name, current and maximum votes
• Whether a party or countdown is active, countdown or trigger timing
• Update timestamp and nonce

This is global server state, not an individual player profile.

Retention and your choices

Current application behavior:

• Emote backups remain until replaced or manually deleted.
• Collected-cosmetics backups remain until replaced or manually deleted.
• Disabling Cosmetics & Wardrobe clears the active loadout and removes the Wardrobe Vault assignment, but retains the collected-cosmetics backup.
• Wardrobe assignments and usable cosmetic IDs otherwise remain until replaced, unassigned, or manually deleted.
• Jobs Lifetime accounts, per-server totals, and accepted update events have no automatic retention limit.
• Disabling Jobs Lifetime does not delete its stored records.
• Shop trades and shop totals have no automatic retention limit, and disabling Shop Stats does not delete them.
• Player Stats statistics and claim blocks have no automatic retention limit, and disabling Player Stats does not delete them. Their history records are kept in full for 90 days; after that, one record per day per server is kept (records flagged for review are always kept).
• Job levels, Overflow XP totals, and the Overflow XP batches have no automatic retention limit, and disabling Job Levels & Overflow XP does not delete them.
• Account confirmations have no automatic retention limit.
• Leaderboard name checks are kept while you are on a Player Stats, Shop Stats, or job levels and Overflow XP leaderboard and are refreshed about weekly.
• Authentication hashes remain until manually deleted or reset. A reset removes your account's main key and the sign-in confirmation of its other PCs (they keep their keys and are confirmed again at their next sign-in).
• A sign-in session is replaced at your next sign-in and ends when your key is reset or your account is banned; one that has run out (after 12 hours) is deleted within about an hour. Sign-in history records have no automatic retention limit.
• Security events and aggregate emote counts have no automatic retention limit.
• Dungeon reports and earlier donation reports have no automatic retention limit.
• Cooldown requests, including their item details and review, have no automatic retention limit; they are the record of what was asked for and decided.
• A HUD Cloud Save copy is kept until a newer one replaces it or it is deleted at your request; disabling HUD Cloud Save does not delete it. After a delete, a new copy is saved when you next change your HUDs with HUD Cloud Save enabled, or when a PC that has never synced joins a server. Backup files on your PC are kept five at a time for each kind.
• Vote-party records are overwritten by newer server state.
• Linked-account cooldown relay records have automatic cleanup as described above.

There is no general self-service export or full-account deletion endpoint. Wardrobe unassignment is the limited self-service deletion action currently available. You can request manual deletion of other stored player data after completing account-ownership verification. Contact Suite support through the official Discord link below. Avoid posting authentication keys or other sensitive data publicly.