Nothing to sign up for.
Nothing collected.

Last updated 2026-11-13

What the apps send, and where

• Games you open. The apps download a game from the address you give them: a threert dev server on your own network, threert.dev, or a link you open. That server sees the request, as any web server does.
• Logs back to your dev server. A game opened from a threert dev server sends its console output back to that server, so it shows in your terminal. Nothing else receives it.
• The store. ThreeRT for macOS, for Steam Deck and for Android read the list of apps and games and their pictures from threert.app (versions before 0.4.0: from threert.dev). Playing one from there tells threert.app that it was played, with a random number the app made up on this device, so one device counts once a day. The number says nothing about you and is kept two days.
• Multiplayer rooms. A game that plays in a room connects to it on threert.app and sends what the game needs: the name you chose, a random player number kept on this device, and your moves. A room keeps them while it is open and no longer.
• Updates. ThreeRT for macOS, for Steam Deck and for Android ask threert.dev which version is current. The request carries nothing about you.
• Sharing a Mac's GPU (ThreeRT for macOS, only when you turn it on): the frames and input go through the relay you set in Settings, by default one on your own machine.

Playing needs no account. There is no advertising identifier, no crash or usage reporting, and no third-party SDK in any of the apps.

threert.app

Browsing and playing on threert.app need no account. Publishing does: you sign in with GitHub, and threert.app keeps your GitHub user number, login, display name and avatar address. It does not ask GitHub for your e-mail address or for access to your repositories.

• What you publish (an app's files, its name, description and pictures) is public, with your GitHub login as its author. Deleting an app takes it down.
• Sign-ins. A session is one cookie on threert.app in a browser, or a token kept in your home folder by the threert command and ThreeRT for macOS. threert.app keeps only a hash of it, with what asked for it (for example "cli 0.4.0 macOS").
• Likes are kept with your account. Reports are kept with their text, and with your account if you were signed in.
• threert.app is served by Cloudflare, which processes requests to deliver it and counts page views for the site's owner without cookies (Cloudflare Web Analytics).

What stays on your device

• The games you opened recently, and downloaded game files kept as a cache.
• ThreeRT for macOS: your settings and Studio projects, in your home folder.

Camera and local network (iPhone and iPad)

The camera is used only to read the QR code a threert dev server or ThreeRT for Mac shows; the picture is not stored or sent anywhere. Local network access is used only to load games from dev servers on your network. You can turn either off in iOS Settings.

This site

threert.dev is served by Cloudflare, which processes requests to deliver the pages and downloads. The site sets no cookies and runs no analytics.

Your browser makes three kinds of request to other services when it shows these pages, and each of them sees the request as any web server does: the typefaces come from Google Fonts; the Star buttons ask GitHub’s public API for the repository’s star count; and the front page asks threert.app for the list of published apps. The star count is kept in your browser’s local storage for a few hours, so it is not asked for on every page. Nothing else is stored.

TestFlight

If you test ThreeRT for iPhone through TestFlight, Apple shares the information described in Apple's privacy policy for TestFlight (such as crash reports and feedback you choose to send) with the developer.

Questions

Open an issue on github.com/meshy-dev/ThreeRT.