Privacy

Short version: the website runs no analytics, sets no cookies and embeds no third-party code; the installer does not phone home. The long version is below, with every data touchpoint spelled out so you can audit it.

This website (openbox.huize.org)

• What's here — static HTML + one CSS file. No JavaScript on the critical path.
• Hosted on Cloudflare Pages. Cloudflare retains edge access logs under their standard retention policy for operational / abuse-response purposes. We do not export or mirror those logs and do not run Cloudflare Web Analytics.
• Does not set any cookies; does not embed third-party fonts, frames, pixels, trackers, A/B tools or analytics.
• Sends no request to any domain outside openbox.huize.org during a normal page view.
• Subresource Integrity is not needed because no third-party resources are loaded.

The software (OpenHuizeBox installer + GUI + CLI)

• Does not phone home. The installer does not register with any backend, submits no hardware IDs, and does not check for updates automatically.
• Release checking is off by default. If you enable it, it fetches a single static JSON file from openbox.huize.org over HTTPS and sends no payload beyond a standard User-Agent string and your IP address.
• Crash reporting is disabled by default. If you opt in, anonymised crash dumps are attached to a GitHub issue by you, manually — we do not operate an automated crash-ingestion service.
• Telemetry: none.

Data you control

VM disk images (.vdi), captured network traces (.pcapng, .etl), generated TLS root certificates, applied identity profiles and build artefacts all live under your Windows user profile and are never transmitted by the software. Deleting the installation folder and the %USERPROFILE%\VirtualBox VMs directory removes everything.

Third-party services we point at (but don't inline)

We link out to: GitHub (for source, releases, issues, security advisories). Each of those services has its own privacy policy that applies when you follow a link. We do not forward any data to them on your behalf.

Changes to this policy

Changes to the substance of this page are committed with [PRIVACY] as a commit-subject prefix in the site repository so a diff is traceable. The revision history is publicly auditable.

Contact

Privacy questions: [email protected]. Reports of this policy being violated: same address, [PRIVACY-INCIDENT] subject prefix.