Skip to content

Privacy

Orivoxx is a read-only benchmark site with no accounts, no analytics, and no cookies. This page states what a stored result contains and what it never contains.

What is stored

  • A bounded scorecard: overall score, three bench scores, requirement outcomes, cap reasons, structural metrics.
  • Run metadata: status, exit code, duration, adapter identity, and model identity.
  • Version fields: task, ruleset, scoring configuration, adapter, and a repository fingerprint.
  • The produced-code diff as bounded text: 256 KiB, 200 files, 400 lines per file.
  • Redacted trace summaries: model timing, tokens, cost, tool names, paths, byte counts, and status/error class.
  • Attribution and proof: layer × mode, evidence step indices, intervention, and the baseline/counterfactual scores.

What is never stored

  • Full source trees, archives, or ZIP contents.
  • Agent prompts, raw model responses, or provider request bodies.
  • Provider API keys, store tokens, or secret candidates.
  • Raw tool arguments/results, file contents, prompts, or the replay action log.

Replay actions are held in harness memory for the organizer run, used to compute the counterfactual, and deleted. They are never written to the result store.

Captured workspaces exclude .env files, keys, certificates, credentials, .git, node_modules, build output, binaries, and large generated content.

Where it lives and how long

Results are appended to a shared Upstash Redis store in deployment, or to a local append-only directory for organizer runs. Results are retained for 90 days. The store is append-only; a re-run produces a new row. The public site has no write or delete endpoint.

Model provider

The score path makes no model calls. Real adapter runs are organizer-executed and send the task specification and source context to OpenRouter through its OpenAI-compatible API. Provider-side processing and retention are governed by the provider's terms. Orivoxx does not claim provider-side zero retention.

Tracking

No analytics, no cookies, no third-party telemetry, no advertising identifiers. Server logs are limited to request ids, status, timing, and safe metrics.

Full detail: results and retention. This page is not legal advice.