Flarial Launcher Privacy.

Flarial ("Flarial," "we," "us") publishes the Flarial Launcher, an Android application that injects the Flarial client into Minecraft: Bedrock Edition on your device. You can reach us via our Discord server.

The Flarial Launcher loads the Flarial client (a cosmetic and utility modification) into your locally-installed copy of Minecraft: Bedrock Edition. All injection and modification happens on your device. The launcher itself is not a game and does not provide multiplayer services.

The launcher gates access behind a Discord-authenticated beta program. When you tap "Request access":

• You complete a Discord OAuth flow. Discord returns an OAuth authorization code to the app.
• The app sends the OAuth code, your Android ANDROID_ID (a 64-bit identifier scoped to your device + signing key + user), and your phone's manufacturer and model string (e.g. "Google Pixel 8") to api.flarial.xyz/beta/request.
• The server uses the OAuth code to read your Discord user ID and roles, then issues a device token. The app stores that token locally and sends it as X-Device-Token when polling api.flarial.xyz/beta/status for approval (roughly once every five seconds while a request is pending).
• We retain your Discord user ID, ANDROID_ID, phone model, and issued device token while your beta request is active so we can authorize subsequent launches without re-prompting. You can request deletion via Discord.

The launcher displays a short interstitial advertisement on each launch, served by the third-party provider lootapp.ai. The flow is:

• The app fetches an ad URL from lootapp.ai/inapp?tid=1256848 and renders it in an in-app WebView before Minecraft loads.
• JavaScript and third-party cookies are enabled in that WebView so the ad can render and measure correctly. lootapp.ai and its partners may set cookies, read standard request data (your IP address, user-agent), and use that data to serve and measure ads.
• A close button appears after the mandatory display window.
• Data handling by lootapp.ai is governed by their own privacy policy. We do not control which sub-networks or trackers they choose to embed.

• No third-party analytics SDK. The app does not embed Firebase Analytics, Crashlytics, Google Analytics, AppsFlyer, Adjust, Sentry, or similar.
• No automatic crash upload. If the launcher crashes, a diagnostic log may be generated locally. It is not uploaded automatically — you can attach it to a Discord bug report if you choose.
• No advertising ID. The app does not read the Google Advertising ID. (lootapp.ai may set its own cookies inside its WebView; that is separate from device-level advertising IDs.)
• No contacts, location, camera, microphone, or messages. The launcher does not request those permissions.

To play Minecraft: Bedrock Edition you must be signed in to your Microsoft / Xbox Live account. That sign-in is handled by Minecraft itself once it has loaded — the Flarial Launcher does not collect your Microsoft credentials and does not see the authentication tokens Minecraft uses. Microsoft's handling of your account data is governed by the Microsoft Privacy Statement.

Once the launcher loads Flarial into Minecraft, the Flarial client itself sends limited telemetry (module enable/disable events, startup version pings, crash reports, and a VIP/online-users stream) to api.flarial.xyz. That is documented in the main privacy policy.

The following permissions are declared in the app'sAndroidManifest.xmland why each one is needed:

• INTERNET, ACCESS_NETWORK_STATE — fetch the ad payload, talk to api.flarial.xyz for beta access, and download the Flarial client and assets.
• WRITE_EXTERNAL_STORAGE — write the Flarial client files into your local Minecraft installation. Files stay on your device.
• SYSTEM_ALERT_WINDOW / OVERLAY_WINDOW — render the launch-time ad WebView as an overlay, and draw the Flarial in-game HUD on top of Minecraft.
• POST_NOTIFICATIONS — show status notifications (download progress, ready-to-play, errors).

We do not declare permissions for contacts, location, camera, microphone, SMS, or call logs.

We share data with two third parties in normal launcher operation:

• Discord — for the beta-access OAuth flow.
• lootapp.ai — for the launch-time ad.

We do not sell personal information.

The Flarial Launcher is not directed at children under 13, and we do not knowingly collect data from users under 13. The launcher also shows third-party advertisements. If you believe a child has provided us with personal information, contact us via Discord and we'll remove it.

• You can revoke any individual Android permission at any time from Settings → Apps → Flarial Launcher → Permissions. The launcher will still install but features tied to that permission will be disabled.
• You can revoke Flarial's Discord OAuth access at any time at discord.com/settings/authorized-apps.
• You can reset your Android device-scoped identifiers (including ANDROID_ID, on devices where the OS supports it) via system settings.
• Uninstalling the app removes all locally-stored launcher data, including the cached beta device token.

Questions, requests, or concerns about this policy? Reach us in the Flarial Discord (#support).

We may update this policy. Material changes will be announced on the Site or in Discord. The "last updated" date above always reflects the current version.