Privacy policy
Last updated: 26 October 2026
This policy covers this website, the Cubiq Launcher, the Cubiq Client mod and the Cubiq services. In short: no tracking, no analytics, no advertising – only what is needed for what you use.
Controller
Lucas Wilms
Lüdenscheider Str. 21
51688 Wipperfürth
E-mail: [email protected]
All details are in the imprint.
This website
Hosting. The website and the Cubiq services run in one app on a server of the controller. It is reachable only through a Cloudflare Tunnel; Cloudflare (Cloudflare, Inc. / Cloudflare Germany GmbH) terminates the HTTPS connection and processes your IP address and the requests on our behalf under its data processing addendum. Transfers to the USA are covered by the EU-US Data Privacy Framework and standard contractual clauses. Legal basis: Art. 6(1)(f) GDPR (a secure, working website).
Server logs. Our logs contain only technical data (method, path without query, status, duration, request id) – no IP addresses. Rate limits count requests per IP address in memory only; the counters are never written to disk and disappear after a few minutes.
Cookies. The website sets no tracking or advertising cookies and uses no analytics. There are only four technically necessary cookies (§ 25(2) TDDDG):
| Cookie | Purpose | Duration |
|---|---|---|
cubiq_lang |
Remembers the language you picked | 1 year |
cubiq_oauth |
Protects the sign-in with Microsoft against forgery (random value, only on /auth/microsoft, httpOnly) | max. 10 minutes |
cubiq_llogin |
Ties a sign-in with the Cubiq Launcher to this browser (random value, only on /v1/web/launcher-login, httpOnly) | max. 3 minutes |
cubiq_session |
Keeps you signed in after the sign-in with Microsoft or the Cubiq Launcher (httpOnly, Secure, SameSite=Strict) | 8 hours |
Fonts and scripts are served from this server – no external CDNs, no Google Fonts.
GitHub. Downloads link to GitHub Releases, and pictures in update posts are loaded from raw.githubusercontent.com. When you download a file or open a post with pictures, your browser connects to GitHub, Inc. (USA), which receives your IP address; see GitHub's privacy statement. Our server asks the GitHub API for the newest version and reads the changelog – without any data about you.
Team area. Team members sign in with Microsoft like everyone else (see “Website sign-in with Microsoft” below). What they see in the team area depends on the permissions of their role – for example, only roles with the right permission see the content of reports or player files. Team members review chat reports – they only see the content that was reported and its context (see “Reports and moderation” below); reported pictures are loaded from this server only. They also manage sanctions, appeals and internal notes (see “Sanctions and appeals” below); every action is written to an audit log (kept 2 years).
Shared modpacks (/p/… pages). A player can share a modpack with a code; its page shows the pack's name, description, the mods, resource packs and shaders inside and the name and head of the player who shared it, and is never indexed by search engines. Names, versions and icons of the files come from Modrinth: our server asks Modrinth's public API only for the project and version IDs in the pack and passes the icons on itself – your browser does not connect to Modrinth and no data about you is sent there. Downloading the pack is only possible in the Cubiq Launcher with a Cubiq account. Signed in, you can report a pack; the report is handled like other reports. Legal basis: Art. 6(1)(f) GDPR (showing a pack the player chose to share, a safe service). Details: “Sharing modpacks” below.
Shared screenshots (/s/… pages). When a player shares a screenshot as a link, anyone with the link can open this page for 30 days. It shows only the picture, the upload date and the expiry date – no name, no Minecraft UUID – and is never indexed by search engines. Chat apps such as Discord load the picture when someone posts the link, to show a preview. With “Report” you can tell our team about a picture without an account: we store only the reason you picked, never your IP address (it is counted for rate limiting in memory only). Legal basis: Art. 6(1)(f) GDPR (a safe service). Details: “Shared screenshots” below.
News posts (/blog). Besides the automatic update posts, the team writes news. A news post shows the name and head of the team member who wrote it (or “Cubiq Team”); its pictures are served from this server. Legal basis: Art. 6(1)(f) GDPR (informing about the project).
Links to Discord, GitHub and other sites are plain links; nothing is loaded from them until you click.
Newsletter and e-mail
Newsletter. You can subscribe to the Cubiq newsletter on this website (footer or /newsletter) or in the Cubiq Launcher (Settings → Account → Newsletter). We use double opt-in: you only get newsletters after clicking the link in the confirmation e-mail (valid 48 hours). We store your e-mail address, the language of the newsletter, the source (website or launcher), the status (waiting, confirmed, unsubscribed), the time of your confirmation and the version of the consent text – as proof of your consent. If you subscribe in the launcher, the address is linked to your Cubiq account only after you confirm. We do not store your IP address, and the e-mails contain no tracking pixels and no tracked links; we do not know whether or when you open them.
Unsubscribing. Every newsletter has an unsubscribe link and supports one-click unsubscribe in your mail program (List-Unsubscribe, RFC 8058). You can also unsubscribe in the launcher. Unconfirmed sign-ups are deleted after 7 days, unsubscribed addresses after 30 days.
Team notifications. Team members can get e-mails about new applications, reports, appeals and creator pet requests at an address they confirm themselves. These e-mails contain only short facts (type, name, position, time) and a link to the team area – never message contents.
Sending. We send e-mails through the mail server (SMTP) set up for this website, from the sender address shown in the e-mail. Pictures in the e-mails (headers, titles, creator heads) are loaded from this website when you open the e-mail; your mail program decides whether it loads them. Sent e-mails stay in our outbox for at most 30 days (address and status, for delivery and error handling), then they are deleted.
Legal basis. Newsletter: your consent, Art. 6(1)(a) GDPR, which you can withdraw at any time with effect for the future. Proof of consent and team notifications: Art. 6(1)(f) GDPR.
Website sign-in with Microsoft
You can sign in to this website with the Microsoft account that owns Minecraft: Java Edition – for example to apply for the team or, as a team member, to open the team area. The sign-in uses Microsoft's standard OAuth procedure: you enter your password only at Microsoft; we never see it.
What we receive. Microsoft, Xbox Live and Minecraft confirm your Minecraft UUID and name. For this our server exchanges short-lived tokens with Microsoft (login.microsoftonline.com), Xbox Live (user.auth.xboxlive.com, xsts.auth.xboxlive.com) and Minecraft (api.minecraftservices.com). The tokens exist only in memory for the few seconds of the sign-in and are discarded right after – we store no Microsoft, Xbox or Minecraft tokens, no e-mail address and no password.
What we store. Your Cubiq account (UUID, name, first and last sign-in – created now if you have not used Cubiq before) and a website session: a hash of the session token, a CSRF token and the expiry (8 hours, at most 5 sessions per account). Signing out deletes the session at once. Sign-ins of team members are recorded in the audit log (2 years).
Legal basis. Art. 6(1)(b) GDPR (you want to use the sign-in); for security measures such as rate limits and the audit log Art. 6(1)(f). Microsoft processes the sign-in under its own privacy statement (Microsoft Corporation, USA; EU-US Data Privacy Framework).
Website sign-in with the Cubiq Launcher
Instead of Microsoft you can confirm the sign-in in your Cubiq Launcher. The website shows a short code and opens the launcher (link cubiq-launcher://web-login/…); the launcher shows the code, the website, a rough browser description and your account and asks you to confirm. Nothing is confirmed without your click.
What we store. For the up to two minutes of the request: a hash of the link value and of a random browser value (cookie cubiq_llogin), the code, a rough browser description such as “Firefox · Windows” (never the full browser identification, never your IP address), the return page and – after you confirm – your Minecraft UUID. The request is deleted when you are signed in, when it is declined, or shortly after it expires. The session afterwards is the same as after the sign-in with Microsoft (see above). Sign-ins of team members are recorded in the audit log (2 years).
Legal basis. Art. 6(1)(b) GDPR (you want to use the sign-in); rate limits and the audit log Art. 6(1)(f).
Team applications
If you apply for a position in the Cubiq team, we store your application: the position, your Minecraft name and UUID (from the sign-in), your Discord name, your age group (never your date of birth), your answers to the questions of the position, the language of the form, the status and our answer to you.
Who sees it. Only team members whose role may see applications (for example the recruiting team and admins). They can add internal notes and votes that you don't see. Team members who may open player files also see your Cubiq sanction history. We use your Discord name only to contact you about the application.
Your view. Under “My applications” (and later in the launcher) you see the status and our answer; you can withdraw an open application at any time.
Storage period. Rejected or withdrawn applications are deleted 6 months after the decision. Accepted applications are kept while you are in the team and deleted 6 months after you leave. Deleting your Cubiq account deletes all your applications at once.
Legal basis. Art. 6(1)(b) GDPR (steps you asked for before a voluntary team membership) and Art. 6(1)(f) (a fair decision and protection against abuse). If you are under 16, please talk to your parents before you apply.
Team page
The team page (/team) shows team members that the team added by hand – nobody appears there automatically. For each of them it shows the Minecraft name, the Minecraft skin (loaded from Mojang's texture server and shown as a 3D figure), the Cubiq cape if the person shows it to others, the group (role) and – only if entered – a position title, a Discord name and up to three links. To show faces and figures without asking Mojang on every visit, we store the address of the last seen Minecraft skin with the Cubiq account. If you are on the team page and want to be removed, tell a team member or write to us (e-mail above); leaving the team does not remove you automatically, the team does. Deleting your Cubiq account removes you from the page at once.
Legal basis. Art. 6(1)(f) GDPR (showing who runs Cubiq and how to reach them) and your agreement as a team member.
Circuit library
Public library. The circuit pages (/circuits) and the Cubiq Client load circuits from our server without an account. The server only counts requests per IP address in memory (rate limit). The Cubiq Client checks for new circuits once per game start – only if you allowed the Cubiq online features.
Submitting a circuit. When you submit a circuit (signed in, on this website or in the Cubiq Client), we store the circuit (only blocks and their states – no chest contents or other block data), the name, description, category and language you entered, the file type, your Minecraft UUID and name, the time, the status and our answer. The uploaded file itself is not stored: it is converted and discarded right away. Only team members whose role may manage the library see submissions.
Your name is shown. If we accept your circuit, it is published in the library on this website and in the Cubiq Client with your Minecraft name (and your UUID for the head picture) as the creator. You confirm this with the checkbox when you submit.
Storage period. Decided submissions (accepted or rejected) are deleted 90 days after the decision; open ones stay until they are decided. A published circuit stays in the library until the team removes it. Deleting your Cubiq account deletes all your submissions and removes your name from the circuits you made (they stay in the library without a creator). You can ask us at any time to remove a circuit of yours (e-mail above).
Reports. Signed-in users can report a circuit; the report is handled like other reports (see “Reports and moderation”).
Legal basis. Art. 6(1)(b) GDPR (you want to publish your circuit) and Art. 6(1)(f) (reviewing content and preventing abuse, e.g. at most 5 submissions a day and upload bans).
Issue tracker and roadmap
Public pages. The issue list (/issues), every issue page (/issues/<number>) and the roadmap (/roadmap) can be read by anyone without an account. They show the issues, comments and screenshots together with the Minecraft name and head of the player who wrote them, votes (as totals), the status and the team's triage (assignee, priority, tags, “fixed in”).
Writing, voting, following. To open an issue, comment, vote or follow you sign in (Microsoft sign-in on this website, or your Cubiq account in the Cubiq Client). We store the issue or comment (title, text, type, area), your Minecraft UUID, the time, edits, your vote per issue (up or down) and which issues you follow. Following means you get a notification in the Cubiq Launcher (over the Cubiq connection you already use) when the status changes, the team answers, a fix ships or the issue is merged – you can unfollow at any time. Your votes are never shown individually, only as a total.
Screenshots. Pictures you attach are re-encoded on our server (no metadata such as location or camera data stays) and are public together with the issue or comment. Pictures you upload but don't attach are deleted after one hour. Please don't put personal data in texts or screenshots.
Bug reports from the Cubiq Client. “Report a bug” in the Cubiq Client can attach technical info – only the parts you tick, and you see exactly what is sent: the Cubiq Client version, the Minecraft version and loader and your mod list (shown publicly with the issue), and an excerpt of the game log, which only you and the team can see. Before sending, the client removes access tokens, session ids, e-mail addresses, IP addresses, UUIDs and your player name from the log; our server does it again.
Team. Team members with the matching permission change status, priority, assignee, tags and “fixed in”, merge duplicates (votes and followers move to the other issue), write internal notes (only visible to the team), close comments and delete issues or comments. These actions are recorded in the audit log (2 years).
Storage period. Issues and comments stay public as long as the tracker exists, because they document the development. You can edit your issue while it is open and edit or delete your comments at any time. Deleted issues are removed completely after 90 days. Deleting your Cubiq account deletes your votes, follows, the log excerpts of your issues and all pictures you uploaded; your issues and comments stay without your name. You can ask us to remove content of yours (e-mail above).
Reports. Signed-in users can report issues and comments; reports are handled like other reports (see “Reports and moderation”).
Legal basis. Art. 6(1)(b) GDPR (you want to report a bug, suggest a feature, vote, comment or be notified) and Art. 6(1)(f) (a transparent development process, moderation, protection against spam – e.g. at most 10 issues, 60 comments and 30 pictures a day).
The Cubiq Launcher
Cubiq Launcher runs on your computer. It has no telemetry, analytics, crash reporting or advertising. It only sends information to a server run by the Cubiq Launcher project if you turn on the optional Cubiq services (capes, friends, online status, chat). Without your consent, the launcher sends nothing there.
The launcher only connects to other services when that is needed for something you asked it to do:
| Service | When | What is sent |
|---|---|---|
| Microsoft / Xbox Live / Minecraft services | Signing in, starting the game | Standard OAuth sign-in; your Minecraft access token when the game starts |
Mojang (piston-meta, libraries, resources) |
Installing or starting a version | Download requests for game files |
Mojang session server (sessionserver.mojang.com) |
Signing in to the Cubiq services (only after you agreed) | The same "join" request a Minecraft server login uses: your access token, UUID and a one-time challenge |
Mojang profile services (api.mojang.com, sessionserver.mojang.com, textures.minecraft.net) |
Importing a skin by player name, showing player faces (friends, admin search) | The player name or UUID being looked up; a download of that skin image |
| The website of a link you enter | Only when you import a skin "by link" | A normal download request for that image (only HTTPS, no cookies or accounts) |
| Cubiq services (this website) | Only after you agreed, see below | Your UUID, name, cape choice, friends, online status, chat messages and pictures you send, reports |
| Fabric, Quilt, Forge, NeoForge maven/meta servers | Installing a mod loader | Download requests |
Modrinth (api.modrinth.com, cdn.modrinth.com) |
Browsing, installing or updating content | Search queries, file hashes of installed mods (for update checks) |
CurseForge (api.curseforge.com; files and images from edge.forgecdn.net, mediafilez.forgecdn.net, media.forgecdn.net) |
Only when you pick CurseForge as the source, install a CurseForge modpack, have content from CurseForge installed or import a CurseForge instance whose files are missing | Search queries and filters, the project and file IDs of content installed from CurseForge (for details and update checks), download requests. Like every web request, this includes your IP address. You don't need a CurseForge account – the launcher identifies itself with its own API key, not with anything about you. |
| Minecraft servers in your server list | Showing live status; Fast Connect (see below) | A standard server-list ping; a DNS lookup of the server's addresses and a short connection test to each (opened and closed again, nothing is sent) |
| mclo.gs | Only when you click "Share log" and confirm | The log you picked (latest log, an older log or a crash report), with access tokens and your Windows/Linux user name removed |
GitHub (github.com) |
Checking for launcher updates | A request for the update manifest |
| Discord app on your computer (local only, no internet) | While the launcher is open and "Show Discord status" is on (default), see below | Your Discord status: "In the Cubiq Launcher", or the Minecraft version, mod loader and play time of the running game |
Account tokens are stored only on your computer, encrypted with Windows DPAPI. Uninstalling the launcher removes the
program; your data in %APPDATA%\Cubiq-Launcher can be deleted at any time.
Importing from other launchers
When you open "Import from another launcher", the launcher looks for other launchers on your own computer (official Minecraft Launcher, CurseForge app, Modrinth App, Prism/MultiMC, Lunar Client, Badlion, Feather, OneClient, ATLauncher, GDLauncher, TLauncher) and reads their instance lists. Nothing of this leaves your computer, and the other launchers' files are only read, never changed – their databases are read from a temporary copy that is deleted right afterwards. Sign-in data of other launchers (account and token files) is never read or copied. When you import an instance, its worlds, mods, packs, settings and server list are copied into the new Cubiq instance; the project and file IDs the other launcher saved are kept so the content can be updated. Only if files of a CurseForge instance are missing does the launcher download them from CurseForge (see the table above).
Switching accounts in the game (Cubiq Client)
- Game started with the Cubiq Launcher: the Cubiq Client can show your launcher accounts and switch between them
without restarting. When you pick an account, the launcher hands a fresh Minecraft access token to the game over a
local connection on your computer only (
127.0.0.1), encrypted and only to the game process it started itself. The key for that connection is handed to the game in memory when it starts and is never written to disk. Nothing leaves your PC for this. "Add account" in the game opens the normal Microsoft sign-in of the launcher in your browser. - Game started without the Cubiq Launcher: accounts you add in the game sign in directly with Microsoft, Xbox Live and
the Minecraft services (with the Cubiq Launcher's own sign-in app). Only the refresh token is kept, encrypted (Windows
DPAPI; elsewhere AES with a key file in your user folder), in
config/cubiqclient/accounts.jsonof that game folder. Access tokens stay in memory. Remove an account in the game to delete it. - For the small faces in the list, the game loads the skin from
textures.minecraft.netand, if needed, the public profile fromsessionserver.mojang.com.
Wardrobe in the game (Cubiq Client)
The wardrobe of the Cubiq Client (skins, outfits, capes, emotes and the skin editor) only goes online for what you do there:
- Applying a skin or choosing a Minecraft cape sends the skin image and its model (classic/slim), or the cape
choice, together with your Minecraft access token directly to Mojang (
api.minecraftservices.com), exactly like the official launcher. To show your capes, the game reads your Minecraft profile there and loads the images fromtextures.minecraft.net. - Adding a skin by player name looks the name up at Mojang (
api.mojang.com,sessionserver.mojang.com) or, with the Cubiq services on, through the Cubiq services, and downloads that skin fromtextures.minecraft.net. - Adding a skin by link downloads that one image from the address you enter – only HTTPS, no cookies, never from addresses in your local network.
- Adding a skin from a file opens your system's file dialog; the file is only read on your PC.
- With the Cubiq services on, your skins in the wardrobe are the same "My skins" as in the launcher (synced with your Cubiq account, see below), and your favourites, outfits (name, skin, cape) and emote wheel slots are saved in a small "wardrobe" entry of your Cubiq account so they are the same on every PC. Choosing a Cubiq cape saves that choice in your Cubiq account; after applying a skin the game tells the Cubiq services, so other Cubiq players see the new skin sooner.
- Without the Cubiq services everything stays on your PC in
config/cubiqclient/wardrobe/of the game folder.
Fast Connect
"Fast Connect" (module of the Cubiq Client, on by default) and the launcher's server page only talk to the servers you use and to your normal DNS resolver – never to the Cubiq services:
- Looking up servers in advance: when you select a server in the list or start a game with a server, its DNS
entries (SRV, IPv4 and IPv6 addresses) are looked up, and the fastest address is found by opening a connection to
each and closing it again right away – without sending any data, like the usual server-list ping. The launcher
passes the result to the game in
config/cubiqclient/connect-hints.json; entries expire after at most 10 minutes. - Server resource packs: the Cubiq Client remembers which resource pack (address and checksum) a server sent, only
if you accepted it, in
config/cubiqclient/server-packs.jsonof the game folder. When you select that server again, the pack is downloaded in the background from the address the server gave – the same download Minecraft would do when you join, never from addresses in your local network unless the server itself is in it. Packs you declined are forgotten.
Discord
If the Discord app is running on your computer, the launcher shows a status on your Discord profile ("Playing Cubiq Launcher"): "In the Cubiq Launcher" while only the launcher is open, and while you play the Minecraft version, the mod loader (e.g. Fabric) and how long you have been playing. It never shows server addresses, instance names or player names.
- The launcher only talks to the Discord app on your own computer (Discord's local interface, a named pipe or local socket). It sends nothing over the internet itself and doesn't need your Discord login.
- The Discord app then shows this status on your profile – publicly visible to the people who can see your Discord profile (friends, members of shared servers). What Discord does with it is covered by Discord's privacy policy.
- The status disappears when you close the launcher. If Discord isn't running, nothing happens.
- It is on by default and can be turned off at any time under Settings → Privacy → Show Discord status (or hide it in Discord under User Settings → Activity Privacy).
Cubiq services
The Cubiq services add Cubiq capes, a friends list and an online status to the launcher and to the Cubiq Client mod. They are off until you agree in the launcher (a short note explains what is stored before the first sign-in). You can turn them off again at any time under Einstellungen → Datenschutz.
How signing in works
The launcher signs in with your Minecraft account the same way a Minecraft server checks a player: it asks the Cubiq server for a one-time challenge, confirms it with Mojang's session server using your Minecraft access token, and the Cubiq server asks Mojang whether that happened. The Cubiq server never sees your password or your Minecraft access token. It then issues its own token, which the launcher stores encrypted with Windows DPAPI on your computer and never hands to web content or to the game. The Cubiq Client mod signs in by itself through the game session.
Friends in the game (Cubiq Client)
With the Cubiq services on, the Cubiq Client mod shows your friends list in the game. It asks the Cubiq server for your
friends, requests and blocked players only while the friends screen (or the server list / pause menu with friends
info) is open – about every 30 seconds, otherwise every 90 seconds or not at all. Friend requests, removing and
blocking are sent only when you click them. Friend faces are loaded from Mojang's public profile service
(sessionserver.mojang.com, textures.minecraft.net) and kept in memory only. The mod stores nothing of this on your
computer – except the servers you pin in the server list (config/cubiqclient/server-pins.json, only addresses, never
sent anywhere).
Cubiq badge in the game (Cubiq Client)
The Cubiq Client shows a small Cubiq badge next to the names of players who are playing with Cubiq right now: while they are in a world or on a server with the Cubiq Client, or while a game started by the Cubiq Launcher runs. A Cubiq user who only has the launcher open, or who plays with another client, gets no badge. For this, the Cubiq Client reports "in game" (version, mod loader and – only with "Server teilen" – the server address) about once a minute while you are in a world or on a server, and the launcher does the same while a game it started runs; both are the online status described below and stop when you leave the world or the game ends.
- Who sees it: whether someone is playing right now is only shown to players who are in game themselves – in practice other Cubiq players on the same server, next to names they see anyway. Everyone else gets "no badge". You always see your own badge. Players you blocked never see it.
- Turning it off: "Show Cubiq badge" (Einstellungen → Datenschutz) hides your badge from everyone. Setting your online status to "nobody" only hides you in friends lists – it does not hide the badge.
Sharing capes with friends
You can share a cape you uploaded with a friend once the team has approved it. Your friend gets an offer in the launcher and in the game and decides whether to accept it. For this the Cubiq server stores which cape was offered to whom, by whom and when, and whether it was accepted. After accepting, your friend can wear the cape like their own, and other Cubiq players see it on them. A friend may pass the cape on to their own friends (at most 20 players per cape).
- Who sees what: the creator sees everyone who has the cape or an open offer for it (with their Minecraft names), also players a friend passed it on to. A holder sees who gave it to them, the creator's name and the players they passed it on to themselves.
- Ending it: the creator can take the cape back from anyone at any time; this also removes it from everyone that player passed it on to. Everyone can give a shared cape back. Removing a friend or blocking a player cancels open offers between you two; capes already accepted stay until someone takes them back. Deleting the cape, a rejection by the team or deleting a Cubiq account removes the affected shares immediately.
Chat and social (Cubiq services)
With the Cubiq services on, you can write with your friends and in groups in the launcher and in the game.
- What is stored: your messages (text, replies, edits, server invites, waypoint cards), pictures you send, reactions, read positions, conversation mutes and group memberships. Messages are kept like in a normal chat until they are deleted – by you (for everyone), by a group owner, by the team or together with your account.
- Encryption: message texts, invites and group names are stored encrypted on the server (AES-256-GCM). Pictures are re-encoded by the server – this removes location data and all other metadata, and large pictures are made smaller – and stored encrypted as well. The key is kept separately from the data. The team only reads messages that were reported (see below); there is no general admin view of chats.
- Who sees what: a direct message only you and your friend; a group message the current members (players added later only see messages from the moment they joined). If you block someone, their messages in shared groups are hidden for you. After you stop being friends, a direct chat stays readable, but nobody can write in it any more.
- Read receipts and "is typing" are on by default and can be turned off in the privacy settings; then you don't see them from others either. "Is typing" is only kept in the server's memory for a few seconds.
- Server invites: when a chat shows a server address, the Cubiq server asks that Minecraft server for its icon, player count and description (the usual server list ping) and keeps the answer in memory for about a minute. Your IP address is not passed on – the Minecraft server only sees the Cubiq server. Addresses in local networks are never contacted.
- Waypoints: in the Cubiq Client you can send a waypoint (or your position) to a friend or a group. The card contains only the name you gave it, the coordinates, the dimension and the server address – for a singleplayer world only a short code calculated from the world folder, never the world name. Coordinates that appear in the normal Minecraft chat are recognised only locally in the Cubiq Client; saving them as a waypoint sends nothing anywhere.
- Realtime: while the launcher or the game is open, a connection to the Cubiq server delivers new messages and other updates (friend requests, online status, cape offers) right away. Missed updates are kept in the server's memory for up to 10 minutes so they arrive after a short disconnect.
Chat data on this PC
- Notification settings (corner, duration, sound, Do not disturb, which kinds) are stored only in the launcher's settings on your PC. Windows notifications are only shown while the launcher is in the background, and only if that switch is on.
- Pictures from your PC stay where they are. So they appear under "Uploads", the launcher remembers the paths of the
last 40 picture files you picked in
chat-uploads.jsonin its data folder; screenshots you star are remembered inscreenshot-favorites.json. Nothing of this leaves your PC unless you send a picture. Pictures pasted from the clipboard are only kept in memory until the launcher closes. - Pictures you receive are loaded by the launcher itself and only kept in memory while it runs – nothing is written to disk, and your Cubiq token never reaches the launcher window.
- "Last online" in the friend list is what the launcher itself saw (stored locally per account), not information from the server.
Shared screenshots
In the launcher's screenshot gallery and in the Cubiq Client ("Clips & pictures") you can share a screenshot as a link
(<this website>/s/…). Only the one picture you chose is sent, and only when you click
"Share as link"; your other screenshots stay on your PC.
- What is stored: the picture, re-encoded by the server (this removes location data and all other metadata; pictures larger than 4096 pixels are made smaller), its size and format, when it was shared and when it expires, and which Cubiq account shared it. The account is only used internally – for your list "My shared pictures", the limits and moderation. The public page and the picture show no player name and no UUID.
- Who sees it: anyone who has the link – there is no password. The link contains a long random code that can't
be guessed, and the page tells search engines not to index it (
noindex). If you post the link in Discord or a similar app, that app's servers load the picture to show a preview. - How long: 30 days, then the picture is deleted automatically. You can delete it earlier under "My shared pictures" in the launcher or the Cubiq Client – the link stops working right away (previews that other apps already made are outside our control). "Alle Cubiq-Daten löschen" deletes all your shared pictures.
- Limits: at most 10 MB per picture, 50 active links and 20 new links per day per account. An upload ban from moderation also blocks sharing.
- Reports: a shared picture can be reported, also directly on its page. A report from the page only sends the reason; the page stores no IP address (rate limits count in memory only). A report keeps a copy of the picture as evidence, like other reports (see below), and the team can delete shared pictures.
Sharing modpacks
In the launcher you can share an instance as a modpack (Instance → Share → Share modpack). The launcher packs the
mod list (mods that are on Modrinth are only listed with their download address) and the folders you pick
(e.g. settings/configs, resource packs, your own mod files) into a .mrpack file and uploads it only when you click
"Share". Worlds, screenshots, logs and account files are never included.
- What is stored: the pack file, its name, description and version, Minecraft version and mod loader, how many files it contains, when it was shared, updated and when it expires, how often it was installed, the sharing Cubiq account, and to which friends it was sent.
- Who sees it: anyone with the code (
CBQ-XXXX-XXXX) or the link (/p/…) sees the name, description, contents summary and your player name and head – so people know whose pack it is. Downloading the pack needs a Cubiq account (the launcher). Friends you send it to see it in their list "Shared with me". The page is not indexed by search engines. - How long: you choose per pack – 1, 7 or 30 days, or no expiry. Expired packs are deleted automatically; you can delete a pack earlier in "My modpacks" – code and link stop working right away (copies others already installed stay on their PCs). A new version keeps the code; friends who installed it see "Update available".
- Limits: at most 50 MB per pack, 10 shared packs and 30 uploads per day per account. An upload ban from moderation also blocks sharing.
- Reports: a pack can be reported in the launcher or on its page (signed in). The report keeps the pack's name, code, description, contents summary and checksum as evidence (not the file); the team can delete packs.
Circuit library (Cubiq Client)
The circuit library in the Cubiq Client (and on the website, /circuits) loads its circuits from the Cubiq server. It needs
no account: once per game start the Cubiq Client asks whether there are new or changed circuits and downloads only those;
they are cached in config/cubiqclient/circuits/. This only happens while the Cubiq online features are allowed. The
server only counts requests per IP address in memory (rate limit).
- Submitting a circuit (signed in, in the Cubiq Client or on the website): we store the circuit (only blocks and their states – no chest contents or other block data), the name, description, category and language you entered, your Minecraft UUID and name, the time, the status and the team's answer. Uploaded files are converted and discarded right away. Only team members whose role may manage the library see submissions.
- Your name is shown: if the team accepts your circuit, it appears in the library in the Cubiq Client and on the website with your Minecraft name (and your UUID for the head picture) as the creator. You confirm this before submitting.
- How long: decided submissions are deleted 90 days after the decision, open ones stay until they are decided. A published circuit stays until the team removes it; "Alle Cubiq-Daten löschen" deletes your submissions and removes your name from your circuits. You can ask us to remove a circuit of yours at any time.
- Limits and reports: at most 5 submissions per day; an upload ban from moderation also blocks submissions. Circuits can be reported like other content (see below).
Issues and bug reports
The public issue tracker on the website (/issues, /roadmap) is described in the website part of this policy. The launcher and the Cubiq Client use it like this:
- Notifications: if you follow an issue (you do automatically for issues you opened or commented on), the launcher gets an event over its existing Cubiq connection when the status changes, the team answers, a fix ships ("fixed in") or the issue is merged, and shows a social notification with a "View" button that opens the issue in your browser. Nothing is stored for this on your PC; the social notification settings apply.
- "Report a bug" in the Cubiq Client sends a title, your description and – only the parts you tick, shown before sending – the Cubiq Client version, the Minecraft version and loader, your mod list, an excerpt of the game log and a screenshot, together with your Cubiq account. The client removes access tokens, session ids, e-mail addresses, IP addresses, UUIDs and your player name from the log first, the server does it again. The issue, versions, mod list and screenshot are public on the website with your Minecraft name; the log excerpt only you and the team can see.
- How long: issues and comments stay while the tracker exists; "Alle Cubiq-Daten löschen" deletes your votes, follows, log excerpts and uploaded pictures, your issues and comments stay without your name.
Reporting bugs in the Cubiq Client
Cubiq Client menu → "Report bug" sends a bug report to the Cubiq issue tracker, signed in with your Cubiq account (Cubiq services must be turned on in the launcher). Nothing is sent before you press "Send now" on the preview page, which shows exactly what goes out.
- Always: title and description you typed, your Minecraft UUID and name (as the author of the report) and the time.
- Ticked by default: Cubiq Client version, Minecraft version and loader, list of mod file names in
mods/. - Only if you tick it: an excerpt of the game log (the last 300 lines of
logs/latest.log, or the start of the newest crash report) and one screenshot (the newest one or one you pick). - The log is cleaned on your PC before it's sent: access and session tokens,
--accessTokenand similar start arguments, UUIDs, your player name and account names, IP addresses, user names in paths (C:\Users\<name>→C:\Users\<user>), email addresses and the content of chat lines are replaced. The preview shows how many of each were removed. A screenshot is sent as it is – check what it shows. - Who sees it: the report appears publicly in the issue tracker on the Cubiq website (title, description, screenshot, versions, mod list and your name as author). The log excerpt is only visible to the Cubiq team and to you.
- Limits: a few reports per day; a sanction from moderation can block reporting.
Reports and moderation
You can report messages, pictures, players and groups (with a reason and an optional note). The report stores an encrypted copy of the reported content and of up to 10 messages before and after it, exactly as you could see them; reported pictures are copied. Team members whose role allows it review reports on the website or in the launcher and can delete messages, warn a player, mute them in chat for a while or ban them; every action is logged. The reporter only learns whether something was done, not what. The reported player doesn't learn who reported them.
Automatic protection: messages sent too fast or repeated many times are blocked and can lead to a short automatic mute; links and server invites in groups are only accepted from the owner or from players who are friends with everyone in the group; the team can keep a list of blocked words. If three different players report the same player within a day, that player is muted in chat until the team has looked at it. Players whose reports are often unfounded don't count for this.
Reports are kept while they are open and for 90 days after the decision (for objections); then the copies, notes and pictures are deleted, and the report itself (without content) is deleted after one year. If you delete your account, reports you filed stay without your name; reports against you and an active chat mute stay until these periods end, so moderation can't be escaped by deleting the account.
Sanctions and appeals
The team (members whose role allows it) can give sanctions for violations: a warning, a chat mute, a social ban (no friend requests, groups or invites), an upload ban (no own capes or cosmetics), a world hosting ban or a ban of the whole Cubiq account – for a limited time or permanently. We store your UUID, the kind, the reason (from a fixed list, plus an optional text you can see), start and end, who gave the sanction, an internal team note and every later change (shortened, extended, lifted – each with time, team member and reason). The team can also keep internal notes about players and sees the names an account used to sign in to Cubiq.
In the launcher and in the game you see your active and past sanctions with kind, reason, start and end – not the internal note and not who gave it. You can appeal each active sanction once (20 to 1000 characters); even with a banned account this works through a short access valid only for that (1 hour). A team member who did not give the sanction decides and writes you an answer.
Retention: sanctions with their changes and appeal are deleted 2 years after they ended (expired or lifted); permanent sanctions stay while they apply. Internal notes are deleted after 2 years, former names 2 years after their last use, entries in the team's audit log after 2 years. If you delete your account, warnings and ended sanctions are deleted at once; active sanctions (and notes about them) stay until they end, so they can't be escaped by deleting. The legal basis is our legitimate interest in a safe service (Art. 6(1)(f) GDPR).
Website sign-in and team applications
Website sign-in with Microsoft. On the Cubiq website you can sign in with the Microsoft account that owns Minecraft: Java Edition. We only receive your Minecraft UUID and name; the Microsoft, Xbox and Minecraft tokens exist in memory for a few seconds and are discarded – we store no tokens, e-mail or password, only a website session (8 hours).
Website sign-in with the Cubiq Launcher. Instead of Microsoft you can confirm a website sign-in in the launcher: the website shows a short code and opens the launcher (or you type the code under Settings → Privacy → "Sign in on the website"). The launcher then looks up the request and – only after you click "Confirm" – confirms it with the Cubiq token of the account you picked; "Decline" rejects it. The launcher sends only the request reference and the code; it shows the website, the code, a rough browser description (such as "Firefox · Windows") and the time of the request. The server keeps the request for at most two minutes (hashes of the link and of a browser value, the code, the rough browser description, after confirming your UUID) and then only the website session (8 hours).
News in the launcher. With the Cubiq services switched on, the launcher also loads the team's news posts from the Cubiq server (text and pictures; without your token – nothing about you is sent) and caches them locally.
Team applications: position, Minecraft name and UUID, Discord name, age group (never a birth date), your answers, status and our answer. Only team members whose role may review applications see them. Rejected or withdrawn applications are deleted 6 months after the decision, accepted ones 6 months after you leave the team; deleting your Cubiq account deletes them at once.
Hosting a world for friends (Cubiq Client)
In the Cubiq Client you can open your singleplayer world for friends ("Host world") without port forwarding. The Cubiq server only manages who may join and helps the two games find each other; the game itself never runs through the Cubiq server.
- Stored on the Cubiq server while the world is open: the world name, Minecraft version, mod loader and settings you chose (game mode, PvP, cheats, max. players, open/closed, visible to friends), the join code, who you invited, who asked to join and who you let in or banned (with times), and the player count your game reports. When you close the world, or 90 seconds after your game stops reporting, all of this is deleted. Friends see your open world only if you leave it visible to friends.
- Kept longer: only your own list of players you banned from all your worlds ("remember ban"), until you remove them or delete your Cubiq account.
- Connecting: the two games first try to connect directly. For this each game asks a STUN server (by default only the Cubiq relay server) for its public address and sends its connection candidates to the other player through the Cubiq server. With a direct connection, you and the other player see each other's IP address – like on any Minecraft server. These candidates are only passed through and kept at most 10 minutes in the server's memory for delivery.
- Cubiq relay: if a direct connection doesn't work, the game data runs through the Cubiq relay server (a separate server run by the operator of the Cubiq server). It only lets players in with a short-lived access key from the Cubiq server, sees the IP addresses of the connected games and forwards the bytes. It does not store or log any game data or IP addresses (only counters such as the number of connections) and keeps nothing on disk.
- Joining from the launcher: under Social → Worlds, in chat (world cards) and in notifications the launcher shows
your friends' open worlds and invites, and sends your "Join"/"Ask to join" to the Cubiq server with your Cubiq sign-in.
When you are let in, it starts a matching instance and hands the game only the world's ID and join code, over the
local connection on your computer (
127.0.0.1) – no access keys. The game then connects by itself as described above. The launcher keeps nothing about hosted worlds on disk. - Public link (e4mc): optionally you can create a public link that anyone can use to join. This uses e4mc, a
service by other operators, not the Cubiq server. When you turn it on (only after a warning you have to confirm), your
game connects to e4mc's relay and e4mc sees your IP address and the players' IP addresses and forwards the game data;
e4mc's own privacy policy applies. It is off by default. The first time you turn it on, the game downloads the
network library it needs (Netty with QUIC, open source) once from Maven Central (
repo1.maven.org, checked against fixed checksums) and asks e4mc's broker (broker.e4mc.link) for the nearest relay – both see your IP address. The e4mc part of the Cubiq Client is based on the e4mc mod (MIT licence, © Skye); its licence text ships inside the game. - Only through the relay: in the Cubiq Client (Social → "Direct connections") you can turn direct connections off. Then your game always uses the Cubiq relay and the other player never learns your IP address.
- World backup: before opening, the Cubiq Client can save a ZIP of your world in the game's
backupsfolder on your computer. It never leaves your computer. - Protection in the game: a guest can only log in with the name the Cubiq server confirmed for them (nobody can take the host's name), and when you remove or ban a player the game closes their connection at once.
Sharing a local server ("My servers")
- Addresses: to show how friends reach a server running on your computer, the launcher looks up your public IP
address at
api.ipify.org(or, if that fails, Cloudflare's1.1.1.1/cdn-cgi/trace) – both see your IP address. The result is only kept in memory for 10 minutes. "Check reachability" asks the Cubiq server to ping that address (like the server cards in chat). - Via Cubiq relay: the launcher opens a world room on the Cubiq server that only invited friends can see (same data and deletion rules as hosting a world above) and connects to the Cubiq relay itself; players reach your server through it and your server sees them as connections from your own computer. Invites are world invites with a card in your chat.
- Public link (e4mc): off by default and only after a warning; the launcher then connects to e4mc's broker and relay
(
*.e4mc.link), which see your IP address and the players' IP addresses and forward the game data. e4mc's own privacy policy applies. Turning it off or stopping the server ends the link.
Mods and resource pack when hosting a world
- Off by default. Only if you turn on "Share mods" or "Share resource pack" for a world does the Cubiq Client share
anything; the choice is remembered in the game folder (
config/cubiqclient/hosting-share.json). - What the Cubiq server stores (only while the world is open, deleted with it): the list of shared mods – name, version, file name, size, required/optional, source (Modrinth, CurseForge, directly from the host or "get it yourself") with project and file IDs and the files' checksums (SHA-1, SHA-512/SHA-256) – and for a resource pack its name, size and checksums. Everybody who may see your world sees this list. No files are ever stored on or sent through the Cubiq server.
- Recognizing your mods: to find out which mods are on Modrinth or CurseForge, the Cubiq Launcher reads the mod files
of your instance and sends their checksums (and CurseForge fingerprints) to Modrinth (
api.modrinth.com) and CurseForge (api.curseforge.com); without the launcher the Cubiq Client asks Modrinth itself. They see your IP address. - Files directly between the players: mods that are in no store (only if you turn on "Send mods directly from the host") and the resource pack go directly from the host's game to the guest – through the same direct connection or the Cubiq relay as the game, which only forwards the bytes and stores nothing. Only players you let into the world get them, and only exactly the files you chose. Guests download store mods themselves from Modrinth or CurseForge.
- Guests: the launcher shows the list on every join and checks every file (checksum and size) before using it. Mods
directly from the host are only installed after you confirm "I trust this host". The resource pack is only used if you
answer Minecraft's question with yes; your game serves it to Minecraft through a local address on your computer
(
127.0.0.1) that only works for this connection.
Achievements
The launcher has achievements (points, rarities, a few rewards such as a cape or a cosmetic). They are part of the Cubiq services and only work while those are on.
- What the server counts itself: time in game and day streaks (from the in-game status the launcher or the Cubiq Client sends anyway), friends, chat messages, issues and votes, circuits, shared packs, worlds, capes and cosmetics.
- What the launcher reports: a few facts only it knows – a game was started (with the local hour of the start, 0–23, for time-of-day achievements), mods or a modpack were installed (only the number), a clip was saved (only the number), the crash helper fixed something, instances were imported from another launcher. No names, files, paths or instances are sent. Reports are collected for a few seconds and sent in the background; nothing is sent without the Cubiq services or while you are offline.
- Stored on the Cubiq server: which achievements you unlocked and when, counters and flags per account, your total time in game with the current and longest session and your day streak (no history of sessions), and the switch "Achievements visible to friends".
- Who sees it: you and your accepted friends (points and unlocked achievements) – nobody else. With "Achievements visible to friends" off (achievements page or Einstellungen → Datenschutz) your friends only see that your achievements are private.
- How long: as long as your Cubiq account exists; "Alle Cubiq-Daten löschen" deletes all of it.
What is stored
| Data | Why |
|---|---|
| Minecraft UUID and player name | To identify your Cubiq account and show your name to friends |
| Account creation time and last sign-in time | Account management and abuse prevention |
| The address of your current Minecraft skin (a public link on Mojang's texture server), its model and when it was last seen | Showing your face in lists and your figure on the team page without asking Mojang every time |
| Session tokens (only as SHA-256 hashes, valid for 30 days, at most 10 per account) | Keeping you signed in |
| Your privacy settings (Cubiq badge, cape visible to others, online status visible to friends/nobody, share server) | So the services respect your choices |
| Your chosen cape, capes unlocked by codes or granted by the team | Showing your cape to other Cubiq players |
| Capes you upload (the image, re-encoded without metadata), their review status and an optional name | Cape uploads; every upload is reviewed by the team before others see it |
| Reports you file about other players' capes (reason, optional note) | Moderation |
| Cape shares: which capes you offered to whom (and who passed them on), open offers to you and the capes friends shared with you, each with the time and whether it was accepted | Sharing capes with friends (see above) |
| Friends, friend requests and blocks | The friends list |
| Online status: "online in the launcher" or "in game" (from the launcher or the Cubiq Client) with version and mod loader, and, only if you turned on "Server teilen", the server address | Showing friends what you play and letting them join you; showing the Cubiq badge while you play (see above) |
| Only with "Sync with Cubiq account" on: your own skins from "My skins" (the image, re-encoded without metadata, its name and model), your own mod presets (names and Modrinth project IDs, no files or folder paths) and your theme, accent colour and language, each with the time of the last change; deleted skins and presets are remembered for a short while | Keeping these the same on every PC where you use this Minecraft account |
| Only with the Cubiq services on and "Sync with Cubiq account" on in the Cubiq Client (in game): your Cubiq Client settings – which modules are on and their settings, HUD layouts and profiles, the Cubiq keys of the modules, the config mode for performance mods, whether you finished the introduction (and the module pack you picked) and which "NEW" entries you have opened – each part with the time of its last change; no waypoints, no server addresses, no files, paths or tokens | Keeping the Cubiq Client the same on every PC and game folder where you use this Minecraft account, and showing the introduction only once |
| Only with the Cubiq services on: the wardrobe entry of the Cubiq Client – your favourite skins, outfits (name, skin, cape) and emote wheel slots, with the time of the last change | The same wardrobe on every PC |
| Only with the Cubiq services on, "Sync with Cubiq account" on in the Cubiq Client and the notes switch "Sync with Cubiq account" on: your world notes from the Cubiq Client – title, text (including checklists and coordinates you typed), creation and change time, and the world they belong to (server address, or for a singleplayer world a code made from the world folder plus the folder name); deleted notes are remembered as an empty marker | The same notes on every PC |
| Chat: your messages (text, replies, edits, server invites), the pictures you send (re-encoded, encrypted), reactions, read positions, conversation mutes and group memberships, each with times | Chatting with friends and in groups (see above) |
| Chat settings: read receipts and "is typing" on or off | So the chat respects your choices |
| Shared screenshots (only the pictures you share): the re-encoded picture, size, format, share and expiry time, the sharing account (not shown publicly) | Sharing a screenshot as a link (see above) |
| Shared modpacks (only the packs you share): the pack file, name, description, version, Minecraft version, loader, file counts, share/update/expiry time, installs, the sharing account (name shown on the pack page), friends it was sent to | Sharing a modpack by code, link or with friends (see above) |
| Issues and comments you write, your votes and follows; with "Report a bug" in the Cubiq Client the parts you tick (versions, mod list, log excerpt – cleaned, only visible to you and the team – and a screenshot) | Reporting bugs, suggesting features, voting and notifications (see above) |
| Achievements: which ones you unlocked and when, counters and flags (e.g. number of game starts or installed mods, the local hour of a start), total time in game with current and longest session, day streak, and whether friends may see your achievements | Achievements and their rewards; visible to you and your friends only (see above) |
| Circuit submissions: the circuit (blocks and states only), name, description, category, language, time, status and the team's answer; for accepted circuits your name as the creator | Submitting a circuit to the library (see above) |
| Reports you file and reports about you, each with an encrypted copy of the reported content and its context; sanctions (warning, mute, bans) with their history and appeal, internal team notes, former names | Moderation (see above) |
| World hosting (only while your world is open): world name, version, mod loader and settings, join code, invited players, join requests, admitted and banned players with times, player count, shared mod list and resource pack info (names, sizes, sources, checksums – no files); your list of players banned from all your worlds | Hosting a world for friends (see above) |
Sync: "Sync with Cubiq account" (Einstellungen → Datenschutz, on by default while the Cubiq services are on) keeps your own skins, your own presets and the look of the launcher (theme, accent colour, language) the same on all your PCs. Java, memory and all other settings are not synced and never leave your PC. Turn the switch off to stop syncing; what was already synced stays on the server until you delete it with "Alle Cubiq-Daten löschen". Only you can read your synced data – there is no admin view of it.
Cubiq Client sync: the Cubiq Client mod signs in by itself (see above) and keeps its own settings in the same place, as one document of at most 64 KB per account. It only does this while the Cubiq services are on in the launcher and its switch "Sync with Cubiq account" (Cubiq menu → Cubiq Online Features, on by default) is on; the switch itself, waypoints, the freelook server list and Minecraft's own options (options.txt) stay on your PC. The game also reads your synced theme, accent colour and language and, when you change them in the introduction, writes them back so the launcher follows. Deleting all Cubiq data deletes this document too.
Cubiq Client notes: notes per world are saved on your PC in config/cubiqclient/notes (one file per world or
server). With the Cubiq services on and both switches on (Cubiq Online Features → "Sync with Cubiq account" and on the
World Notes page "Sync with Cubiq account", both on by default) the Cubiq Client also keeps them in your Cubiq account,
note by note, so they are the same on every PC. Which note is pinned to the HUD stays on your PC. Only you can read your notes – there is no admin view.
A deleted note leaves an empty marker for 90 days so your other PCs delete it too. Turn off the notes switch to keep
all notes on this PC; "Alle Cubiq-Daten löschen" deletes the synced notes.
The online status is kept only in the server's memory, is never written to disk, has no history and expires 3 minutes after the last update. It is visible only to your friends, and not at all if you set it to "nobody". Only whether you are in game right now can also show up as your Cubiq badge (see above).
Admin actions (such as approving a cape, a ban or a decision on a chat report) are recorded in an audit log together with the affected UUID.
Purpose and legal basis
The data is processed only to provide the Cubiq services you asked for: capes, the friends list, the online status, the chat and syncing your skins, presets and launcher look between your PCs. The legal basis is the performance of the service you requested (Art. 6(1)(b) GDPR). Keeping the services free of abuse (reviewing uploads, reports and their evidence, spam protection, mutes, bans and rate limits) is based on our legitimate interest in a safe service (Art. 6(1)(f) GDPR). There is no advertising, no profiling and no sale of data.
Retention and deletion
- Your data is kept as long as your Cubiq account exists.
- Session tokens expire after 30 days; signing out or removing an account from the launcher revokes the token.
- The online status disappears 3 minutes after the last update, or immediately when you close the launcher and leave the world.
- Synced notes stay until you delete them in the Cubiq Client or delete all Cubiq data; markers of deleted notes are removed after 90 days.
- Synced skins, presets and settings stay until you delete them in the launcher (a skin deleted on one PC is deleted on the server, too). Notes about deleted skins are kept for 30 days so your other PCs can delete them as well.
- Chat messages and pictures stay until they are deleted (by you for everyone, by the group owner or by the team) or the group is deleted. Pictures that were uploaded but never sent are deleted after 1 hour.
- Shared screenshots are deleted automatically 30 days after sharing, or earlier when you (or the team) delete them.
- Shared modpacks are deleted automatically when the duration you chose ends (1, 7 or 30 days; "no expiry" stays until you or the team delete it).
- Decided circuit submissions are deleted 90 days after the decision; published circuits stay until the team removes them (without your name after "Alle Cubiq-Daten löschen").
- "Alle Cubiq-Daten löschen" (Einstellungen → Datenschutz) deletes everything immediately (GDPR Art. 17): your account, sessions, friendships, requests and blocks, uploaded capes and their files, cape shares (your capes with friends and the capes friends shared with you), code redemptions, reports, your online status, all synced skins, presets and settings, all your direct chats (for both sides) and your messages, reactions and pictures in groups (groups you own go to the longest member), all pictures you shared as a link, all modpacks you shared and your achievements with their counters. Afterwards the Cubiq services are turned off in the launcher. The skins and presets on your PC are kept.
- Only active sanctions (such as a ban or a running chat mute, with reason and period) and reports about you (until their retention ends, see above) are kept after deletion, so they can't be escaped by signing in again.
- Server logs contain only technical data (method, path without query, status, duration, request id) – no IP addresses and no tokens. Rate limits count requests per IP address and per account in memory only; those counters are never written to disk.
Hosting and processors
- Where the Cubiq server runs and which processors it uses: see "This website" above.
- Mojang/Microsoft confirms the sign-in (see above): your computer sends the join request to Mojang directly, and
the Cubiq server asks Mojang with your player name and the one-time challenge (
hasJoined). - Minecraft servers in chat invites are contacted by the Cubiq server (server list ping) to show their icon and player count; they only see the Cubiq server's address.
- Cubiq relay server (world hosting, see above): a separate server run by the operator of the Cubiq server; it only forwards game data and keeps nothing on disk.
Your rights
You have the right to access, rectification, erasure, restriction of processing, data portability and objection (Art. 15–21 GDPR), and the right to lodge a complaint with a supervisory authority. Most of this you can do yourself in the launcher (turn the services off, change the privacy settings, delete all data). For anything else, contact us.
Contact
PwiePixel – open an issue at https://github.com/PwiePixel/Cubiq-launcher/issues. Please don't post personal data in public issues; ask for a private contact instead.
You can lodge a complaint with a data protection supervisory authority, in particular in the EU member state of your residence or of the controller.