Beta builds carry features that have not reached a stable release yet, so you can try them against your own estate first. They are signed and SBOM'd exactly as stable builds are — beta means early, not unchecked. In exchange, a beta binary reports diagnostics back to Vrtmv on every run: engine version, which command ran, whether it succeeded, the source and target OS, timings and counts, and — on a failure — an error message with paths, hostnames, IPs and email addresses stripped out. It never sends image contents, configuration, accounts, keys or your package list. That reporting is the condition of the channel; there is no way to take the builds without it.

Enrolling covers the whole account, so it takes two steps: any user reads the terms and requests access, then an account admin accepts the same terms on the account's behalf. Full field list and retention: the beta channel reference.