MC Planner

Privacy policy

Last updated:

This page explains which personal data MC Planner processes, why, how long we keep it, and what your rights are under UK data protection law (the UK GDPR and the Data Protection Act 2018) and, if you live in the EU, the EU GDPR. The article numbers below are the same in both.

The short version

1. Who is responsible

MC Planner is made by Lab43. Lab43 is a trading name of Robin Lauckner, a sole trader in the United Kingdom. The "controller" of your data is Robin Lauckner, trading as Lab43, 10 William Jessop Way, Liverpool, L3 1DX, United Kingdom, email hello@lab43.dev. See the legal notice.

Only the small Lab43 team (Robin and the people who build MC Planner with him) can see personal data, and only as far as their work on MC Planner needs it, for example to answer support questions or fix a problem. The team also uses AI tools to build and run MC Planner, and those tools can see personal data when we use them for that work (section 13).

We plan to move Lab43 into a UK limited company. That company will then take over as the controller. We will update this page and email account holders before that happens; the way we use your data will not change because of it.

2. What stays on your computer

Your Minecraft game jar, your world files, your plans, imported schematic files and pinboard images are read and stored only in your browser (IndexedDB, local storage) or, in the desktop app, on your computer. We don't receive them unless you use one of the features in section 4. Settings such as your chosen display name are kept in your browser's local storage; this is needed for the app to work and is not used for tracking.

The MC Planner app uses no cookies, no third-party analytics and no advertising trackers. The app stores in your browser only what it needs to do what you ask: your settings, your local plans and files, your sign-in session if you sign in, the email address you last typed into the sign-in form (so you don't have to type it again), and, for one tab only, the name of the site that sent you (section 3). The website remembers the currency you chose for prices and, on its Schematics pages, which layers of a build you marked as built. None of this needs your consent under the UK's Privacy and Electronic Communications Regulations. The app also keeps the day of your first visit and which steps of getting started it has already counted, only for the statistics in section 12 ("How far people get in the app"), which you can turn off. The website counts its visits itself, without cookies and without anything that tells us who you are (section 3); if you turn that off, it keeps that one setting. Two things are the exception, and for both the website first asks you: the ads on the website, in Google's consent message (section 3, "Ads on the website"), and detailed counting of your visits, in that message or the website's own question (section 3, "If you agree to detailed counting"), whose answer it keeps.

Block textures from Mojang. When you press "Get started" (or "Get them from Mojang", or "Get the block textures from Mojang" on an invite), your browser or the desktop app downloads Minecraft's block textures directly from Mojang's servers (Mojang AB / Microsoft): the parts of the official Minecraft game file that hold them, from the same servers the Minecraft launcher uses. Mojang receives the usual technical data of a download (such as your IP address); see Mojang's privacy statement. The files are kept only on your computer. They never pass through our servers and we never receive or store them. If you'd rather not, choose "Use my own game file instead": MC Planner then reads the textures from your own game file, on your computer, and contacts Mojang only if you later choose it.

3. Visiting the website

The app at app.mc-planner.com and our server run on Cloudflare (Cloudflare, Inc., USA). When you open the app, Cloudflare processes technical data needed to deliver it and protect it from attacks: IP address, date and time, the address requested, browser type (user agent). We use this only to run and secure the service (legitimate interests, Art. 6(1)(f)) and don't combine it with other data. Our server's own logs at Cloudflare are deleted after at most 7 days. Beyond that, Cloudflare keeps what it needs to run and protect its network for as long as its own privacy policy allows, which we don't control.

The website www.mc-planner.com (the home page, pricing, downloads, the mod's page, the Academy and Schematics) is hosted by Vercel (Vercel Inc., USA), which processes the same kind of technical data to deliver it.

We count visits to the website ourselves. When a page opens, it tells our server which page it is, which site sent you (if any), the campaign tags in the page's address (such as utm_source) and the hour on your device's clock. When you leave the page or switch away from it, it says how long the page was on screen and how far down you scrolled. When you click one of the website's buttons (such as a download, the app or Modrinth) or a link to another site, it says which. Our server passes each of these to Lab43's internal dashboard (Lab43 HQ, whose database is at Supabase in Frankfurt, section 13) with: the page, the sending site's name only (not its full address), the country and region Vercel works out from your IP address, your browser's first language, the text your browser identifies itself with (its user agent) and a one-way code made from your IP address, so your IP address itself never leaves our server. The dashboard turns the code and that text into an anonymous ID that changes every day, using a random key that it deletes once the day is over. It keeps the kind of device and the names of your browser and system (such as "Chrome on Windows"), and never the code, your IP address or the user agent itself.

Unless you agree to more, what you did on the website is kept with that day's ID only until the end of that day: within about an hour after midnight, German time, it is added into daily totals (how many visitors, visits and page views there were, how long people stayed, and how they split by page, source, country, device and so on), which hold no ID and nothing about any one visit, and deleted. So that the totals can't describe anyone, a day with fewer than five visitors keeps only how many there were and at what hours, and a campaign tag that only one visitor came with is counted among the others. The UK's Privacy and Electronic Communications Regulations allow this without asking first, because it is used only to make statistics that help us improve the website and you can turn it off. We do it to see which pages help people (legitimate interests, Art. 6(1)(f)).

In the EU, Iceland, Liechtenstein and Norway the law has no such exception, so there we count your visits only if you agree to detailed counting (below), and then as described there; without that, the page sends nothing about your visit. The same goes when Vercel can't tell which country you are in.

If you agree to detailed counting. In the UK, the EU, Iceland, Liechtenstein, Norway and Switzerland, and when Vercel can't tell which country you are in, the website asks you first. On pages with ads, Google's consent message asks (also for its ads; see "Ads on the website" below): agreeing there to "Measure content performance" for MC Planner (agreeing to everything includes it) is your yes. Where Google's message isn't shown to you (a page without ads, ads switched off or blocked, or Google's message not working), the website asks its own question instead, "Can we count your visits in detail?", with "Yes, count in detail" and "No, thanks". To know whether to ask you, and whether a no still counts towards the daily totals where you are, the website first asks our server when you open it, which tells from the country Vercel works out; that request doesn't include the page you're on or anything you did. If you agree, we also keep what you did on each day, with that day's anonymous ID, for 400 days, so that we can see, for example, which pages the people who downloaded the app had read first. We still can't tell who you are from it, and one day's visits can't be linked to another's. This rests on your consent (Art. 6(1)(a)); you can change your choice at any time with "Privacy and cookie settings" at the bottom of the website's pages, and visits from then on follow your new choice. What was kept before stays for its 400 days, because it can't be linked back to you. While you are being asked, the page holds back what it would send until you answer; if you leave or switch away without answering, it counts the visit as if you had said no.

We set no cookies for this counting. For the detailed level, the page reads the choice that Google's message keeps in your browser, or keeps your answer to the website's own question in your browser's local storage for 6 months, after which it asks again. Nothing is counted when your browser sends Do Not Track or Global Privacy Control, and you can turn counting off on your device with Don't count my visits at the bottom of the website's pages (it keeps that one setting in your browser's local storage, and the same button turns counting on again). The daily totals are kept for 400 days; the dashboard's encrypted backups hold the totals, never the visits, for up to 30 days longer.

"Plan in my world" on a Schematics page makes the app download that build's file from the website, like any other download; nothing about you or your world is sent with it. The Marketplace in the app's Schematics window downloads the list of builds and the files of the builds it shows from the website in the same way; so that it has pictures when you open it, the list and the files of the first 30 builds are downloaded a moment after you open a world. Nothing about you or your world is sent with it.

If you came to the website from another site (for example reddit.com) and follow a link into the app, the link carries that site's name. The app keeps it for that browser tab only. If you then create an account, it goes with the request for your sign-in code; when you confirm the account, Lab43 adds one to a count of new accounts that came from that site and removes the name from your account (after a day if you never confirm it), so it isn't kept with you. Nothing is passed on when your browser sends Do Not Track or Global Privacy Control.

Ads on the website. The website www.mc-planner.com shows ads from Google AdSense, which help pay for MC Planner. The app, the desktop app and the Minecraft mod show no ads. When a page with ads opens, your browser loads Google's ad code from Google's servers. Google then receives the usual technical data (such as your IP address, your browser and the page you're on) and can use cookies or similar storage on your device. In the UK, the EU, Iceland, Liechtenstein, Norway and Switzerland, Google first asks you in a message on the website whether it may use cookies and your data for ads, including personalised ads. The same message also asks whether MC Planner may keep detailed visit counts (section 3, "If you agree to detailed counting"). What you agree to there is your consent (Art. 6(1)(a)), and you can change it at any time with "Privacy and cookie settings" on the website. If you say no, Google shows only ads that aren't based on you. Google runs the ads and is responsible itself for the data it gets, under its privacy policy (see also how Google uses information from sites that use its services); we don't receive that data. The website doesn't load Google's ad code when your browser sends Do Not Track or Global Privacy Control, and your Library and the layer-by-layer pages on Schematics show no ads.

4. Collaboration (optional)

When you…we storewho can see it
go live on a worldthe plan (objects, names, notes, statuses, pinboard cards), your account's display name and colour, your cursor position while connectedthe people in that world
share a worldthe world's files (level.dat, region files, world data) and a colour map of it; who owns the world, its members and their roles, and its invite links. A Minecraft world's files can contain the Minecraft names and player ids of the people who played in it.the people in that world
add an image to a pinboard while livethe image (resized in your browser first)the people in that world

This data is stored with Cloudflare (Durable Objects and R2 storage) and, for owners, members and invites, with Supabase (section 5), so the people you invite can plan with you (performance of our contract with you, Art. 6(1)(b)). Invite links are private: anyone who has one can join the world with a free account, so only share them with people you trust, and switch a link off (Revoke in the Share panel) when you no longer need it. Your game textures are never uploaded.

How long: a shared world stays on our servers until its owner stops sharing it (Stop sharing…, then Delete the shared copy, which deletes its plan, files, members and invite links on the server) or deletes their account. If the owner's plan no longer covers the world, it pauses: everyone can still open it read-only and export the plan, and nothing is deleted. A paused world stays until its owner deletes it or their account. If we ever start deleting worlds that have been paused for a long time, we will update this page first and email the owner at least 7 days before anything is deleted.

Builds on Schematics

The builds on Schematics (www.mc-planner.com/schematics) are made and published by Lab43. Since 12 November 2026 nobody else can publish a build there or ask to sell one. Looking at builds, downloading free ones and "Plan in my world" need no account (section 3).

Reports. Anyone can report a build on Schematics, without an account. We store the reason, what you wrote, your email address if you give one (only to answer you) and, if you're signed in, your account's id. To stop abuse, our server counts reports per IP address for a minute without storing the address. Only Lab43's reviewers see the report. Reports are kept until they're dealt with and then for up to a year, or until the build is deleted (legitimate interests, Art. 6(1)(f): keeping Schematics free of copied and harmful builds).

Paid builds. Some builds on Schematics are paid builds. They come with Cloud, Team and Lifetime (section 6), and can be bought one by one or in kits. To open a paid build you sign in on the website with your account (section 5). The website passes your sign-in on to MC Planner's server and doesn't keep it. The server looks up whether your account has one of these plans or was given the build by Lab43, and tells the website only whether you have the build and how (performance of our contract with you, Art. 6(1)(b)). The build's file is then written for you by our website from the build's blocks on MC Planner's server. When you download a paid build, we note your account's id, which build, when, for which Minecraft version and format, and how you have it (through your plan, for example), but not your IP address. We keep this for two years, to deal with copies and disputes (legitimate interests, Art. 6(1)(f)); if you delete your account earlier, the entries stay without your account's id. If Lab43 gives you a paid build (to test it, for example), we store that and the note it was given with, until you delete your account.

Buying a build or kit. When you buy one, our account service (auth.lab43.dev, section 5) opens Stripe's checkout for you and keeps the purchase: your account's id, which build or kit, the price, the currency, when, the payment's reference at Stripe, its state (paid, refunded or disputed), and when you ticked the box that you want the files now. Stripe (Link) is the seller of record and handles your payment details; we never see your card. We keep a purchase for six years, as tax law asks (legal obligation, Art. 6(1)(c)); if you delete your account earlier, it stays without your account's id. To show prices in your currency, the website reads the country your connection comes from (as Vercel tells it) when the page asks, and keeps nothing of it: your browser remembers only the currency until you close the tab.

Your cart on Schematics. A cart is the list of paid builds and kits you put in it. While you aren't signed in, it is kept in your browser's local storage (their addresses and how many there are) and nowhere else; to show what it costs, your browser sends that list to our server, which answers with the prices and keeps nothing. When you sign in, the list is kept with your account instead (which builds and kits, and when you added each), so it is there on your other devices; a cart from your browser joins it. We keep it until you take things out, buy them or delete your account. We use it only to show and to check out your cart (to take steps you ask for before a purchase, Art. 6(1)(b)).

If you sent us a build or asked to sell before 12 November 2026. Until then, people with an account could publish their own builds on Schematics and ask to sell them. From a build you sent we kept only its blocks (not the file itself, its metadata or anything else in it), the cover picture, the words you wrote, the creator name you chose and your account's id. A build that was approved is public with your creator name, never your email; one that wasn't is seen only by Lab43's reviewers, with your account's email address. If you asked to sell, we also hold what you told us then: your country, whether you sell as a private person or a business, your business name and VAT number if you gave them, that you confirmed you are 18 or older, which version of the seller terms you accepted and when, the prices you set, and what Lab43's reviewers decided about your request. This is stored with Cloudflare (R2 storage) and Supabase (section 5), because you asked us to publish or sell your builds (performance of our contract with you, Art. 6(1)(b)). The website no longer has pages to manage it, so write to hello@lab43.dev and we delete it for you; it is also deleted with your account. Copies of a build that people downloaded while it was public are theirs.

5. Accounts (optional)

You only need an account to plan together with others. An MC Planner account is a Lab43 account: the same account works on auth.lab43.dev, Lab43's account site, and for the Minecraft mod. When you create one we store: your email address; a password if you set one (stored only as a secure hash, never readable by us); the name and colour shown to the people you plan with (you pick them when you create the account; until you change it, the name is the one your sign-in service gives us, or the part of your email address before the @); when the account was created, when you last signed in, and that it was made in MC Planner (Lab43 counts how many accounts each app brings); which Lab43 apps you use and when each last asked Lab43 about your account (MC Planner does when you're signed in and use the server, at most once an hour); the devices you connected (such as the Minecraft mod, with the device name and when it was last used); and, if you sign in with Discord, Google, Microsoft or Apple where we offer it, the basic profile that service shares with us (your name and email). We use this to sign you in, to show who is planning in a shared world and to know what your plan includes (performance of our contract with you, Art. 6(1)(b)).

Accounts are stored with Supabase (Supabase Pte. Ltd.; servers in Frankfurt, Germany), which processes the data on our behalf. When you ask for a sign-in code or sign in, your browser talks to Supabase directly. Supabase uses your IP address to limit how many attempts can be made, and keeps the IP address and browser of each sign-in session until the session ends or the account is deleted, to keep accounts secure (legitimate interests, Art. 6(1)(f)). The sign-in session is kept in your browser's local storage (and, on auth.lab43.dev, in the cookies sign-in needs). You can change your name and colour in the app at any time. You can delete your account in the app (click your initial at the top right, then Delete account…) or on auth.lab43.dev: we first delete your shared worlds, end any subscription that could still charge you, and then delete the account and everything above.

What the Lab43 team sees. To help people and to understand how MC Planner is used, Lab43's managers can look up an account: its email and name, when it was made and last signed in, which Lab43 apps it uses and when it first and last used each, its plan and purchases (and an earlier free trial, if it had one), the mod devices it connected, its MC Planner worlds and its feedback posts and votes. They also see totals, such as how many accounts are active and how many people come back 7 and 30 days after they first used an app. They look this up live and keep no copy. We do this for support and to improve MC Planner (legitimate interests, Art. 6(1)(f)); you can object (section 16). We don't use it for ads or to make decisions about you.

Passwords known from data leaks. When you choose a password in the app (a new account, a new or changed password), the app checks it against Have I Been Pwned's list of passwords from known data leaks (Pwned Passwords, run by Troy Hunt through Cloudflare). Your password never leaves your device: the app turns it into a code (a SHA-1 hash) and sends only that code's first five characters; the list of leaked codes that start with them comes back and the app compares them on your device. Like any website, the service sees your IP address with the request. We do this to keep your account safe (legitimate interests, Art. 6(1)(f)); if the check can't be made, your password is not held up.

Lab43's account site is explained in full in the Lab43 privacy policy.

Emails we send

We email you only about your account and your plan: sign-in and confirmation codes, password resets, and important notices about your shared worlds or your plan, and, when Lab43 gives you a build or kit, one email saying what was added to your account and where to find it. These emails are part of the service (Art. 6(1)(b)). They are sent from Lab43's Gmail account through Google (Google LLC, USA), which handles the email address, the message and the time it was sent. We haven't signed separate data processing or transfer terms with Google (sections 13 and 14). Receipts, invoices and payment reminders come from Link, not from us (section 6). News about MC Planner only if you ask for it. When you create an account in the app, in the app's account menu and at checkout on the website there is a box: "Get new builds first. Email me when new builds, kits and features come out in MC Planner. At most twice a month. Unsubscribe any time." It is never ticked for you and it is separate from the terms. If you tick it, we may email you about those things, at most twice a month (your consent, Art. 6(1)(a)). You can untick it in the account menu at any time, and every such email has a link to stop them; stopping never affects your account. We keep a record of each choice you make there (yes or no, the words you were shown, where and when), because the law asks us to be able to show you agreed; it is deleted with your account. Without a yes we send you no such email, with one exception for customers: when you buy a build or kit on Schematics, the checkout shows an unticked box, "Don't email me about new builds and kits on MC Planner Schematics". If you leave it unticked and pay, we may email you about new builds and kits on Schematics (never other news), at most twice a month. This is the rule for a business's own customers (UK PECR reg. 22(3), the "soft opt-in"; our legitimate interest in telling customers about similar things, Art. 6(1)(f)). Every such email has a one-click link to stop them, and once you say no (there, in the account menu or by ticking the box) we never email you on this ground again. We keep the same record of it as of a yes. Each news email carries a link of its own that stops them with one click; we keep which news emails went to you (so nobody gets one twice) until your account is deleted. Like the account emails, they go out through Lab43's Gmail account.

6. Paid plans and payments

MC Planner's paid plans (Cloud, Team and Lifetime) are sold by Link, LLC ("Link"), Stripe's merchant of record. You pay on Stripe's checkout page, and Link takes the payment, handles the tax, checks for fraud, sends your receipts, invoices and subscription emails, and handles payment support, refunds and disputes. For this, Link and Stripe are responsible for your payment data themselves, under the Stripe privacy policy and Link's own terms. We never see or store your card details.

From Stripe we keep: one Stripe customer id for your account, what you bought, its status and dates (for example when a paid period ends or that a payment failed, and when a free trial ran if your plan started with one before free trials ended on 12 November 2026), and, for a one-time purchase such as Lifetime, the amount and the email address it was paid with. Your account page may show your card type and its last four digits, read from Stripe when you open it; we don't store them. We use this so MC Planner knows what your plan includes, to warn you before a plan ends, and to sort out refunds and disputes (performance of our contract with you, Art. 6(1)(b), and legitimate interests, Art. 6(1)(f)). If you delete your account, these purchase records are kept without the link to your account for up to 6 years after the purchase, for refunds, disputes and our tax records (legitimate interests and legal obligation, Art. 6(1)(f) and (c)), then deleted.

When you paste a link (for example Pinterest or YouTube) into a pinboard, also when you plan alone, the app sends the link to our server, which fetches that page to show its title and picture (performance of our contract with you, Art. 6(1)(b)). The website you link to sees our server, not you. Our server keeps the preview (the page's title, the site's name and a copy of its picture) under the link's address, not under your name, and fetches it again after 7 days.

8. Desktop app

The desktop app looks for Minecraft launcher folders on your computer to find your game jar and worlds. This happens only on your computer; nothing is sent to us.

Updates. A few seconds after it starts, the desktop app asks GitHub (GitHub, Inc., USA, part of Microsoft) whether a new version of MC Planner is out, and an update you choose to install is downloaded from GitHub. GitHub receives the usual technical data of a download, such as your IP address, under its own privacy statement. The request carries nothing about you or your worlds. The installers on our download page come from GitHub in the same way. On Windows, if Microsoft Edge WebView2 (which the app needs to show its window) is missing, the installer downloads it from Microsoft.

9. Minecraft mod

The MC Planner mod for Minecraft (Java Edition, Fabric) runs on your computer. It only talks to auth.lab43.dev and our server, and only while you use it.

Signing in. You sign the mod in with a code through auth.lab43.dev, the Lab43 account service. The mod asks for the code with a device name such as "Minecraft 26.2 · Windows", so you can recognise the device in your account. Your password and email address never reach the mod. Once you confirm the code, the mod gets its own key (a token that only works for the mod) and keeps it in .lab43/mcplanner-minecraft.json in your user folder (if that folder can't be written to: config/mcplanner-auth.json in the Minecraft profile).

What it sends. Every request to our server carries the key and the mod and Minecraft versions. Beyond that, the mod sends only the changes you make: a status you set, and a marker you add (its name and its position: x, y, z and the dimension). The people in that shared world see them. In return the mod receives your name and colour, the list of your shared worlds and the plan of the one you pick. It never asks whether you have a paid plan.

How often. While you're in a world with the plan overlay or the HUD on (or one of the mod's screens open), the mod asks our server every 10 seconds whether the plan has changed; usually the answer is "no" and nothing else is sent.

Files it reads. The mod only reads these files on your computer:

The mod never uploads these files and has no analytics. Beyond what's above it sends only a crash report, and only when you press Send (section 10). In the Minecraft profile it keeps its settings (with which crash report it last offered) and the last copy of each shared world's plan, so it works offline. (Version 0.2.0 also kept the result of a plan check in .lab43/mcplanner-access.json; later versions delete that file.)

Signing out. Signing out in the mod disconnects this computer and deletes the key from it. You can also disconnect the device from your Lab43 account at auth.lab43.dev.

10. Crash reports

If the MC Planner app (in the browser or the desktop app) crashes, it shows a crash screen. If Minecraft crashed with the mod in the crash, or the mod hit an error, the mod's menu offers Crash report. Both show you the whole report first, and you can add a note. Nothing is sent unless you press Send: never automatically, never in the background.

What a report contains: the error and where in the code it happened (the stack trace); the version of the app or the mod; the browser, or the Java, Minecraft and Fabric versions; the operating system; the name and limits of the graphics card; how long it had been running; the screen or tool that was open; settings that change how it works; counts (how many plan objects, regions or chunks); the last error and warning lines of its own log; and your note. The mod's report also contains Minecraft's crash report and the lines about the mod from Minecraft's log.

What's never in it: the names of your worlds, plans, files, schematics or servers; your plan's contents; invite links; your Minecraft name and player id; your email address or account id; tokens, keys or passwords; IP addresses; anything from Minecraft's game files. Folder paths are shortened so your user name isn't in them.

Where it goes: to auth.lab43.dev, Lab43's account site, without signing in. Only the Lab43 team reads crash reports, in Lab43's own tools, to find and fix the problem (legitimate interests, Art. 6(1)(f)). Your IP address isn't stored: the site keeps a code made from it that changes every day, only to limit how many reports one address can send. Crash reports are deleted after 90 days.

11. Feedback

In the app, Help (?) has Send feedback: a post on MC Planner's public feedback board at auth.lab43.dev, Lab43's account site. Nothing is sent unless you press Send, and before that the dialog shows everything that goes: your title and details, and one line with MC Planner's version, your system (web or desktop app, the browser, the operating system) and the screen you were on. Only the Lab43 team sees that line. Nothing about your plans, worlds, schematics or files is sent.

If you're signed in, the post is made with your Lab43 account and shows its display name. Without an account it shows as Anonymous; to limit spam, the account site keeps a code made from your IP address that changes every day, not the address itself. Posts are public once Lab43 approves them. Lab43 copies them, without name or email, into its own task list to act on them (legitimate interests, Art. 6(1)(f)). The code from your IP address is cleared after 7 days. A post without an account that Lab43 never approves is deleted after 90 days, and a hidden post 90 days after it was hidden. Deleting your Lab43 account deletes your posts, comments and votes; to have a post you made without an account deleted, write to hello@lab43.dev.

12. Counting how MC Planner is used

To see whether the paid plans work for people, our server counts three steps: someone wanted to share a world but their plan didn't allow it, a checkout page was opened, and a plan was bought (until 12 November 2026 also that a free trial started). Each count holds only the step and the plan's name, never an account, an email address, an IP address or a world, so it is not personal data. The counts are kept in Cloudflare's analytics storage.

How far people get in the app. To see where people get stuck when they start using MC Planner, the app counts a few steps of getting started: the welcome screen showed, "Get started" or "Use my own game file" was pressed, a world opened (the demo island or your own), the first plan was drawn, the tour began and reached its end, the starter checklist's items were done, someone signed in, and the app was opened again on a later day. The first time your computer reaches one of these, the app tells our server the step's name and whether it is the web or the desktop app. When your first visit ends, it also sends the furthest of the main steps you reached. Nothing else is sent: no account, no ID, no world and nothing about your plans. Our server adds each one to a daily total in Lab43's account database (Supabase, section 13); the totals don't say who did what, so they are not personal data. Our server uses your IP address for about a minute to hold back floods of such requests; it is not stored with the count. So that each step counts only once per computer, the app keeps the day of your first visit and the steps already counted in your browser's local storage (in the desktop app, on your computer). The UK's Privacy and Electronic Communications Regulations allow this without asking first, because it is used only to make statistics that help us improve MC Planner, and you can turn it off: untick "Count how far I get in the app" at the bottom of the welcome screen or under Help (the "?" button). Nothing is counted when your browser sends Do Not Track or Global Privacy Control. Only Lab43 sees the totals. So that the team's own use doesn't count, when you sign in the app asks our server whether your account is one of Lab43's own (the team's and its test accounts); only for such an account does it stop counting on that computer, and for everyone else the answer changes nothing. The website does the same for its page views and download counts.

Download counts on Schematics. To see which builds people use, our server also counts how often each build on Schematics is downloaded, opened with "Plan in my world" on its page, or placed from the Marketplace in the app. When you do one of these, the website or the app tells our server the build's address and which of the three it was. Each count holds only the build, the day and that kind, never an account, an IP address, a device or a world, so it is not personal data. Our server uses your IP address for about a minute to hold back floods of such requests; it is not stored with the count. Nothing is counted when your browser sends Do Not Track or Global Privacy Control. The counts are kept in our database. They are not shown in public: only Lab43 sees them. In the same way, and with the same limits, the website counts how often each build's or kit's page is opened, and our server counts how often a build or kit is taken to the payment page; with the sales this shows Lab43 which builds people look at but don't buy. These counts hold only the build or kit, the day and "page opened" or "went to pay".

13. Who else gets data

These providers get personal data from MC Planner. For each one: what we use it for, which data, where, how a transfer out of the UK is covered, whether we have a data processing agreement with it and, where we know it, how long it keeps the data.

Anthropic (Claude)

Company
Anthropic Ireland, Limited for people in the UK and the EU; Anthropic, PBC (USA)
What for
Claude, the AI assistant the team uses to build and run Lab43's products and tools. When it looks into a problem it can see the personal data involved.
Which data
Account details, crash reports and feedback posts it is shown; feedback copied into our internal dashboard without name or email
Where
Ireland; data processed on servers in the USA
Transfers out of the UK
None of ours: no data processing agreement and no transfer agreement. Anthropic's own privacy policy covers its transfers.
Data processing agreement
None
How long
Under Anthropic's privacy policy and the team's account settings

Cloudflare

Company
Cloudflare, Inc.
What for
Hosts MC Planner's app and server, shared worlds and pinboard images; security
Which data
IP address and server logs; shared worlds' files and images
Where
USA (worldwide network)
Transfers out of the UK
EU-U.S. Data Privacy Framework and its UK Extension (the UK-US data bridge)
Data processing agreement
None
How long
Server logs at most 7 days

GitHub

Company
GitHub, Inc.
What for
Desktop downloads and update checks (release files)
Which data
IP address and browser when a file is downloaded
Where
USA
Transfers out of the UK
Not needed: GitHub is responsible for this data itself
Data processing agreement
Not needed

Google (Gmail)

What for
Sends the sign-in codes and account emails (the team's Gmail over SMTP), and is the team mailbox hello@lab43.dev forwards to
Which data
Email addresses and the emails: sign-in codes we send, and emails people send us
Where
USA
Transfers out of the UK
None signed: no separate data processing or transfer terms
Data processing agreement
None
How long
Emails people send us: at most 2 years after the conversation ends

Google AdSense

Company
Google Ireland Limited for people in the UK and the EU; Google LLC (USA)
What for
Shows the ads on www.mc-planner.com that help pay for MC Planner, and the message that asks about ad cookies in the UK, the EU and Switzerland
Which data
IP address, browser and device details, the page, and cookies or similar identifiers where you agree to them
Where
Ireland and the USA
Transfers out of the UK
Not needed: Google is responsible for this data itself, under Google's controller terms for ads and its own privacy policy
Data processing agreement
Not needed
How long
Under Google's privacy policy

ImprovMX

Company
ImprovMX Incorporated
What for
Forwards hello@lab43.dev to the team's Gmail
Which data
Emails people send us
Where
USA (servers in the EU and the USA)
Transfers out of the UK
None signed: no separate data processing or transfer terms
Data processing agreement
None

Mojang (Minecraft)

Company
Mojang AB (part of Microsoft)
What for
Block textures: when you choose it, your browser or the desktop app downloads Minecraft's block textures straight from Mojang's servers. Nothing passes through ours.
Which data
IP address and browser, the usual data of a download
Where
Sweden; Microsoft servers worldwide
Transfers out of the UK
Not needed: Mojang is responsible for this data itself, under Mojang's and Microsoft's privacy statements
Data processing agreement
Not needed
How long
Under Mojang's and Microsoft's privacy statements

Sign-in services

Company
Discord, Google, Microsoft or Apple, whichever a person picks
What for
Signing in with an account someone already has, where we offer it
Which data
The basic profile it shares: name and email
Where
USA
Transfers out of the UK
Not needed: each is responsible for this data itself
Data processing agreement
Not needed

Supabase

Company
Supabase Pte. Ltd. (Singapore)
What for
Stores the Lab43 account, purchase records, feedback and crash reports, and MC Planner's shared worlds; and the database of our internal dashboard
Which data
Account email and name, sign-ins with IP address and browser, purchases, feedback posts and crash reports
Where
Data in Frankfurt, Germany; support from elsewhere
Transfers out of the UK
Data in the EU (UK adequacy regulations); support from elsewhere: Supabase's DPA, the EU SCCs with the ICO's UK Addendum
Data processing agreement
Accepted (read the agreement)
How long
Sign-in sessions until they end or the account is deleted

Vercel

Company
Vercel Inc.
What for
Hosts lab43.dev, auth.lab43.dev, www.gamesweep.app and www.mc-planner.com
Which data
IP address, browser and the pages asked for (request logs)
Where
USA (auth.lab43.dev and our internal dashboard run in Frankfurt)
Transfers out of the UK
EU-U.S. Data Privacy Framework and its UK Extension; the SCCs with the UK Addendum in its DPA
Data processing agreement
Accepted (read the agreement)
How long
Request logs at most 30 days

AI tools (Anthropic). The Lab43 team uses Claude, an AI assistant made by Anthropic, to build and run MC Planner. When we use it to look into a problem or a support question, it can see the personal data involved, such as account details, crash reports and feedback posts. Feedback that Lab43 copies into its own task list (without name or email, section 11) can also go to Claude, to suggest tasks. We do this to support people and to improve MC Planner (legitimate interests, Art. 6(1)(f)).

We use Claude on Anthropic's plans for individuals, under its consumer terms. There is no data processing agreement between us and Anthropic, so Anthropic doesn't process this data on our behalf: it handles what it receives under its own privacy policy. That policy names Anthropic Ireland, Limited as responsible for people in the UK and the EU, and says the data is processed on servers in the USA. How long Anthropic keeps it, and whether it may use it to improve its models, depend on that policy and our account settings. We are deciding whether to move to an Anthropic business plan with a data processing agreement, or to keep personal data out of AI tools. We will update this page when we do.

Email (Google and ImprovMX). Our emails to you (section 5) are sent from Lab43's Gmail account through Google (Google LLC, USA). hello@lab43.dev is forwarded by ImprovMX (ImprovMX Incorporated, USA; servers in the EU and the USA) to Lab43's mailbox with Google (Gmail), so we can read and answer your email (legitimate interests, Art. 6(1)(f)). We haven't signed separate data processing or transfer terms with Google or ImprovMX: they handle these emails under their own terms and privacy policies.

These organisations are responsible for the data they get themselves, under their own privacy policies: Link and Stripe (payments, section 6); GitHub (desktop downloads and update checks, section 8); Microsoft (WebView2 for the Windows app, section 8); Mojang (when your browser downloads the block textures from it, section 2); Google (the ads on the website, section 3); and Discord, Google, Microsoft or Apple if you use them to sign in.

We don't sell personal data and don't share it for advertising. The ads on the website are Google's: Google gets its data from your browser directly (section 3), not from us. We would only give personal data to the police or another authority if the law requires us to.

14. Data outside the UK

Some of the providers in section 13 are outside the UK or can reach data from there. How each transfer is covered is under "Transfers out of the UK" for each provider in the list in section 13. Providers that rely on the EU–U.S. Data Privacy Framework and its UK Extension (the "UK–US data bridge") say so in their privacy policies, for example Cloudflare and Vercel.

The organisations that are responsible for data themselves (section 13) explain their own transfers in their privacy policies. Write to us if you'd like to know more.

15. How long we keep data

Datakept until
Your accountyou delete it
A shared world (plan, files, images, members, invite links)its owner deletes the shared copy or their account (section 4)
Purchase recordsup to 6 years after the purchase (section 6)
Our server's logsat most 7 days
What you did on the website, with that day's anonymous IDuntil the end of that day, or 400 days if you agreed to detailed counting (section 3)
Your answer to the website's own question about counting6 months, in your browser only (section 3)
Daily totals of website visits (no IDs)400 days, and up to 30 days longer in encrypted backups (section 3)
Reports about a build on Schematicsup to a year after they're dealt with, or the build is deleted (section 4)
The note of a paid build you downloaded2 years (section 4)
A build you sent us or a request to sell, from before 12 November 2026you ask us to delete it, or you delete your account (section 4)
Crash reports90 days
Feedback postsas in section 11
The mod's key (on your computer)you sign out in the mod or disconnect the device
Emails you send usas long as we need them to help, at most 2 years after the conversation ends

16. Your rights

You can ask us for a copy of the data we hold about you, and to correct it, delete it, restrict how we use it, or give it to you in a machine-readable form. You can object at any time to anything we do on the basis of legitimate interests. Write to hello@lab43.dev from the email address of your account, or tell us how to find your data. We answer within one month; for complicated requests we may need up to two more months, and we'll tell you if so. Asking is free. Many things you can do yourself in the app: change your name and colour, stop sharing a world, disconnect a device, delete your account.

We don't make decisions about you by automated means that have legal or similarly significant effects.

17. Complaints

If you're unhappy with how we handle your data, please tell us first at hello@lab43.dev. We will confirm that we received your complaint within 30 days, look into it, keep you updated, and tell you what we found and what we're doing about it without undue delay. You can also complain to the Information Commissioner's Office (ICO), the UK's data protection regulator, at any time: ico.org.uk/make-a-complaint, phone 0303 123 1113. If you live in the EU, you can also complain to the data protection authority in your own country.

18. Children and young players

Many people who play Minecraft are young, so we keep MC Planner simple and private by default: planning on your own needs no account and no personal data; the app has no ads, no tracking and no location data; we don't build advertising profiles or recommend content to anyone; shared worlds are only open to the people the owner invites; and other people see only your account's name and colour. The website shows ads from Google; in the UK, the EU and Switzerland, Google asks first before it uses cookies for them (section 3). You pick the name when you create the account: we suggest a nickname rather than your real name.

You need to be at least 13 years old to create an account. If you're under 18, please ask a parent or guardian before you buy a plan: they need to agree to it (see the terms). If you're a parent and think your child under 13 has made an account, write to us and we'll delete it.

19. Security

Everything between your device and our servers is encrypted (HTTPS). Shared worlds are only reachable through their invite links, passwords are stored as hashes, and only the Lab43 team, and the AI tools they work with (section 13), can reach the systems that hold personal data. If something ever goes wrong with your data, we will tell you and, where the law requires it, the ICO.

20. Changes

We will update this page when MC Planner or the law changes. The date at the top shows the latest version. If a change matters for how we use your data, we will also tell account holders by email or in the app before it applies.