Clear about what stays local, and what has to travel.
Ferrite is a desktop launcher. Its data flows are shaped by Minecraft services, content providers and the diagnostics a player chooses to export.
Local application data
Ferrite stores settings, instances, caches, logs, provisioned runtimes and backups under its data root. The root can be moved from Settings. Destructive operations preserve copies in backups rather than deleting user content in place.
Accounts and tokens
Microsoft sign-in uses OAuth device code or authorization code with PKCE; Ferrite never asks for or stores a Microsoft password. Persisted token material is protected with Windows DPAPI on Windows. Non-Windows environments use a degraded file-based mode and disclose that state in the application.
Provider communication
Content discovery and downloads communicate with services such as Mojang, Modrinth and CurseForge over HTTPS. These providers receive the requests needed to return metadata and files. Ferrite does not present those integrations as official partnerships.
Diagnostics and support bundles
Logs and support bundles can include system information, operation history, Java/platform details and recent instance output. Ferrite redacts access tokens and bundled provider credentials before writing diagnostic output. Exporting a bundle is a user action; review it before sharing.
Website
This static website does not require an account and does not include analytics or marketing cookies in its initial release. The site links to third-party repositories and provider websites, which have their own policies.