HELM PUBLIC BETA — PRIVACY SUMMARY

Helm runs on your computer.

Beta diagnostics are OFF by default.

If you explicitly opt in to "Help us improve Helm while it's in beta", Helm may send a sanitised run receipt to Pixelhatch after a completed job. Automatic beta diagnostics are limited to:
- Helm version and operating-system/platform information;
- coding provider, model route and reasoning levels;
- provider turn and model-switch counts;
- token/usage and capacity measurements when the provider exposes them;
- forecast-versus-actual usage measurements;
- verification, counterexample, repair, regression-test and quality-gate counts.

Automatic beta diagnostics do NOT include your objective, prompts, source code, repository contents, filenames, file paths, secrets or generated code.

Helm stores a random installation ID locally when diagnostics are enabled so multiple anonymous run receipts can be grouped. It is not derived from your hardware, account, repository or identity.

After a completed run, opted-in users can optionally answer whether Helm completed the job correctly. If you type a written feedback note, that note is sent exactly as written, so do not include private project information, code, file paths or secrets.

You can turn beta diagnostics off at any time in Helm Settings and inspect the exact automatic payload Helm would send.

To perform its job, Helm may also communicate with:
- the coding-agent provider you selected;
- provider account/usage endpoints used to read live capacity;
- the public Helm model catalogue when model metadata is refreshed.

A coding provider may receive code, files, prompts or other project context needed to perform the requested work. That processing is governed by the provider account and settings you use.

Helm stores its own run state, receipts and handoff metadata locally, including `.autoroute` data inside a selected project when required for continuity.

Do not place secrets in prompts unless the coding task genuinely requires them. Review your coding provider's privacy and data controls separately.
