Flarial
Last updated · May 17, 2026

Privacy Policy.

Plain-English summary of what we collect, why, and what your choices are. Covers flarial.xyz, the Flarial desktop launcher, and the Flarial client for Minecraft: Bedrock Edition. For the Android launcher, see the Android launcher privacy policy.

Who we are

Flarial ("Flarial," "we," "us") operates flarial.xyz (the "Site"), the Flarial desktop launcher, and the Flarial client for Minecraft: Bedrock Edition. You can reach us via our Discord server.

What the website collects

  • Usage data: pages viewed, referring URL, approximate region, browser and device type. Collected via standard analytics and server logs.
  • Local storage: cosmetic preferences (favorite modules). Stored in your browser only — never sent to us.
  • Discord widget: the homepage reads the public Discord widget for the "online now" count. No personal data is exchanged.

What the desktop launcher collects

The Flarial desktop launcher (Windows, downloaded from flarial.xyz/download) sends the following to our servers:

  • Launch events: a per-install identifier (derived from your Windows machine GUID), launcher version, and timestamp. Posted to api.flarial.xyz/launcher/events/launch on each launch. Used to count daily active installs.
  • Update checks: the launcher fetches the latest version string from cdn.flarial.xyz/launcher/launcherVersion.txt. The request carries only standard web headers (IP, user-agent).
  • Local settings: your launcher preferences are stored on your device. They are not synced to our servers.

What the Minecraft client collects

The Flarial client (the DLL injected into Minecraft: Bedrock Edition) sends the following to our servers:

  • Module events: when you enable or disable a module (e.g. Keystrokes, FOV Changer), we record the module name and action against a hashed user identifier. Posted to api.flarial.xyz/telemetry/module-events. Used to see which features are actually used.
  • Startup ping: on client launch we send your hashed user identifier and client version to api.flarial.xyz/telemetry/version-startup.
  • Crash reports: if the client crashes, we send a diagnostic report to api.flarial.xyz/api/v1/crash-logs. The report includes stack trace, hashed in-game username, client version, hardware summary (CPU/GPU model, RAM, disk, OS version, DirectX version), which modules were enabled, the last ~50 KB of the client log, and a short history of recent in-game actions from the current session. Crash reports are retained for 30 days and may be relayed to a private Discord channel for staff triage.
  • VIP / online users stream: the client opens a WebSocket to wss://api.flarial.xyz/ws/vips and periodically fetches /vips and /allOnlineUsers so VIP and creator badges show up in-game. This carries public Minecraft usernames.
  • Hashed user identifier: derived from your computer name, Windows machine GUID, CPU model, and core count, hashed with SHA-256 before transmission. It is stable across sessions on the same device but we do not store the raw inputs.

What the client does not collect: your Microsoft password, Mojang/Xbox tokens, IP address (beyond what any web request includes), MAC address, location, camera, microphone, keystrokes outside of in-game keybinds, game world data, or payment information.

What the backend stores about Minecraft players

To power leaderboards, the public "online players" widget, and community features, our backend keeps a record per Minecraft username it has seen: total playtime, first-seen timestamp, last heartbeat, and ranking position. Inactive players are pruned 30 days after their last heartbeat. Aggregate session data (country and region derived from IP, user-agent, session length) is used for analytics — we don't publish individual session rows.

What our Discord bot stores

If you interact with the Flarial Discord server, our bot may store your Discord user ID and username, XP/reputation, warnings issued by moderators, claimed Minecraft IGN (if you link one), ticket history, booster status, and starboard / reaction-role records. This data is kept for as long as you remain a member; you can request deletion via Discord.

Ads (Google AdSense)

The /download page may serve ads via Google AdSense. AdSense is a third-party provider that uses cookies and similar technologies to serve ads based on your prior visits.

  • Google may use the DoubleClick cookie to serve ads based on your visit to this site and other sites on the internet.
  • You can opt out of personalized advertising at google.com/settings/ads or via the Digital Advertising Alliance opt-out.
  • Where Google requires it (e.g. for visitors in regions covered by its consent framework), AdSense itself shows a consent prompt before setting personalized-ad cookies.

More info: Google's advertising policies. The desktop launcher and Minecraft client do not show ads.

How we use it

  • Operate, secure, and improve the Site, launcher, and client.
  • Diagnose crashes and measure which features are actually used.
  • Power leaderboards and community features (VIP badges, online counts).
  • Comply with legal obligations.

We don't sell personal information.

Cookies

We use a small number of cookies for analytics and, on /download, for ads via Google AdSense. You can clear or disable cookies in your browser settings — Site functionality will continue to work.

Children

Flarial is intended for users 13 and older. We don't knowingly collect data from younger users. If you believe a child has provided us with personal information, contact us via Discord and we'll remove it.

Changes

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.