← Back to home

Privacy Policy

Effective 2026-04-18 · Private Beta

Plain-language summary — Blue Client stores your Microsoft login tokens on your own computer so you don't have to sign in every time. It does not send gameplay telemetry, analytics, or personal data to us. Beta access is tracked via Discord. Details below.

1. Who we are

"Blue Client" (referred to as "we", "us", "the Client") is an independent Minecraft 1.8.9 client in private beta. We are not affiliated with Mojang Studios or Microsoft.

2. Data stored on your device

The Client writes the following files to your computer. None of this leaves your machine unless required by the services listed in Section 3.

  • Microsoft authentication tokens (access token, refresh token, profile UUID and username) in %APPDATA%/UnJava/auth.json or the equivalent path on macOS / Linux. Used to keep you signed in to Minecraft.
  • Launcher and mod configuration (HUD positions, enabled mods, game settings) in local config files.
  • Screenshots saved to a local folder when you use the screenshot feature.
  • Resource packs you install.

3. Third-party services

The Client communicates with the following external services, controlled by their respective operators under their own privacy policies.

  • Microsoft authentication endpoints to sign in to your Xbox Live / Minecraft account. We never see your Microsoft password.
  • Minecraft session and profile APIs (sessionserver.mojang.com, api.minecraftservices.com) to authenticate server joins.
  • Minecraft servers you connect to. These see your IP address, username, UUID, and in-game actions. This is the same as vanilla Minecraft.

4. Data we collect on our side

Beta participation: To grant beta access, we associate your Discord ID with an invite record. We may also store your Minecraft username / UUID when you receive a build so we can recognize it in crash reports you voluntarily share.

No gameplay telemetry. The Client does not send tick-level, position, or session data to us.

No analytics tracking on this website at the time of writing. If that changes (e.g., for basic privacy-respecting page counts), this policy will be updated.

Voluntary crash reports. If the Client crashes, it may produce a local log file. You decide whether to share it in the Discord. We do not auto-upload anything.

5. Cookies

This website does not use cookies.

6. Data retention

Local data on your computer stays until you delete the Client's config folder or uninstall. Discord-side beta records are retained while the beta program is active and may be purged at public release.

7. Your choices

  • Sign out / delete local tokens: sign out in the launcher, or delete auth.json.
  • Leave beta: leave the Discord. Your beta record will be removed on request.
  • Data deletion requests: ask in Discord (DM an admin) or via any email address we announce later.

8. Children

This beta is intended for users who can agree to Minecraft's own age requirements on their own account. We don't knowingly maintain beta records for users under the applicable age of consent in their country.

9. Security

We do our best, but no software is perfectly secure. Keep your computer and Minecraft account credentials safe. If you suspect your auth.json was exposed, sign out and revoke sessions from your Microsoft account settings.

10. Changes

This policy may change as the project evolves. Material changes will be announced in the Discord. The "Effective" date at the top reflects the current version.

11. Contact

Questions about this policy go in the Discord.