Privacy
RDMBench keeps everything on the bench computer. The only requests it makes, what they carry, and how to turn them off.
RDMBench is local. Reports, monitoring sessions and repair notes are files on the bench computer, and the app works fully offline. It has no analytics, no telemetry and no crash reporting.
What it sends, and when
| Request | When | What it carries | Turn it off |
|---|---|---|---|
App updates: updates.rdmbench.com/appcast.xml | Once a day | Nothing about your fixtures | Settings → General → Updates |
Fixture library: a manifest on raw.githubusercontent.com | When you connect | Nothing about your fixtures | Settings → General, or the Connect sheet |
GDTF Share: gdtf-share.com | Only if you sign in with your own account | Your sign-in, and the fixture you look up | Don’t sign in |
- An update is downloaded only when you accept it.
- Changed library tables are downloaded only when you click Update in the banner that offers them.
- The GDTF Share password is kept in the macOS Keychain. There is no shared account and no RDMBench server in between.
- Propose… and Contribute Fixture Profile… open a prefilled pull request in your browser, for you to read and send yourself.
AI assistants
Connecting an assistant sends nothing anywhere. The MCP server runs on the bench computer and talks to the app over a loopback address. What the assistant reads then goes to its provider as part of your conversation (Assistants).
Where your data is
Everything is under ~/Library/Application Support/RDMBench:
captures/: the reports and monitoring sessions, one folder per unit; simulator runs incaptures/simulator/;manufacturer-pids/: library tables you have downloaded;gdtf/: GDTF files you have added.
This website
No cookies, no scripts, and nothing loaded from another site. The fonts are served from here. Cloudflare serves the site and sees each request, as any host does; there is no analytics script.