Privacy Policy

Last updated: 23 October 2026

KLP Launcher is a desktop program that runs on your own computer. Its main work, such as managing instances, downloading game files and launching the game, happens locally and does not pass through our servers. This page sets out what leaves your machine, where it goes, and where things are stored. Each statement corresponds to specific behaviour in the launcher. If you find one that does not match what the launcher actually does, please contact us and we will correct this page or the implementation.

Accounts and sign-in

The launcher never handles, displays or stores your Microsoft password.

Sign-in uses Microsoft's official device code flow: the launcher shows you a verification URL and a short code, and you complete the sign-in in your own browser, on Microsoft's own page. Your password never passes through any field in the launcher.

After a successful sign-in, what the launcher stores are the tokens returned by the Microsoft and Minecraft services (refresh token, access token, expiry, Xbox user id), so that you do not have to sign in again next time. If any sign-in method requires you to type a password, that password is used only for that one request to the corresponding sign-in service and is not retained in application state after the request finishes. It is not written to account files or sent to our servers.

Where tokens are stored

This differs by platform, as set out below. Forum sign-in, Codex channel credentials and any API keys you enter are stored the same way.

macOS, installed build: in the system Keychain, encrypted by the operating system.
Windows: in the installed build, the portable build and with a custom data directory, everything is encrypted with the system's DPAPI before it is written to disk; account files contain no plain-text tokens. The installed and portable builds keep them in %APPDATA%\KlpLauncher by default, so the portable build does not put them in its own folder. The DPAPI key is derived from the current Windows user's sign-in credentials and cannot be decrypted on another computer or by another Windows user.
Game accounts set to "This folder only" in the Windows portable build: stored in the .klpl directory inside the portable folder. Credentials are still DPAPI-encrypted; the account name and UUID are plain text. After the folder is copied to another computer the credentials cannot be decrypted, and you will need to sign in again.
macOS portable build, a custom data directory on macOS, and Linux: in accounts.json and secrets.json inside the data directory, with file permissions restricted to the current user (0600), but without additional encryption.

On the macOS portable build, with a custom data directory, or on Linux, any program able to read your data directory can read those tokens, and copying the whole folder onto removable storage copies the tokens with it. On Windows, DPAPI stops the tokens from being used on another computer, but programs running as you can still decrypt them.

Game account tokens are never sent to our servers. They only go to the service that issued them. Microsoft account tokens only go to the official Microsoft, Xbox Live and Minecraft endpoints, to sign you in to the game itself.

What we do not collect

No telemetry or analytics for ordinary launcher actions. The free AI channel records usage by forum account, as described below.
Manual launches do not report crashes automatically. If the AI assistant launched the game, a crash report is sent to that AI conversation automatically; on the free channel it passes through our relay. A launch approved through the AI assistant also sends an exit summary automatically.
We do not collect Microsoft passwords or game sign-in tokens. Forum sign-in and the free AI channel use separate identity tokens.
No contents of your saves, worlds or mod files.
No ads and no third-party tracking code in the launcher. For visitor statistics on this website, see "Website analytics" below.

What the launcher asks our servers for

The launcher requests updates, news and AI configuration from api.klp-launcher.com. Forum sign-in and the free AI channel also make identity-related requests:

Update checks: the request path contains only the operating system (windows / darwin / linux) and the CPU architecture (such as x86_64 or aarch64). A query parameter carries the current version to select an update channel. There is no machine identifier and no account information.
News and server-directory content: fetching lists and detail pages, the same as browsing a website.
The AI assistant's system prompt and skill manual: text sent down to the launcher with a digital signature; if the signature does not verify, the launcher uses the copy built into the program. This only downloads and uploads nothing.
Forum account and free AI channel: after forum sign-in, our service issues an identity token for the free channel. AI requests pass through our relay, which records usage against the forum user identifier.
CurseForge content proxy: if you have not entered your own CurseForge API key, CurseForge search, detail, file-information and mod-identification requests are forwarded through our server. They contain search terms, project IDs and, when identifying local mods, file fingerprints (hashes of the file contents, not the files themselves), and no account information.

As with any network request, our server sees your IP address while handling these. We do not attach an account to ordinary content requests. Sign-in and free AI requests are associated with a forum account.

The AI assistant

The AI assistant has several connection modes. The own-key channel connects directly to the model service you choose. The free channel requires a forum account; its requests, including conversation content and tool results, pass through our relay before reaching a model service. The Codex channel connects using the corresponding account. Choose a channel you trust.

The following content may be sent to the model provider used by your channel; on the free channel it also passes through our relay. The provider's terms and privacy policy govern how it processes and retains data.

What may be sent when you ask a question or ask it to diagnose a problem

Your question and the context of the current conversation.
Images you attach in the input box. At present only the own-key DeepSeek channel accepts images, and they are first uploaded to DeepSeek's file endpoint.
Game logs (by default the tail of latest.log, distilled to the important lines; you can also ask it to read the full file).
The full text of crash reports.
The mod list of the instance, along with versions and loader information.
Device information: CPU model and core count, machine model, architecture, memory size, operating system name and version, free disk space.
File paths, including Java installation paths and instance paths.

The launcher currently performs no redaction on any of this. Logs, crash reports and paths normally contain your home directory name (for example C:\Users\YourName\…). If your system username is your real name, it may appear verbatim in what is sent to the model provider; on the free channel this content also passes through our relay.

Where conversations are stored

Conversation history is stored on your computer under ai/sessions/ in the data directory, one file per conversation. Storing it locally does not mean requests are processed only on your device: the free channel sends each request and its context through our relay and records usage by forum user identifier.

How to disable it

If you do not want to use the AI assistant, simply do not start a conversation. You can also sign out of the forum account used by the free channel or remove your own-key provider configuration. Your own API keys are not included when settings are exported.

Third-party services

The launcher contacts the following services in response to what you do. Each has its own privacy policy, in respect of which this project can give no undertaking.

Microsoft / Mojang: authentication, and downloading the game itself, its assets and libraries.
Modrinth, CurseForge: searching for and downloading mods, modpacks and resource packs.
Mirror nodes: faster downloads of game files. When the download source is set to "Automatic" (the default for new users), region and interface language decide whether a mirror is used; you can choose a specific source in settings.
MCIM content mirror (mod.mcimirror.top): a caching mirror of Modrinth and CurseForge content, on by default on networks in mainland China. When the region cannot be detected, the interface language decides: it is on for Simplified Chinese and Classical Chinese. It can be turned off in settings.
Cloudflare: unless you have set both the content mirror switch and the download source yourself, the launcher makes one request to www.cloudflare.com/cdn-cgi/trace at every launch. Only the region code is read, to decide whether the content mirror is on by default and which source the "Automatic" download option uses.
Community mod translation service: translated mod names and summaries are fetched for the current interface language; requests contain the project ID and name. When a search term contains Chinese, Japanese or Korean, the term is also sent, together with the selected game version and loader.
The official Fabric, Forge, NeoForge and Quilt sources: loader files.
Adoptium: automatically downloading the Java runtime an instance needs.
Reference sites, video sites and search engines: contacted only when the AI assistant needs to look something up; the search terms and the addresses it reads are sent to those sites. On the own-key DeepSeek channel, web search and page reading go through DeepSeek's official endpoints first, so search terms and addresses are sent to DeepSeek.
Crafatar: fetching your skin avatar by account UUID.

Website analytics

This website (klp-launcher.com) uses 51.LA to count visits and see where visitors come from. When you open a page, your browser loads an analytics script from sdk.51.la and sends 51.LA the page you visited, the referring page, your IP address, and browser and device information. The script also sets a cookie to tell new visitors from returning ones. 51.LA handles this data under its own privacy policy. We only look at aggregate reports and never link them to launcher or forum accounts. The launcher itself does not contain this script.

If you do not want to be counted, block sdk.51.la or disable JavaScript in your browser. Browsing and downloads keep working.

Children's privacy

Game accounts are managed by Microsoft; the free AI channel also uses a forum account. Parental controls and age-related rules are governed by the relevant account services' policies.

Changes to this policy

When features or data flows change, this page is revised and the date at the top is updated. If a change ever leaves this page out of date, that is an oversight on our part; please let us know so that it can be corrected.

Contact

For privacy questions, correction requests, or if you find a sentence on this page that does not match the actual implementation:
please email admin@klp-launcher.com.

← Back to home