Privacy Policy

BeamBench does not send telemetry in the background. The desktop app only sends a diagnostic report when you choose to submit one. Project files are never included unless you explicitly turn on the project-file attachment.

Reports are retained until manually deleted on request. To request deletion, email support@beambench.com with your report ID.

When you submit a bug report from the BeamBench desktop app, the app builds a diagnostic bundle so you do not have to copy version numbers, logs, serial port details, or firmware information by hand.

The bundle may include:

• Your report title, description, optional notes, and optional reply-to email.
• BeamBench app version, build target, Git build ID, Tauri version, and Rust version.
• Operating system, OS version, CPU architecture, and locale.
• Connected laser state, active machine profile and preset, configured baud rate, controller family/model, transfer mode, firmware version, GRBL settings/quirk flags, and handshake state.
• Detected serial ports, including port names, descriptions, manufacturers, vendor IDs, product IDs, and whether BeamBench is using the port.
• Recent connection events such as port scans, open attempts, banner waits, controller-info queries, timeouts, and connection errors.
• Recent serial traffic in hex form, recent warning/error log entries, source context, optional JavaScript stack traces, and recent panic reports.
• Project metadata such as object count, file name, file size, and whether the project contains raster, vector, or text content.
• Known-issue warnings and raw GRBL handshake messages used for connection troubleshooting.
• Your IP address and app user agent as seen by the BeamBench site.

The default diagnostic report includes project metadata only, not the project geometry or artwork. If you choose to include the project file, BeamBench attaches the current .lzrproj file so the issue can be reproduced. This checkbox is off by default.

Before a diagnostic report is saved or sent, BeamBench scrubs common home directory paths such as /Users/name/, /home/name/, and C:\Users\name\, replacing the username portion with <userhome>. The same pass is applied to logs and panic messages.

The desktop app may keep local panic files and local feedback history on your computer so a later report can include useful context. This local data is not transmitted to BeamBench unless you choose to submit or save a report.

If you email BeamBench, we receive the information you provide and the normal delivery metadata needed to respond. The public website may also receive standard web server logs such as IP address, request path, user agent, and timestamp for security and operations.

The BeamBench website uses Google Analytics to count which pages get visited, so we can tell which docs and features actually help people. No analytics script loads and no analytics cookie is set unless you choose Accept on the cookie banner. If you decline, the site works exactly the same.

If you accept, Google Analytics sets first-party cookies (named _ga and _ga_…) to tell returning visits apart. We use this for traffic measurement only, not advertising or cross-site tracking. Google processes this data on BeamBench's behalf; see Google's privacy policy.

You can change your mind at any time. Declining stops analytics from loading and removes BeamBench's analytics cookies; you can also clear cookies in your browser.

Cookie settings

You can ask for a copy of the data BeamBench holds about you, ask for it to be corrected, or ask for it to be deleted. Email support@beambench.com. For bug reports, include the report ID shown in the app so the record can be found quickly. Requests are handled at that mailbox regardless of where you live.

BeamBench uses a small number of outside services to run the site and respond to you:

• A hosting provider runs the web server and keeps standard server logs.
• Mailgun delivers the email BeamBench sends (such as report notifications).
• GitHub hosts the private bug-triage mirror described above.
• Google provides website analytics, only after you accept the cookie banner.

Diagnostic reports are stored on BeamBench-controlled infrastructure. We do not sell diagnostic reports, share them with advertising networks, or use them for unrelated tracking. Reports are used to debug BeamBench, improve compatibility, and respond to support requests.

When a report is accepted, BeamBench sends a notification email to the support mailbox with the report ID, kind, title, description, notes, optional reply-to email, app version, operating system, and whether a project file was attached. Raw diagnostic logs, serial traffic, panic backtraces, and project files are not included in that notification email.

Report metadata and scrubbed diagnostic contents, including your title, description, optional notes, and optional reply-to email, may also be mirrored into a private GitHub repository controlled by BeamBench for triage. GitHub acts as a processor for that private mirror. Attached project files remain in BeamBench's database only and are never copied into GitHub issues.

To delete a report, email support@beambench.com with the report ID shown by the app after submission. Deletion removes the report row and any attached project file associated with that report.

For privacy questions, support requests, or deletion requests, email support@beambench.com. For security vulnerabilities, email security@beambench.com.