Privacy & telemetry

Blixt sends an anonymous boot ping to a Cloudflare Worker we operate when your server starts the resource. This page documents exactly what’s sent, why, and how to disable it.

What’s sent

Every time the resource starts, one HTTP POST is sent with this payload:

{
  "licenseHash": "a1b2c3d4",
  "resource": "blixt",
  "version": "1.0.1",
  "framework": "qbox",
  "bootedAt": 1730000000000
}

Field	What it is
licenseHash	An 8-character djb2 hash of sv_licenseKey. Not reversible to your real key.
resource	The FiveM resource folder name (always blixt unless you renamed it).
version	The Blixt version string from fxmanifest.lua.
framework	One of qbox, qbcore, esx, standalone, auto, or unknown.
bootedAt	Server-local boot time as Unix milliseconds.

That’s it. No player data, no IP addresses (beyond the standard CDN request log), no plaintext license, no script content.

What it’s used for

• Adoption metrics — how many active installs, which frameworks dominate.
• Version distribution — when can we drop a deprecated migration path.
• Field debugging — pairing a bug report from a server owner with their recent boot pings via the licenseHash they share with us.

We don’t sell or share this data.

How to disable

Add this to your server.cfg:

set blixt:telemetry "false"

Restart the resource. The boot ping is suppressed at the source — no network call is made.

How to verify

The boot-ping payload is the exact JSON shown above and nothing else. You can confirm at the network layer with tcpdump / a proxy on the FXServer host, or just set blixt:telemetry "false" and observe that no outbound call is made.

reportBoot is invoked exactly once per resource start, immediately after the framework adapter resolves. If you’d like to audit the implementation in depth, ask in the Blixt Discord.