Skip to content
Hbench
hbench

Reference

Privacy and redaction

What stays private on Your bench, what publishing a run makes public, how to make its trajectories public, what the site keeps when you delete a job, how hbench and the site redact keys, and how to keep your model key safe.

A job stays private until you publish it. Before anything is stored, hbench and the site replace key-like values with [REDACTED]. The privacy notice lists everything we keep, for how long, and who sees it.

What stays private

Only you can see a job on Your bench, with its trajectories, logs and files. Maintainers can open it when they handle an abuse report or a support request, and the site records every such access. Limits says how long Your bench shows each kind of file. The site never publishes logs or files, even for a run on a board, and publishes a run's trajectories only when you make them public.

What a board makes public

Every job you upload stays private until you publish it, including a run you issued. Publishing puts the run on its board and makes these public:

  • your entry name;

  • the run's score, agent, model, trial and error counts, and date;

  • its agent configuration: the agent, the version that ran, the commit of an agent from a git repository, and the agent's options. An option value that is an object, a URL or text over 40 characters shows only as a short digest, so a private model server's address stays private;

  • from 24 October 2026, each task's result: its name, its reward and any error, the agent's time, and the tokens and cost it used.

The board doesn't name you. Your GitHub handle, and any hardware you reported when you issued the run, are public only in the site's API, with each run you publish. Your profile page, if you turn it on, also shows your handle.

Each task's result shows when someone compares two configurations on a board's Compare tab, and through GET /api/compare. A run published before 24 October 2026 shows each task's result only if its owner agrees; until then, a comparison that includes it shows only its totals. Logs and files, your contact email, any job you didn't publish and any trajectories you haven't made public stay private.

Make trajectories public

A trajectory records what the agent did and saw in a trial. Publishing a run leaves its trajectories private. To share them, select Make trajectories public on the run's page or on its job in Your bench, within 30 days of the upload.

Before a trajectory goes public, the site replaces your saved keys and values in common key formats with [REDACTED] again, then scans it with gitleaks' secret-detection rules and for nodeq.tech's own API and run tokens. A trial with a finding stays private, as does a trajectory over 32 MiB or one the scan doesn't finish in 60 seconds. The run's page says how many trials stayed private, and which rules matched.

Anyone can read the other trials' trajectories on the run's page while its score is on its board. These public copies don't expire with the job's files, and nothing deletes them. A withdrawal or a take-down hides them; if the score is put back, they show again without a new scan. Hide trajectories hides them until you make them public again, which scans every trial again.

How keys are redacted

hbench redacts on your machine first. When a trial ends, it looks at every variable it read whose name contains KEY, TOKEN, SECRET, PASSWORD, CREDENTIAL or AUTH, and replaces its value with [REDACTED] in every file of the trial's folder. It does the same to the job's folder when the job ends. Values shorter than 8 characters are left alone. In config.json it records such a variable as a reference, such as ${DEEPSEEK_API_KEY}, or masked.

The site then scans every uploaded file before it stores anything, and replaces:

  • values in common key formats, from Anthropic, OpenAI, DeepSeek, Google, GitHub, Hugging Face, Slack and AWS;

  • any key you saved on the site before it stopped taking keys.

The upload message and the job's page say how many values were replaced. Redaction misses a key in another format that hbench never read, such as one the agent found in a file, and a key the agent changed, such as one cut in two.

Keep your model key safe

The site takes no model keys. hbench passes your key from your shell to the agent in the task container, so the key leaves your machine only for your provider. An agent that prints its environment writes the key into its trajectory, where hbench replaces it when the trial ends.

  • Use a separate key for benchmarks, with a spending limit.

  • Export it from a file, so it stays out of your shell history: export DEEPSEEK_API_KEY="$(cat ~/.deepseek-key)".

  • If a key leaks, revoke it with your provider.

Have data removed

Delete a job to take its results, trajectories, logs and files off Your bench at once. Nothing is deleted automatically: the site keeps the job's record, hidden, Limits says when its files leave storage, and backups keep a copy until a maintainer removes it by hand. Deleting a job doesn't take its run off its board, so withdraw the score first.

When you delete a job you published, or uploaded with its run token, the site keeps its hbench job id and each trial's task, start time, finish time and token counts, so the job can't be published twice (A job that had a score).

To remove a score whose job is gone, report it. To remove anything else, such as your entries, email hello@nodeq.tech.

Reviewed on October 30, 2026.