LumaClient 3.0.0 Back to the website

Legal documents

Privacy Policy

This policy explains what information LumaClient uses, where it is stored and when it is sent to external services.

Last updated: August 8, 2026

1. Summary

The current version of LumaClient does not send its own telemetry to count installations or active users. Settings, accounts, session history and mod profiles are stored locally on your computer. Data is sent to external services only when a selected feature requires it.

2. Controller and contact

The LumaClient project is run by Eryczus (_eastplaya). For privacy-related questions, contact the project through the Discord server or its GitHub repository.

3. Data stored locally

  • appearance, language, RAM and launcher behavior settings;
  • installation names, Minecraft versions and assigned mod profiles;
  • nickname, UUID and tokens required to maintain a Microsoft account session;
  • local launch history and application logs;
  • an optional AI service key saved by the user.

Configuration data is stored mainly in %APPDATA%\.luma. Protect your Windows account and do not share files containing tokens.

4. Microsoft and Minecraft sign-in

During sign-in, LumaClient communicates directly with Microsoft, Xbox Live and Minecraft Services. Data required for authentication is transmitted, and the returned tokens and profile data are stored locally to maintain the session. LumaClient does not receive your Microsoft account password.

5. Mods, versions and updates

Queries for mods and their files are sent to Modrinth. Game version and asset information may be downloaded from Mojang services. Update checks use the GitHub API and GitHub Releases. These providers may process standard network information such as your IP address, request time and application information.

6. AI log analysis

This feature runs only after you deliberately request an analysis. The final part of the log — up to approximately 4,000 characters — is sent to Groq to generate a response. A log may contain the player's nickname, mod names, versions, parts of file paths or error details. Do not include passwords, tokens or other secrets in a log before sending it.

7. Avatars and Discord Rich Presence

To display an avatar, the launcher may download an image from Crafatar, MC-Heads or Minotar, including the player's UUID in the request URL. If you enable Discord Rich Presence, activity information such as your nickname and game version is sent to the local Discord application and displayed according to your Discord settings.

8. Website

The website is hosted by Netlify. It currently contains no advertising or analytics scripts and does not set its own cookies. Netlify may process technical request logs required to deliver the site, protect the service and produce infrastructure statistics.

9. Deleting data

You can delete launcher data by removing accounts in the application and then, after closing it, deleting %APPDATA%\.luma. Uninstalling the application may not automatically remove configuration files or downloaded Minecraft files.

10. Future analytics

If anonymous installation or activity counting is added to LumaClient, it should include a clear consent control. Before public release, this policy will be updated with the provider's name, the events collected, the retention period and the method for withdrawing consent.

11. Your rights and policy changes

For questions about accessing, deleting or explaining the processing of data, contact the project through Discord or GitHub. Changes to this policy will be published on this page with an updated date.