Privacy
Your game data lives primarily on your own device. This page explains what the website, launcher and optional network features process.
Scope and maintainers
This policy covers the CobbleLauncher project website and launcher, provided by the open-source project maintainers. Third-party login, content platforms, servers and plugin providers process data under their own policies.
Visiting this website
This site has no advertising, analytics scripts, account registration or file uploads. Browser local storage saves only language and theme preferences. Clear this site’s data in your browser to remove them.
Cloudflare Pages hosts this website. To deliver pages and secure its network, Cloudflare may process IP addresses, request times, URLs, browser and connection information. See the Cloudflare Privacy Policy. Website requests do not include your local game files.
Games and accounts on your device
Instance settings, player profiles, download records, game logs, worlds and backups are stored locally. Cobble does not require its own cloud account or automatically upload these files.
Microsoft sign-in contacts Microsoft, Xbox and Minecraft services for authorization, profile information and game entitlement checks. Credentials use the existing system credential store, with session-only storage when persistence is unavailable. Offline profiles retain the local name you enter.
Network services you use
Searches, downloads, update checks and plugin catalog requests send necessary information to the chosen service, such as project identifiers, versions, search terms and file URLs. Services can see connection information such as your IP address. Providers may include Microsoft, Mojang, Modrinth, CurseForge, BMCLAPI, GitHub, and mirrors or catalogs you add.
Public avatars, skins, icons and metadata may be cached locally. Account sign-in, applying skins and other authenticated actions follow the relevant provider’s authorization rules.
Optional Cobble Mesh
When enabled, Mesh connects to directories, seeds or relays and uses a local key to establish a verifiable identity. Public identifiers, display names, invitations and connection information needed for multiplayer are shared with relevant nodes or peers. Private keys stay local.
Peers and services receive data and traffic metadata required for connections; relays carry established game traffic. Invitation recipients can share invitations further, so treat them as connection credentials. Disabling Mesh stops future connections but cannot recall information already received by others.
Plugins, diagnostics and AI
Plugins use host capabilities according to their declarations and your grants. Network access, folder access and other sensitive actions require the corresponding permissions. Plugins and their providers may have separate policies; review them when installing or granting access.
Logs, configuration and diagnostic results leave your device when you choose to share, export or submit them. Optional AI features send selected text or diagnostics to the model service you configure. Review the contents and that service’s data policy first. Redaction may not remove every piece of personal information.
Retention, removal and choices
Local data remains until you delete it, clear it or the applicable cache or log retention rules remove it. You can manage profiles, clear caches, uninstall plugins, revoke folder grants, disable Mesh and revoke account authorization at the provider. Removing the launcher program does not necessarily remove separate game folders or backups.
Third-party retention is governed by their policies. Contact the maintainers about accessing, correcting or deleting information they hold, or exercising rights available under applicable law. The project cannot promise to remove data outside its control.
Minors, changes and contact
Where local rules require it, minors should have a guardian help them understand account, network and sharing features. This page’s date changes with policy updates; operations requiring new permissions still follow their corresponding authorization flow.
To contact the maintainers, describe the type of request first. Do not post tokens, private logs or personal information in a public issue; arrange an appropriate channel if more information is needed.