Privacy
Last updated 11 November 2026
In short
- The model files you open stay on your computer. They're never uploaded.
- When you sign in, Fitbench knows your email address. Signed in to the web app, your settings and saved bodies and measurements sync automatically; the Windows app syncs them once you sign in to it (Account → Sign in).
- Crash reports and feedback are only sent with your OK (or if you chose "Always send" for crash reports), and this page lists what's in them.
- While Fitbench is being tested, it sends its developers usage statistics: how long it's used, which tools, errors and how fast it runs. Never your files, projects, measurements or anything you type. You can turn this off in Preferences (the menu under your picture, top right).
- There are no ads, no advertising or third-party trackers, and no selling of your data.
- You can delete your synced data at any time.
Who runs Fitbench
Fitbench is made by Ryan Greene, who is responsible for the data described here. For any question about your data, or to ask for a copy or its removal, email [email protected].
What stays on your device
- Models and projects. In the browser, files you open are read on your own computer and never sent anywhere. Saving or exporting downloads a file to you. The Windows app works with files on your PC.
- Settings. Kept in your browser's storage (web) or a settings file in your Windows user folder. While you're signed in, a copy is synced too (see below).
Signing in
Sign-in is handled by Cloudflare Access, on Cloudflare's servers. You can sign in with Google, Microsoft or a one-time code sent to your email. Fitbench receives your email address (and, from Google or Microsoft, the name on the account and, if the sign-in shares it, your profile picture), so it knows which data is yours and can show who's signed in. It doesn't receive your password. Cloudflare keeps a sign-in cookie in your browser so you stay signed in. See Cloudflare's privacy policy.
Synced settings, bodies and measurements
While you're signed in, Fitbench keeps these on its server so they follow you between the web app and the Windows app. The web app syncs them automatically; the Windows app does once you sign in to it:
- your preferences (units, theme, printer and the like)
- your profile picture: the one from your sign-in, or one you choose in Account → My profile (kept as a small copy; you can switch back or show initials instead)
- bodies you save and their measurements, which can include body measurements you entered or that Fitbench took from a scan or photos
They're stored in a database on Cloudflare, linked to your email address. Only you can read them. Body measurements are personal information, so they're used only to show your bodies back to you. They're never shared, sold or used for anything else. In the app, Account → Delete my synced data removes all of it from the server straight away and signs the Windows app out on every PC. The only thing kept is a one-way hash of your email address and the time you deleted it, so a copy still open in another browser isn't uploaded again; the hash can't be turned back into your address. What's on your own devices stays there.
Crash reports and feedback
If Fitbench stops because of an error, it asks whether to send a report, unless you chose "Always send" or "Never". Help → Send feedback sends what you write: something that's wrong, an idea or a question. A crash report, or feedback that something's wrong, contains:
- Fitbench's version, your Windows version or browser, and your graphics card
- the error and where in Fitbench it happened, plus Fitbench's own recent log lines, with your user name and folders removed from file paths
- for feedback, what you wrote, and your email only if you chose to give it for a reply
An idea or a question carries only what you wrote, Fitbench's version, and your email if you gave it.
Reports are stored as issues in a private GitHub repository that only Fitbench's developers can see. See GitHub's privacy statement.
Usage statistics
To learn how Fitbench is used and where it goes wrong while it's being tested, the web app and the Windows app send a small, fixed set of events to Fitbench's own server (not to an analytics company). They're on unless you turn them off, and the first time you open Fitbench a note says so. What's sent:
- when a session starts and ends, and how much of it was active or idle
- which tools and actions are used, from a fixed list (Attach, Snap edges, Split, joints, hardware, fitting to the body, the build guide, each kind of export, and so on), and which one was undone straight after it ran
- how far you got the first time: opened Fitbench, opened a model, first attach, saved a project, exported
- errors shown, as a short code (for example "could_not_save"), not the message's text
- imports that failed, as the file type only (for example "stl")
- whether your browser lacks WebGPU, and whether Fitbench crashed
- how fast it runs: how long a model took to load, how many triangles and parts the project has, how long frames take to draw, and how much memory the models use
With each one goes: web or Windows, Fitbench's build, your Windows version or browser, your graphics card, a random number made for this install of Fitbench (or this browser), and, when you're signed in, a one-way hash of your email address. Fitbench's owner can match that hash to the testers' accounts, so during testing these statistics are linked to you when you're signed in.
Never sent: file names, project names, model contents, body measurements, notes, or anything you type. The app and the server both check every event against a fixed list of what's allowed and refuse anything else.
Usage statistics are kept for 90 days and then deleted. Only Fitbench's owner can see them. To stop them, turn off Preferences → Privacy → Share usage statistics: then nothing is recorded or sent, and anything not yet sent is deleted from your device.
Who processes your data
- Cloudflare: hosting, sign-in, and the database for synced data and usage statistics
- GitHub: crash reports and feedback
- Google or Microsoft: only if you choose to sign in with them
These services may store data outside your country. They're required to protect it under their own policies linked above.
How long it's kept
- Synced data: until you delete it, or until your account is removed.
- Reports: until the problem they describe is resolved, and then for up to a year.
- Usage statistics: 90 days.
Your choices
- Use Fitbench without syncing: in the web app, Account → Sign out stops syncing in that browser; in the Windows app, don't sign in (or sign out). Your settings and bodies then stay on your device.
- Turn crash reports to "Never" in the app's settings.
- Turn off Preferences → Privacy → Share usage statistics, in each app and browser you use.
- Ask for a copy of your data, a correction, or its removal, by emailing the address above. We'll answer within 30 days.
- If you're unhappy with how your data is handled, you can complain to your local privacy regulator, for example the Office of the Australian Information Commissioner in Australia, or your national data protection authority in the EU or UK.
Children
Fitbench isn't meant for children under 13, and we don't knowingly keep their data.
Changes
If this policy changes in a way that matters, Fitbench will say so in What's new, and the date at the top will change.