Sandbox and privacy
What the sandbox blocks, why untrusted instances use it by default, its switches, and the stand-in sign-in token.
Mods are programs, and a launcher runs them. The sandbox plays an instance so its mods only reach that instance, Java, Minecraft's shared files and the folders you allow, and never your Microsoft sign-in.
Where it runs today: on macOS it is tested with a real Java program. The Windows and Linux sandboxes are written and still being tested, and it is still being tried with real games on every system.
Untrusted instances, by default #
An instance is untrusted when you imported it, or added mods to it by hand. By default those play sandboxed; instances made in the launcher from Modrinth don't need to. Settings > Privacy > Sandbox the game chooses:
| Choice | What happens |
|---|---|
| Untrusted instances (default) | Untrusted instances play sandboxed. Where the sandbox can't run, they play without it rather than not at all. |
| Always | Every instance plays sandboxed. Where the sandbox can't run, the launch is refused. |
| Off | No instance is sandboxed. |
Each instance can decide for itself in its Options: Sandbox this instance is Default, On or Off. On also refuses to start where the sandbox can't run; the message has a Sandbox options button. The instance's header shows Sandboxed, or Sandbox unavailable.
The switches #
| In Settings > Privacy | Default | For |
|---|---|---|
| Internet | On | Servers, and mods that download. Off, the game can only reach the launcher's sign-in stand-in. |
| Microphone | On | Voice chat mods |
| Discord | Off | Rich Presence mods |
| Your Downloads folder | Off | Mods that open or save files there |
| Your Documents folder | Off | The same, for Documents |
| Other folders | None | Any folder you add |
What the game can reach #
- Read and write: the instance's game folder, shared skins, a home folder of its own, a temporary folder for each launch, and the folders you allowed.
- Read only: Java, the game's libraries and assets, and the launcher's shared mod store.
- Not at all: the rest of your files, the launcher's own records about the instance, and other apps. On macOS nothing opens through the system, so links and Open folder buttons inside the game don't work while sandboxed.
- A short list of environment variables, and a mark mods can check:
INSIDE_VOXELSPROUT_SANDBOX=1.
Before a sandboxed launch, the launcher checks that the game folder is a real folder and doesn't overlap Java, its shared files or the sandbox home; otherwise the launch is refused. It never follows a link the game planted.
The stand-in sign-in token #
- A sandboxed game gets a dummy token, not your real one.
- Its sign-in requests go through a small proxy inside the launcher, on your own computer, behind a secret that changes every launch.
- The proxy swaps in the real token only for four fixed Mojang and Microsoft servers, and only for what a game does: joining and checking servers, profiles and skins, chat signing, privacy settings, the blocklist, reports and name lookups.
- Changes to your account (name, skin, cape) are refused. So is Realms, which doesn't work sandboxed.
Other privacy #
- Links never install anything: a
voxelsprout://link, or amodrinth://link if you allow them, opens a page, and you click Install. - Logs hide tokens, e-mail addresses and IP addresses before they are shown or uploaded.
- Crash analysis by mclo.gs sends the log to a third party, so it is off until you turn it on. The launcher's own crash hints always run on your computer.
- Report a problem is for the launcher's own problems, and only sends when you click Send. Minecraft crashes caused by mods are never sent.
- No ads.
Something missing or wrong on this page? Say so on Discord.