Privacy Policy

Last updated 16 October 2026

We do not track you and we do not sell your data.

On startup TuxBlox checks our server for updates, and that is the only thing it sends on its own. Three further features can send something off your machine, and all three are off until you turn them on. This page covers each of them, who gets what, which parts of TuxBlox we host, and what the Roblox client itself can see.

Only an update check

On startup TuxBlox checks whether it is up to date. Nothing else is sent to us until you turn a feature on.

The website is not ours

GitHub Pages serves it, behind Cloudflare. Only the releases page reaches a server of ours.

Never your login

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

No trackers, anywhere

No analytics, no third-party assets, nothing sold or shared. Not on any page here.

What leaves your machine

The update check below happens every time TuxBlox starts and no setting controls it, so it comes first. Everything after it is a feature that is off on a fresh install, and a switch that is off sends nothing at all.

The update check every launch

Every time TuxBlox starts, it asks setup.tuxblox.net two things: which version your release channel currently serves, and that version's file list, which carries each file's size and checksum. The second is how TuxBlox tells whether the copy on your disk still matches the release it claims to be, so it is fetched whether an update is needed or not. That list is held in memory and never written to your disk.

No setting turns this off. It is how TuxBlox knows it is out of date, and it is the same request whatever else you have chosen. What our server records about it is covered under Logs.

If an update then gets installed, because Auto-Update is on or because you asked for one, TuxBlox makes further requests to the same server to download the new files. Those are TuxBlox's own files and nothing else.

Roblox itself never comes from us. TuxBlox always downloads the Roblox client, and checks which Roblox version is current, from Roblox's own servers. Those requests go to Roblox under Roblox's own policies, and none of it passes through our infrastructure.

Crash reports off by default

When Roblox stops with an error, TuxBlox can send us one report about it. With the setting off, nothing is sent on its own. The error window gets a Report button instead, and a report goes only if you press it, only for that one crash. Turning the setting on sends every crash without asking. A report contains:

  • 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 codesWhat TuxBlox and Roblox each exited with
  • TimestampWhen the crash happened
  • The tail of that session's logUp to the last 1 MB, sent as it was written. Roblox writes its own log into the end of the same file, so that part comes too.
  • Whether it ran as administratorYes or no. TuxBlox refuses to run with administrator rights unless you deliberately force it.

Reports go to telemetry.tuxblox.net, a server we run, and are deleted after 90 days. The log gets written to your own disk either way. The switch only decides whether a copy of it leaves your machine.

Roblox writes its own log into the end of that same file, and it goes to our telemetry server along with ours. Roblox's part of it can name things we never ask for, including:

  • Place namesWhat you had open, or were playing, at the time
  • The server addressThe Roblox server you were connected to
  • Your Roblox user IDThe number your account is identified by
  • Other people joiningAnybody with edit access who joined a place you were in

TuxBlox does not collect, request or separate out any of that. It is in the file because Roblox wrote it there, and that log is usually the only thing that explains a crash. This is why the setting starts off, and why sending a report is left up to you.

TuxBlox developers can read the reports that arrive, since that is what makes a crash fixable. The address a report came from is not shown alongside it, and only the server knows which report belongs to which address.

That does not make a report anonymous. Roblox's part of the log can carry your Roblox user ID, as above, and anybody reading it can look that up. A report identifies you as much as the log inside it does. It is the other reason sending one is left up to you.

Discord Rich Presence off by default

This shows what you are playing or editing on your Discord profile: the experience's name, who made it, its icon, how long you have been in it, and buttons to open its page.

None of this is sent to us. TuxBlox hands it to the Discord app already running on your own machine, over a connection that never leaves your computer. Discord publishes it from there, under Discord's own policies. With Discord closed, nothing happens at all.

To name what you are in, the launcher asks Roblox's own public services for the experience's name, creator and icon. Those requests go to Roblox, not to us.

Anyone who can see your Discord profile can see the result. That is the point of the feature, but it is worth saying out loud. Two switches sit under it:

  • Let people join your serverOn by default. Adds a join button, which puts the server you are in on your profile. Off keeps the rest of the presence without it.
  • Let games use the Rich Presence APIOn by default. Lets an experience set its own status text, such as which area you are in. Off means nothing an experience sends is read at all, and your profile shows only what TuxBlox worked out itself.

Server location off by default

This shows a notification naming the region of the Roblox server you just joined. What gets looked up is the Roblox server's address, not yours. The lookup goes to geo.tuxblox.net, which answers from a database held on that same server, so the address is not passed on to anybody else.

A test on your own machine is not a server, so local and private addresses are never looked up. Each server is asked about once per session.

Looking up a Roblox server is not recorded beyond the ordinary request log. A lookup for anything that is not a Roblox server is counted against where it came from, so the service cannot be used as a general address lookup tool, and that count lasts 24 hours. See Logs.

Where each part is hosted

TuxBlox is not all in one place, and the difference decides who can see what.

  • tuxblox.net
    (this site and the docs)    GitHub Pages, behind Cloudflare. Not our infrastructure.
  • setup.tuxblox.netOur own server, with neither GitHub nor Cloudflare involved. Update checks, TuxBlox's own downloads, and the releases page's version list.
  • geo.tuxblox.netOur own server, behind Cloudflare. Server location lookups.
  • telemetry.tuxblox.netOur own server, behind Cloudflare. Crash reports.

GitHub Pages and Cloudflare serve this website between them, so for almost every page we receive nothing at all about your visit. No logs, no analytics, no way for us to know you were here. GitHub and Cloudflare handle those requests and keep whatever their own policies say they keep.

The releases page is the exception. To list what is published, it asks setup.tuxblox.net for the metadata of every available version, and your browser makes that request itself. Opening that page therefore does reach a server of ours, and it is logged the same as any other request to it. That server sits behind neither GitHub nor Cloudflare.

The three subdomains above are servers we run. Requests to them reach us. Cloudflare sits in front of geo and telemetry, so it handles those two as well.

What Roblox can see

TuxBlox runs the real Roblox client. The client asks your computer the same questions it would ask a Windows machine, and TuxBlox answers them: your machine's make and model, your processor, your graphics card, your network adapter's address, and identifiers such as the machine's serial numbers and UUID. Roblox's anti-tamper reads these, the same as it does on Windows.

The network adapter's address is always the permanent one. If you randomise or change your MAC address, Roblox is still shown the address the adapter was built with rather than the one in use. TuxBlox asks the adapter itself for that value, because it is what a Windows machine reports and it does not change.

Some of those values cannot be read on Linux without administrator rights, which TuxBlox never asks for. Rather than report nothing at all, TuxBlox works out a stand-in from your hardware that stays the same for that machine.

These answers go to the Roblox client, not to us. TuxBlox does not collect, store, log or send any of them, and none of it is part of a crash report.

What the Roblox client then sends to Roblox, and what Roblox does with it, is between you and Roblox, under Roblox's own policies. We cannot see it and we cannot change it. TuxBlox is not affiliated with, endorsed by, or associated with Roblox Corporation, and playing through TuxBlox does not change the policies and rules that apply to your Roblox account. Enforcement of those rules is Roblox's decision alone.

Roblox itself is never downloaded from us. The launcher always fetches the Roblox client, and checks which Roblox version is current, from Roblox's own servers, so those requests go to Roblox and Roblox's own policies cover them. Only TuxBlox's own files come from setup.tuxblox.net.

What is never sent

  • Your Roblox password, login, or session data
  • The contents of your places, plugins, or project files
  • Any other file from your virtual drive. Only that session's log travels, and only in a report you sent
  • Any identifier of our own. TuxBlox adds no account, device or install ID to a report, and does not tie reports together

TuxBlox embeds no third-party analytics or tracking SDKs, and neither does this website. Its assets are served from this domain rather than somebody else's, so loading a page here reaches nobody but this site. Reports go to servers we run. We do not sell them and we do not share them.

Turning it all off

All three switches live together in the launcher, under Settings → Privacy:

Always send crash reports
Enable Discord Rich Presence
Notify server location

Each one takes effect straight away, and each one is off until you turn it on. If you have never opened that page, none of the three has ever sent anything. The update check is the one thing that happens either way.

Logs and how long we keep them

Every connection to a tuxblox.net subdomain is logged, whichever one it is and whether TuxBlox or your browser made it. This website is the exception, because it runs on GitHub Pages behind Cloudflare and those requests never reach us at all. The one part of it that does is the releases page asking for the version list, which is logged like anything else.

For everything else, each request is recorded with:

  • IP addressThe address the request came from
  • User agentWhat the request said it was, such as the launcher or a web browser
  • HeadersThe rest of what the request sent along with it
  • URL and request typeWhat was asked for, and how it was asked for
  • HTTP code and responseWhat our server answered
  • Which server answeredThe machine of ours that handled it
  • Time of the requestWhen it reached us

We keep this to spot abuse and intrusion attempts, and it is deleted automatically after 30 days. The logs stay on our own servers and cannot be reached from outside them. They are not linked to crash reports and they are not used to track anyone.

Crash reports themselves are deleted after 90 days.

geo.tuxblox.net keeps one extra record. Everything above applies to it, and on top of that a lookup for an address that is not a Roblox server is stored against the address it came from. That exists to rate limit those lookups, so the service cannot be used as a general address lookup tool. Ordinary use never reaches it: asking about the Roblox server you joined is not recorded there at all. What does get recorded is held apart from the ordinary logs and is deleted automatically after 24 hours.

Cloudflare sits in front of geo.tuxblox.net and telemetry.tuxblox.net, so it handles those requests too and keeps its own records under its own retention policy. The same applies to this website, where GitHub and Cloudflare are the ones who see your visits rather than us.

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: contact@tuxblox.net.

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 contact@tuxblox.net.