Skip to content

Tbench · Trust and support

Service terms

The boundaries of account access, task work, trials and Tbench assurance.

Published revision · 2026-10-09

Accounts and authorised use

Use Tbench only if you are at least 18, acting in a professional capacity and authorised to submit the material involved. Account approval and project enrollment are separate steps. Keep credentials private and use only the repositories, projects and operations assigned to your account.

Do not upload secrets, infringing material, personal data without authority, or code intended to attack shared infrastructure. Do not evade attempt budgets, forge CI evidence or claim another contributor’s work. Access may be restricted while a security or ownership concern is investigated.

Expert task production

An opportunity defines a category and capacity. Claiming creates or assigns a task with a unique identifier. Proposal approval, repository access, task construction, PR checks, model trials and final review remain distinct gates. Task acceptance follows the recorded check outcomes and independent final review.

Trial capacity is bounded by the project’s current policy. Exhausted, skipped or unsuitable tasks enter an operator review bucket; a reset or republish is an explicit operator action. Fellows do not need a client prepaid wallet for this flow. Payment and acceptance obligations, if any, must be agreed for the particular project; a claim alone is not a payment guarantee.

Audit results and local execution

A result applies to its recorded source, task selection and methodology revision. Issuance requires completed required-stage evidence. Local development checks and contributor-reported results support rehearsal; independent certification follows the authorised assurance process and its public identifier.

Availability is shown by the live admission and runner status. Customer audit admission stays closed when the required execution profile is not qualified. No guaranteed model pass, benchmark score, platform availability, accreditation or equivalence to another provider is promised.

Charges and renewal

Automatic recurring billing is disabled in these flows. Client audit quotes and admission state are shown separately; paused admission prevents submission charges. Expert trials use their assigned project budget.

Any future recurring purchase must disclose its price, billing frequency, renewal conditions and cancellation process before acceptance. These terms do not authorise a charge or automatic renewal, and no payment-provider launch is implied.

Fifteen-day service trial

Eligible organizations receive one 15-day platform-service trial after the first explicit service approval. Applying or signing in does not start it. The clock is shared across eligible services, is not renewed by a new invitation or reapproval, and continues during a suspension. Current dates and status appear in the authenticated workspace.

The trial does not authorize an automatic charge. Continuing with a paid plan requires a separate purchase decision. Customer-owned compute, provider charges, hosted benchmark audit credits and project model-attempt limits remain separately controlled. Expert contributors retain their project enrollment and payroll terms; a customer trial does not limit an expert’s active task to fifteen days.

Questions and disputes

Contact support@tbench.in for account, project, evidence, privacy or ownership concerns. Include the relevant public task or certificate ID and keep credentials private. Project-specific commercial agreements and applicable mandatory rights are assessed separately. Contact support for formal notices and verified legal-entity details.