Privacy Policy

What we store

Your account. Your name, e-mail address, billing address and, if you order as a business, your VAT number. We need these to set up your server, to invoice you and to work out the right VAT.

Your payments. Which plan you bought, what you paid and when, and whether a payment succeeded. Card numbers are handled by our payment provider and never reach our servers.

Your server. The files, worlds, configurations and logs on the server you rent, and the backups of them. This is your content. We treat it as yours.

Technical records. Which addresses connect to our systems, and when. This is how we find a problem and how we spot an attack.

When your server crashes. We read the end of its console log to start it again and to tell you in plain words what went wrong. We keep a short excerpt of that log, the Minecraft version and loader, and a fingerprint of the error, so we recognise the same error next time and our explanations and fixes get better. Before we store the excerpt we remove IP addresses, UUIDs, e-mail addresses, anything that looks like a password or token, and the chat messages and player names we can recognise. If you use a fix button in the panel, we keep what the fix changed, who pressed it and whether the server started afterwards, but not the contents of your files. A file the fix moves goes to the fix-backups folder on your server, so you can put it back. If you ask the Copilot in the panel why your server crashed, we keep the same kind of excerpt and note which checks and suggestions it used, but not your question or its answer; those stay in your Copilot history. We do the same when a plugin shuts your server down because it could not start. When one of our own steps on your server fails, such as getting it ready, setting up crossplay or moving a server in from another host, we note which step it was and its error message, but not your files or the links you gave us.

Invites. If you share your invite link, we keep your invite code, every visit to it (with a one-way fingerprint of the visitor's IP address, never the address itself), which accounts were made through it and how far each one got, and for an account made through a link, who invited it. We use this to add Copilot credits, to show you how your invites are doing (friends are masked, like j***@gmail.com) and to stop misuse. We keep it for as long as either account exists.

The Copilot. If you use the Copilot in the panel, we keep your questions, its answers and what the Copilot remembers about your server. To answer you, it sends your question and the files, settings and logs of that server it needs to the AI service that writes its answers. Once a day an automated check reads the Copilot conversations of the day before, through the same AI service, and compares them with the current state of the same server (the same files, its port allocations and its log) to find wrong answers and wrong changes. We use the result to repair what the Copilot broke and to add general rules so it does not make the same mistake again; those rules contain no names, server names or addresses from your conversation. The AI service does not use this data to train its models. If you do not use the Copilot, none of this happens.

The Copilot in the website builder. If you use the Copilot in the builder of your free server website, it sends your request, the content of your website (texts, pages, settings, style and the ids of images you uploaded) and basic facts about your server (its name, address, version and how many players are online) to the same AI service, to build or change your website as you asked. The AI service does not use this data to train its models. We keep your requests and the Copilot's answers with your website, so you can read the conversation back in the builder; they are deleted together with your website. Nothing goes online until you publish.

Files you attach. You can attach files to a Copilot question, such as a screenshot, a log or a config file. What you attach is sent to the same AI service, only to answer that question, and is not used to train AI models. Images are not kept: after the answer, only the file name stays in the conversation. The text of a log or config file you attach becomes part of your question and is kept with the conversation, like the rest of your question, until you delete the conversation. Do not attach files that contain passwords, API keys or other people's personal data.

Talking to support in the Copilot. If you click Talk to support in the Copilot and allow it, our support team can read that one conversation and reply to you in it. They see your questions, the Copilot's answers and what you write to support there. What you write to support is not a question to the Copilot, but the Copilot reads it as background the next time you ask it something in that conversation. You can withdraw your permission at any time with Stop sharing with support; after that, support can no longer read the conversation or reply in it. We keep when you gave the permission and when you withdrew it, with the conversation.

What you send us. Messages through the contact form or support, so we can answer and look things up later.

The waiting list. If you left your e-mail address on the page we showed before launch, we keep that one address for one message: the one that says we are open.

Why we are allowed to

Most of it is simply the agreement: without an e-mail address and an address for the invoice there is no server and no bill. Keeping our machines and other customers safe is our own legitimate interest. Invoices and tax records are a legal duty. The waiting list is your consent, and you can take that back at any time.

How long we keep it

Server files and backups: while you rent the server, plus 7 days after it ends so you can download them. After that they are deleted.

Invoices and what belongs to them: seven years, because Dutch tax law says so.

Technical records: weeks, not years, unless one is part of an incident we are still looking into.

Support messages: as long as they are useful for helping you, and then they go.

Crash excerpts and fix records: 12 months. After that only a count per type of error is left, without a link to you or your server.

The report of the daily Copilot check: 90 days.

The waiting list: deleted after the launch message is sent, or as soon as you ask.

Who else sees your data

Only parties we need to run the service: the company that processes payments and produces the invoice, the data centres in Europe where the machines stand, the network that keeps attacks away from them, the service that delivers our e-mail and, only if you use the Copilot, the AI service that writes its answers and is used for the daily check. Our support team uses the same AI service to look into new kinds of server errors. Each of them gets only what they need for their part, works under a written agreement, and may not use it for anything else.

We do not sell data, we do not trade it, and we do not hand it to advertisers. We hand something to an authority only when the law obliges us to.

Where it is

Your server, your backups and your account data stay on machines in Europe. Where a supplier processes something outside the European Economic Area, such as the AI service behind the Copilot in the United States, it happens under the safeguards the GDPR requires.

Cookies

This site sets only what it needs to work: a cookie that keeps you logged in, and while we are still building, one that remembers you entered the preview password. We do not use advertising cookies and we do not follow you across other sites.

If you open someone's invite link, the customer area sets two more: one remembers for 30 days whose link it was, so the Copilot credits reach the right account when you sign up, and one holds a random device code, used only to spot someone inviting themselves.

What you can ask us

You can ask for a copy of what we hold about you, have it corrected, have it deleted where we are not obliged to keep it, ask us to stop using it, or ask for it in a form you can take elsewhere. Ask through the contact page and you hear from us within a month, usually a lot sooner.

If you think we handle your data badly, tell us first so we can fix it. You can also complain to the Dutch data protection authority, the Autoriteit Persoonsgegevens.

Children

A lot of Minecraft players are young. If you are under 16, ask a parent to place the order and to be the person we deal with. If you are a parent and you think we hold data about your child that should not be there, write to us and we will remove it.