privacy policy

last updated: 2026-08-20

public benchmark data

A normal run automatically submits a completed result. The service stores allowlisted CPU/GPU names, approximate memory, OS and architecture, system model, core counts, GPU driver, backend and execution plan, benchmark profile, software/model identities, raw timing samples, calculated scores, stability, phase timings, and optional hardware-temperature observations so the result can be validated.

The public leaderboard API exposes the hardware description, calculated score and workload summaries, stability, phase timings, and temperature start/maximum/end summaries. It does not expose raw timing arrays, per-second temperature samples, the private machine ID, or the cross-device owner ID.

A random private machine ID is created by normiebench. It is not a vendor serial number or hardware identifier. The Worker converts it, together with the hardware description already published on the leaderboard, into a non-reversible public ID using a server-side keyed HMAC. The private ID never leaves your machine in published form and cannot be recovered from the public one. Up to ten accepted runs per machine and profile are retained publicly.

private diagnostics

Unless local-only mode is selected, a fatal native-runner error automatically submits the runner version, OS/architecture, CPU/GPU names, failure stage, and sanitized error text. Home-directory paths are redacted before submission. Diagnostics are stored separately from public results, are not displayed on the leaderboard, and are automatically deleted after 90 days.

who your machine connects to

A run contacts more than normiebench. The bootstrap and the runner download from normiebench.com; engine packages come from github.com release assets, and for Intel macOS from gitlab.com; the model files come from huggingface.co. Those hosts see your IP address, the requested file, and a normiebench/<version> user agent, and they apply their own privacy policies, which normiebench does not control. These downloads are cached, so later runs normally contact only the submission endpoint.

IP addresses and infrastructure

normiebench does not write IP addresses to its application database. Cloudflare necessarily processes connection metadata and the Worker uses the connecting address transiently for abuse rate limiting. Cloudflare may retain its own platform logs under the Cloudflare privacy policy.

The website is hosted on Cloudflare Pages, results are processed by a Cloudflare Worker, and results are stored in Cloudflare D1. Source code and release CI are hosted on GitLab. The website does not load third-party fonts or analytics.

local-only mode

Set NORMIEBENCH_NO_SUBMIT=1 before running to disable both result and diagnostic submission. Benchmarking still works and the full JSON result remains in the per-user normiebench cache. Network or submission failure never deletes the local result.

removal

To request removal, open a confidential issue in the GitLab project and include the private machine ID stored beside last-result.json. Never post the private ID publicly.

contact

Questions and removal requests can be filed at gitlab.com/brando69/normiebench/-/issues.