Privacy

What this covers

voxelsprout.com, its tools and generators, the marketplace, and the online features my mods use, such as signing in and build sync.

When you just visit

You can use the site, the generators and the marketplace without an account. What is kept then:

• Analytics. Visits are counted with Umami, which runs on my own server. It uses no cookies and does not store your IP address. It records the page, the page you came from, your browser, operating system, screen size, language and country.
• Session recordings and heatmaps. Some visits are recorded through the same Umami install: page changes, scrolling, mouse movement and clicks. I use them to find bugs and parts of the site that confuse people. Account details are masked in these recordings.
• Server logs. The server keeps technical logs to find errors and abuse. Your IP address is used for rate limiting, which only holds it in memory for a short time.
• Your browser's storage. Some tools, such as the tree generator, keep your settings and saved presets in your browser's local storage. That stays on your device and is not sent anywhere unless you sign in and save it to your account.

When you use a mod

When my mods talk to voxelsprout.com (to browse the marketplace, fetch trees or sync a build), they say which mod is asking, its version, the Minecraft version, the mod loader and your operating system's name. Not your Minecraft username, UUID or the server you are on. Bug reports send more, and only when you choose to; see below.

When BuildPrint lists the marketplace, it also sends the ids of the installed mods that add blocks or entities (such as create), so it only shows builds you can place in your game. That list is used to filter the results of that one request and is not stored, logged or tied to you. You can still see every build: the line under the categories shows the ones for other mods.

When you have an account

Signing in

Sign-in goes through Microsoft. From Microsoft I receive your name, email address and account ID, plus the sign-in tokens Microsoft hands back. Your email is not shown to other people. You also pick a username, which is public.

Each download of a build is recorded with when it happened and where from (the website, the BuildPrint mod with its version, or something else), so creators can see how their builds do. To count how many different people downloaded a build, the record carries your account id, or when you are not signed in a salted hash of your address and browser; neither your address nor your browser is stored as such, and nothing in these records is shown to anyone. Visits to a build page or a creator page are counted per day, without anything about who visited.

Your creator profile is public too: the display name, bio, links and avatar you choose to add, and the Minecraft username when you use its skin as your avatar. All of it is optional and you can change or remove it on your profile page.

Sessions and linked devices

For every browser or game client signed in to your account, the server keeps the IP address it signed in from, its user agent, and when it was last used. For a mod signed in to your account that also includes the mod version, Minecraft version and platform it reports. The account itself records when it was last used and whether that was from the website or a mod. You can see all of this and sign any session out on your account page.

Marketplace

When you upload a build, the file, its title, description, tags, pictures and the author name you give are stored and shown publicly. Votes and reports you make are stored with your account so they count once. Download counts are kept per day and per build, not per person.

Generators

Presets you save to your account in the generators are stored with your account.

Build sync

When you start or join a build sync session, the server stores what the session needs to keep everyone in step: the session name, the builds in it (file, name, which world and where it is placed, rotation, material swaps, building progress and who last reported it), and files shared in it. To tell worlds apart on servers with several worlds behind one address, it also stores a sample of the bedrock pattern under each build. Anyone with the invite code can see the session.

Bug reports from the mods

My mods can send a bug report, a feature request or a crash report to voxelsprout.com. Nothing is sent until you press Send on the report screen, and you can open and read every attachment before you do: what you see there is exactly what is sent.

A report can hold:

• what you type: the title, what happened, and a contact name if you add one
• which mod and version it is about
• your system: Minecraft, loader and Java versions, operating system, processor, memory, graphics card and driver, window size and GUI scale
• your mod list with versions, and the shader pack's name
• the mod's own state, such as how many schematics are loaded
• the game log and, after a crash, the crash report. Before sending, the mod removes chat lines, your player name and UUID, your home folder, world and server names, IP addresses, email addresses and anything that looks like a password or token. The site removes the same things again when the report arrives.
• a screenshot, only if you switch it on. It is off by default, because it shows your screen as it was, chat and names included.

Your IP address is used to limit how many reports one connection can send, held in memory for a short time, and not stored. The mod also sends a random install id so repeated reports of the same problem from one game count once; it is stored only as a keyed hash, which can count installs but can't be matched with anything else.

If you are signed in, the report is linked to your account, so an answer can reach you as a notification. If not, it is anonymous. Reports are read by me. A short summary (the kind of report, the mod and version, the title, the first lines of the description, and the Minecraft, loader, operating system and graphics card) is posted in a private Discord channel so I see new ones; logs, crash reports and screenshots are never posted there.

Full reports are deleted after 180 days, or 60 days after a problem was marked fixed and stopped coming in. What stays after that are counts per version and per kind of system, which hold nothing about you. You can delete a report yourself from the game (the Sent tab of the report screen), or ask on the Discord with its report id (it looks like R-7K3F9Q).

Cookies

One cookie keeps you signed in. That is it: no advertising or tracking cookies, and analytics works without cookies.

Who else sees your data

• Other people see what is public by design: your username, your uploads and their author name, and the contents of sync sessions they have the code for.
• Microsoft handles sign-in. Their own privacy terms apply to your Microsoft account.
• Discord carries the short summary of each new bug report to a private channel, as described above.
• Moderators can see account details and reports when handling a report or abuse.

Nothing is sold, and nothing is shared for advertising.

How long it is kept

• Account data: until you delete your account.
• Sign-in sessions: until they expire or you sign them out.
• Build sync sessions: they close on their own after 90 days with nobody connected.
• Files shared in build sync: removed after 30 days without use.
• Uploads: until you or a moderator delete them, or you delete your account and choose to delete them too.
• Bug reports from the mods: 180 days, or 60 days after the problem was fixed and stopped coming in.

Deleting your data

You can delete your account at any time from your account page under Danger zone. No email, no waiting period, no asking. Deleting it removes:

• your account, name, email and username, and the link to your Microsoft account
• your creator profile: display name, bio, links and avatar
• your notifications and notification settings
• every session and linked device, so your mods are signed out as well
• your votes and reports
• bug reports you sent from the mods while signed in
• presets you saved in the generators
• your marketplace uploads, files and pictures included, if you choose to delete them

If you choose to keep your uploads, they stay on the marketplace under the author name you gave them, but are no longer linked to any account.

Build sync sessions you started are shared with other people. If a session has admins with an account, the one who has been admin longest becomes its owner and the session carries on without you. If it has none, the session ends with the builds in it, and anyone still connected is told. Builds you added to someone else's session belong to that session and stay in it, no longer linked to you.

Files shared through build sync are stored by a hash of their content, so a file several people share is stored once and is not tied to any one of them. They are removed after 30 days without use.

You can also delete a single upload any time from its page, and saved presets from the generator.

Seeing or correcting your data

Most of what is stored about you is on your account page, and you can change or delete it there. If you want a copy of your data or something is not covered there, get in touch below.

Changes and contact

When this page changes, the date at the top changes with it.

Questions or requests: the VoxelSprout Discord.