The short version
- MC² never sees your Microsoft password. You sign in on Microsoft's own page, in your own browser.
- Your sign-in is kept in the system's secret store: the login Keychain on Mac, Credential Manager on Windows.
- The token that launches Minecraft never goes to MC²'s backend. The backend learns who you are by asking Mojang.
- The Mac app is signed and notarized by Apple, and every update on Mac and Windows is cryptographically signed. MC² refuses an update whose signature does not check out.
- Game files, Java and mods are checked against the hashes their source publishes. A file that does not match is thrown away.
- A shared pack is a list, not a bundle of files. Your friend's MC² downloads each mod from Modrinth or CurseForge itself.
- No analytics, no ads, no tracking SDKs.
Signing in
MC² uses Microsoft's device code sign-in. MC² shows you a short code, opens Microsoft's page in your browser, and you type the code there. Your password and any two-step check happen between you and Microsoft. MC² has no password field for your Microsoft account, and nothing to store one in.
What MC² gets back is a token. It trades that with Xbox Live and Minecraft's own services for the token that launches the game, exactly as the official launcher does.
How MC²'s backend knows it is you
The online features (friends, capes, Cubes, sharing) need MC²'s backend to know which Minecraft account you are, without ever being handed your game token. It works the way a Minecraft server checks a player:
- The backend sends a one-time challenge. It is random, works once, and runs out after 2 minutes.
- MC² tells Mojang directly. Your game token goes to Mojang's session server, the same place it goes when you join any server, along with a hash of the challenge.
- The backend asks Mojang who answered. If Mojang confirms your account, the backend gives MC² a session that lasts 14 days. MC² keeps it in memory only and never writes it to disk.
The backend refuses requests without a session, and refuses a session used for a different account than the one it was issued to.
Where your sign-in lives
- Mac: the login Keychain.
- Windows: Credential Manager, for your Windows user on this PC only. It does not roam to other PCs.
That holds the Microsoft refresh token and the Minecraft token for each account. MC²'s own account list keeps only your username, your Minecraft and Xbox ids and when the token expires. MC² clears the tokens out of that file before writing it, and only your user can read it. If the secret store ever refuses a save, the token stays in that file until a later save works. Keys you add for MC²'s AI features go in the same secret store.
Keeping tokens out of MC²'s folder means they are not in its backups, not in anything you share, and out of reach of plugins.
Signing out deletes both tokens for that account from the Keychain or Credential Manager, and MC² drops its backend session.
What leaves your computer
Your worlds, screenshots, recordings, settings, keybinds and logs stay on your computer unless you choose one of the features below. The privacy policy lists everything MC²'s backend keeps and for how long.
| When | What goes to MC²'s backend |
|---|---|
| While you are signed in | Your Minecraft id and username. Your status for friends, such as Playing and the pack's name. Once a day, the ids of the plugins you have switched on, to count players. While you play, active minutes for Cubes: only whether a key or the mouse was touched in the last minute. |
| When you use a feature | Chat, friend requests and pack invites. A shared pack's recipe. Your cape. A profile you publish. A backup of your pack list. Your server's console, if you open it on your phone. |
| When you send a bug report | Your message, your username, MC²'s version and your OS, and the end of your last game log (see Telemetry). |
| Never | Your Microsoft password, your game token, your worlds and your files. |
MC² also talks to the services its features need: Microsoft, Xbox and Mojang, Modrinth and CurseForge, GitHub for updates and plugins, and Stripe if you buy a rank. Payment happens on Stripe's page, and MC² never sees your card.
Telemetry
MC² contains no analytics, crash reporting or advertising SDK. The only reports it makes on its own are the three in the first row above: your status for friends, the daily count of switched-on plugins, and Cubes minutes.
Crashes are never uploaded by themselves. A bug report goes only when you send one from Report a bug. It includes up to the last 48,000 characters of your newest game log unless you untick Attach the last game log. A game log can include your username and the paths on your computer, so read it if that matters to you. Reports are kept for 180 days.
The game servers MC² runs for you have their own telemetry switched off.
Releases and updates
Mac
The Mac app is signed with an Apple Developer ID, built with the hardened runtime, notarized by Apple and stapled, so it opens without a warning. You can check it yourself:
spctl -a -vv /Applications/MC².app
# accepted
# source=Notarized Developer ID
Windows
The Windows installer is not code-signed yet, so Windows may warn the first time you run it. Download it only from getmc2.com or MC²'s GitHub releases.
Updates
Every update, on Mac and on Windows, is signed with MC²'s private Ed25519 key. The matching public key is built into the app.
- Mac updates through Sparkle, set to verify the signature before it unpacks anything.
- Windows refuses an update with no signature. It checks the download's size and signature before unpacking, then checks that the version inside is the one announced and newer than yours, so an old release cannot be passed off as an update.
The release script refuses to publish an update feed without signatures.
Downloads
When a source publishes a hash for a file, MC² checks the download against it. A file that does not match is deleted and the install stops. MC² does not retry a mismatch or keep a file that failed.
| What | Checked against |
|---|---|
| Minecraft, its libraries and assets | Mojang's SHA-1 hashes |
| Java, when MC² installs it | Mojang's SHA-1 hashes, and every file must land inside the Java folder |
| Mods, resource packs and shaders from Modrinth | Modrinth's SHA-1, when Modrinth lists one |
| Mods from CurseForge | CurseForge's SHA-1. A file without one is refused. |
Files listed in a .mrpack | The pack's SHA-1, over https. A file without both is not downloaded. |
| Forge and NeoForge installers | The SHA-1 published beside them |
| Vanilla, Paper, Folia and Mohist servers | The hash the project publishes |
| Pumpkin | SHA-256, checked again before each start |
| cloudflared and playit | A version and SHA-256 fixed inside MC², checked again before every run |
A few projects publish no hash for their files. These include the Fabric and Quilt server launchers, Purpur, Sponge, Arclight, Geyser, Floodgate and Spigot's BuildTools. MC² downloads them over https only.
Every download refuses a redirect from https to plain http.
It means you got exactly the file Mojang, Modrinth or CurseForge published, unchanged on the way. It cannot tell you whether a mod's author meant well.
Plugins
- Plugins are sandboxed. Each one runs in a hidden web page of its own, apart from the app. It cannot load anything from the internet, open sockets or run code from elsewhere.
- You approve its permissions first. A plugin can only call what it declared and you allowed. An update that wants more asks again.
- Network is a permission. A plugin with it can reach public web addresses through MC². Addresses on your own network, like
localhost,192.168…or.localnames, are refused when written as such. - Plugins in Browse are reviewed by a person. Approval pins the exact files by SHA-256, and MC² refuses a file that does not match. A plugin found harmful can be switched off on every computer.
- A plugin from anywhere else is marked Unreviewed. Installing one by its GitHub address skips review.
What a plugin does with the network permission is up to its author. The developer guide has every rule.
Servers and your network
- Nothing is opened to the internet unless you ask. MC² asks your router to forward a port only when you click to open a server.
- Servers check accounts. New servers start with Minecraft's online mode on, so players must own the game and be who they say.
- The phone console link is the key. It carries a random 100-bit id, and anyone with the link can run console commands, so share it only with yourself. It stops working after 6 hours unused.
- Remote Play stays on your local network and needs a random key that changes each session. Its traffic is not encrypted, so use it on a network you trust.
What this does not promise
No software is completely secure, and MC² does not claim to be. Some things are outside what it can protect:
- Mods and plugins are written by other people. A verified download is the file its author published. MC² does not scan what that code does.
- Software already running as you. Anything running under your user account can reach what you can, including MC²'s folder and your sign-in.
- Other services. Microsoft, Mojang, Modrinth, CurseForge, GitHub and Stripe each keep their own security.
Deleting your data
- On your computer: sign out to remove your tokens. Delete MC² and its folder to remove everything else.
- Your cape: remove it in the app.
- Everything the backend holds about your account: there is no button for it yet. Open an issue or ask on Discord with your Minecraft username, and it will be deleted by hand.
Reporting a vulnerability
Found a security problem in MC², its website or its backend? Report it privately, not in a public issue:
Only MC²'s maintainers see the report. Say what you found, how to reproduce it, and which version of MC² you were on.
Please give us time to fix it before you talk about it publicly, and do not access other players' accounts or data while testing.