ONYX PRIVACY NOTICE Version 2026.10.20.3 Effective 20 October 2026 Onyx has no operator account server, analytics, advertising SDK, automatic telemetry upload or automatic crash report upload. The app processes the following information locally and communicates directly with the providers needed for the features you choose. Microsoft sign in You sign in on Microsoft's page in your browser. Onyx never asks for or stores your Microsoft password. It requests XboxLive.signin and offline_access so it can verify your Minecraft account and refresh an authorized session. Microsoft, Xbox and Minecraft receive the authentication requests. Onyx receives tokens and public profile details such as your Minecraft username, UUID and skin URL. The app registration ID is public, not a password or client secret. Each game launch rechecks Minecraft Java ownership and the authenticated profile with Minecraft services, even when the saved access token is unexpired. Expired or near expiry sessions refresh through the provider authentication chain. Verification failures block gameplay; no cached offline fallback is used. Opening the launcher or reading its initial local account summary does not start these ownership requests or sign you in automatically. Local session protection Access and refresh tokens are encrypted with Windows DPAPI for the current Windows account. The account file is restricted to that user and Windows SYSTEM. Tokens are excluded from frontend snapshots, ordinary settings and launch argument files. Game arguments use a private inherited pipe instead of placing the Minecraft token on Java's command line. Responses and temporary token buffers controlled by Onyx are cleared when no longer needed where practical. These measures do not make tokens impossible to steal. Minecraft must receive its access token in memory. Mods inside that game, same user malware, memory inspection or an administrator may still obtain it. Neither DPAPI nor these terms isolate untrusted code. A Java path you choose must also be trusted. Other network requests Game and asset downloads contact Mojang or Microsoft's infrastructure. Loader and mod requests contact the selected providers, including Fabric, Forge, Modrinth and OptiFine. Managed Java downloads contact Adoptium and its download hosts. Those providers receive ordinary connection information such as your IP address, requested version and the app's user agent. A skin image may be loaded from textures.minecraft.net. Microsoft Edge WebView2 is a separate Microsoft component subject to Microsoft's own terms and privacy policies. Pinned servers and game interface Server pins, UI appearance, HUD layouts, launch presets, vanilla game option presets and last local world names are stored locally in onyx_data.json with a previous copy. The game interface receives your public profile name and account mode, not the encrypted account store or refresh token. Manual server status checks contact only the address you choose. Automatic checks are off initially; if you enable them, opening the game menu contacts saved servers. Those servers receive ordinary connection information, including your IP address. Joining a server uses Minecraft's normal connection process. In game paste reads your clipboard only after you request paste in a text field. TierTagger and live overlays The selected TierTagger mod on Minecraft 1.21 profiles fetches public player rankings from its tier list providers, including MCTiers and SubTiers. Those requests are made by the upstream mod and can include public Minecraft player identifiers and ordinary connection information. Its own settings control its features. You can disable its installation in CORE MODS before starting the game. This does not affect Microsoft sign in. Onyx does not provide a tier list account or store tier service passwords. Onyx live HUD values, widget positions, module settings and game profile shader selection metadata stay in local preferences. The optional RAM widget reads the running Minecraft process working set on supported Windows runtimes. If that native counter is unavailable, an explicit HEAP label identifies Java used heap instead. No memory readings leave the device. No CPU or GPU identification is collected by this overlay. Presets name an existing local shader pack; they do not upload packs. Local data Settings, version choices, selected mods, worlds, caches and launcher logs are kept under %LOCALAPPDATA%\dev.onyx.launcher unless you choose another data root. Device login codes are temporary and are not stored in the launcher log. The current game's access token and saved refresh token are redacted from bridged console output. Mods can still write their own files or unusual logs; inspect logs before sharing them. Clipboard buttons copy only after your click. Display preferences and the accepted terms version are stored locally. Control and retention Sign out removes Onyx's encrypted account file. Gameplay stays blocked until you sign in and live ownership and profile verification succeeds again. It does not revoke Microsoft's existing consent; manage that in your Microsoft account. The application keeps worlds and settings until you remove them. Uninstalling does not automatically erase saved worlds. You can inspect, export or remove local data through the data folder. The uninstaller's optional delete app data checkbox also deletes worlds in the default data folder. Leave it unchecked to retain them. Sign out before uninstalling to remove the local session while keeping worlds. A custom data folder is retained by uninstall. Do not delete a world while the game is running. There is no Onyx hosted database to request deletion from. Questions Contact the distributor who supplied your build using the contact information provided with it. Never include passwords, device login codes or tokens in a support request. The project owner should provide a direct support and privacy contact with any public distribution.