Privacy Policy — EG Launcher

Last updated: 2026-11-08
Project: EG Launcher
Operator: Egyéni Vállalkozás
Contact: info@eg-launcher.xyz · abuse reports: abuse@eg-launcher.xyz · Contact form
This policy describes what EG Launcher (“the app”, “we”) does with information when you install and use the desktop application, https://eg-launcher.xyz, community pack hosting, and related optional online services. Related: Terms of Service.

EG Launcher is free to use; its source code is proprietary and not public (All Rights Reserved, see LICENSE). This document is provided for transparency; it is not legal advice.

1. Summary

2. Distribution channels

3. Data stored on your device

The app stores data locally (paths depend on OS; typically under your user application data / the install directory), including for example:

• Launcher settings (theme, Java path, allocated RAM, preferences)
• Game instances, content you add (mods, resource packs, etc.), and related files
• Microsoft account session material needed to launch Minecraft (tokens / profile info cached by the launcher — not your password)
• Minecraft Offline play names (username only, local)
• Optional partner unlock state if you use those features
• Temporary files used during installs / updates
• UI preferences (e.g. pinned partners) where applicable
• EG community session tokens when you sign in for pack publishing

You can remove local data by uninstalling the app and deleting remaining data folders (clear remaining data under your user profile if needed).

We do not have access to files that never leave your computer.

4. Microsoft account and Minecraft

To play Minecraft: Java Edition, you sign in with a Microsoft account that owns the game (device-code / OAuth-style flow).

• Authentication is handled with Microsoft / Xbox / Minecraft services.
• The app uses the resulting tokens/profile to launch the game and show your username/skin-related info as needed.
• We do not operate Microsoft’s login pages and do not see your Microsoft password.
• Microsoft’s consent screen may show an OAuth application name configured in Azure (historically a shared public client used by open-source Java launchers). That name is not EG Launcher’s product name; login still completes inside EG Launcher.

See also:

• Microsoft Privacy Statement
• Minecraft / Mojang privacy information (or current Mojang/Microsoft gaming privacy docs)

5. Third-party services the app contacts

Depending on features you use, the app may send network requests to:

Those providers process data under their own privacy policies. We do not control Microsoft or the third-party mod catalog.

The app talks about “content” and a “mod catalog” in the UI so the product does not depend on a specific third-party brand name. Network traffic for content still goes to the catalog provider’s infrastructure when you search or add content.

6. EG Launcher CMS and optional online features

The launcher may call a CMS API (default host documented in the project, overridable via configuration) for:

• Home / launcher news
• Partner definitions, partner news/events
• Featured packs
• Community packs (list, detail, download, publish, my packs, staff review)
• Optional ad unit HTML (when ads are enabled)
• Staff / admin features (only if you sign in as staff)

The public website https://eg-launcher.xyz (news, forum, FAQ, contact, pack listing) uses the same operator and, for packs, the same MariaDB / object storage.

6.1 Normal users

Typical CMS calls are content fetches (news, partners, pack lists, etc.). They may log standard web server data (e.g. IP address, user agent, time, URL) for security, debugging, and reliability. Pack download requests increment a counter.

6.2 Staff / admin users

If you use Settings → Staff (or related admin tools):

• You authenticate against the CMS with credentials/session tokens managed by the project operators.
• Session information (e.g. session token, approximate login time, IP) may be stored on the server for security and idle timeout, as implemented in the CMS.
• Staff accounts may require a bound recovery email for password reset; that email is used only for account recovery / security notices as implemented.
• Do not use staff accounts on shared or untrusted machines.

6.3 Minecraft Offline vs EG account

Minecraft Offline accounts (username only, via Add an Account → Offline) stay on your PC and are never used to publish packs. They are not CMS identities.

EG Register / Login is a separate community account (same web_users table as https://eg-launcher.xyz) used for pack upload and related CMS features. Passwords for EG accounts are handled as implemented in the app and CMS; treat them as sensitive.

Partner unlock features, if enabled, are separate from Offline play names.

6.4 Community packs

If you publish a pack:

• We store pack metadata (title, short description, description, version, changelog, Minecraft version, loader, hashes, size) and an optional icon (≤ 512 KB).
• The .egpack file is uploaded directly to object storage with a time-limited URL. PHP does not keep the full file in memory.
• We record which account uploaded it (EG community session, staff / partner session, or a Microsoft profile id after the CMS checks your Minecraft access token with Mojang/Microsoft). Minecraft Offline play accounts are not CMS identities.
• Staff can download a pending pack to test it, then approve or reject it (reject includes a note visible to you).
• Approved packs are public: listed in the launcher and on https://eg-launcher.xyz/packs/, downloadable by anyone.
• We may delete the object and database rows (admin remove, failed validation, expired drafts).

If you only browse / install packs, the CMS sees list/get/download requests (IP, user agent) and the storage host sees the download. Mods inside a pack are fetched from the mod catalog CDN, not from our object storage.

7. Advertising

Current public builds may ship with the in-app ads banner disabled until advertising is approved and turned on.

If ads are enabled in a future build:

• The app may load ad content (e.g. via an iframe / ad unit hosted with the CMS, potentially including Google AdSense).
• Ad networks may use cookies, device/browser identifiers, and IP addresses per their policies (e.g. Google Privacy Policy).
• We do not sell ad audience lists ourselves; ad personalization is controlled by the ad provider and your OS/browser choices where applicable.

8. Updates

• Windows setup.exe: in-app auto-update from eg-launcher.xyz (/downloads/latest.yml). Builds older than 3.2.3 checked GitHub Releases instead. Checks after launch and periodically; you confirm before download/install.
• Linux AppImage: download a new AppImage from eg-launcher.xyz/download when you want a newer version.
• Only the current version is stored on the website (/downloads/). When a new release is published, previous setup.exe / AppImage files are deleted. Auto-update always points at the current files.

9. Analytics and tracking

EG Launcher does not include a separate first-party analytics product (no “phone-home” usage dashboard of our own beyond the CMS/content and third-party services above).

Third parties (Microsoft, the mod catalog, our hosting providers, and optionally Google ads) may collect technical data as part of providing their services.

10. Children

The app is a Minecraft launcher. Minecraft and Microsoft accounts have their own age and parental rules. We do not knowingly collect personal data from children independent of those platforms. If you believe a child has provided data to our CMS inappropriately, contact us at info@eg-launcher.xyz or via the contact form so we can delete staff/server records we control where applicable.

11. Data retention

12. Your choices

• Don’t use optional online features — you can skip Community packs, partners, and the website; core play still needs Microsoft/Minecraft, and adding catalog mods needs the mod catalog.
• Don’t publish packs — uploading is optional.
• Sign out / remove accounts in the launcher where available.
• Uninstall and delete local data folders.
• Staff: sign out; ask operators to revoke sessions if needed.
• Email info@eg-launcher.xyz or the contact form — request deletion of personal data stored on infrastructure we control (e.g. staff accounts, pack listings tied to your account), where feasible.
• Abuse / misuse / pack takedown — abuse@eg-launcher.xyz

For data held only by Microsoft, the mod catalog provider, or an ad network, use those providers’ privacy tools.

13. International transfers

You and the servers you reach may be in different countries. Microsoft, the mod catalog, our website and CMS hosts, and pack object storage may process data in the EU, US, or elsewhere. Use of the app implies data may cross borders as needed to provide the services above.

14. Security

We aim to keep tokens and credentials handled with reasonable care (local storage permissions, HTTPS for CMS where configured, session expiry for staff). No method of transmission or storage is 100% secure. Protect your Microsoft account with a strong password and 2FA.

15. Source code

EG Launcher is proprietary and its source code is not public. This policy applies to official builds downloaded from eg-launcher.xyz and to the project’s CMS as operated by the maintainers. Unofficial or modified builds are not covered.

16. Changes

We may update this policy by editing PRIVACY.md in the repository and changing the Last updated date. Continued use of new versions of the app after changes means you accept the updated policy for that version.

17. Contact

Canonical privacy policy URL:

https://eg-launcher.xyz/privacy/

(or the same path on the default branch if it is renamed later).