Privacy Policy

Last updated 8 August 2026

TuxBlox sends one thing off your machine, and only when something crashes. This page says exactly what is in that report, where it goes, and how to stop it.

One feature sends data

Crash reports, and nothing else. No other part of TuxBlox talks to us.

On by default

One switch in Settings turns it off, and it takes effect immediately.

Never your account

No logins, no session data, and nothing from inside your places or plugins.

No third-party trackers

No analytics SDKs. Reports reach servers we run ourselves, and are never sold.

What a crash report contains

Crash reporting is opt-out: it is on when you install TuxBlox, and you can switch it off at any time. While it is on, and only when Player or Studio exits with a non-zero code, TuxBlox sends a single HTTPS request containing:

  • Operating system and versionDebian 12, Arch Linux 7.1.5, and so on
  • Display serverWayland or X11
  • Desktop environmentKDE Plasma, GNOME, i3, Hyprland, and so on
  • Graphics driversWhich driver and version you are running
  • TuxBlox versionsLauncher and compatibility layer build numbers
  • Which app crashedPlayer or Studio
  • Exit codeThe number the process exited with
  • TimestampWhen the crash happened
  • The tail of that run's crash logUp to the last 1 MB, sent as it was written
  • Whether it ran as rootYes or no. Root is not required to run TuxBlox.

What is never sent

  • Your Roblox account, login, or session data
  • The contents of your places, plugins, or project files
  • Any identifier that links separate reports back to you, or to each other

TuxBlox does not embed any third-party analytics or tracking SDKs. Reports go to infrastructure we run ourselves. We do not sell them or share them.

Turning it off

Settings Send Crash Report Data

Switching it off takes effect immediately: no report is generated, and none is sent. The crash log itself is still written to your own disk either way. The switch controls only whether a copy leaves your machine.

Server logs

Separately from crash reports, anything you request from our infrastructure gets logged: the website, the CDN that TuxBlox fetches launcher and compatibility layer builds from, and the crash reporting endpoint above.

Like effectively any web server, ours records each request's timestamp, IP address, user agent, request method and URL. This is retained for security purposes, such as detecting abuse and intrusion attempts, and is deleted automatically after 30 days. It is not linked to crash reports and is not used to track anyone.

Changes to this policy

If what gets collected changes, the "last updated" date at the top of this page moves, and the change is called out in that release's changelog.

Contact

Questions about this policy: [email protected].

You do not have to take our word for any of this. The launcher and compatibility layer that generate and send these reports are open source, so you can read exactly what gets collected on GitHub. The server that receives them is closed source, to make it harder to abuse.

To have data associated with your IP address deleted, email [email protected].