Contact the team
Email support@tbench.in for sign-in, project enrollment, GitHub invitation, task claim, trial, certificate or privacy help. Include your account email, public task/certificate ID if applicable, the affected page and a short description. Redact tokens, passwords, private keys and sensitive task content from screenshots and logs.
Application receipts confirm requests for team review. Contact support for application status and account recovery. Response times and recovery arrangements are confirmed by the team.
Your computer and trusted execution
A fellow can build and rehearse a task on their own laptop or PC, then submit through the project’s GitHub workflow. A runner on your own computer can reduce provider-hosted compute use, but uses your hardware, power, network and storage. It cannot accept work while it is asleep, offline or stopped.
Run only code you trust on a personal computer. Container restrictions do not make arbitrary repository code safe against the host. Never expose personal credentials or unrelated repositories to a local runner. Local checks do not consume a model attempt unless a budgeted trial is explicitly requested, and local reports are not independent certificates.
Current service status
Live readiness controls determine whether customer audits and model trials can be admitted. The customer audit flow remains closed when its required profile is not qualified; partial or skipped execution cannot issue a full certificate. The expert flow has its own project and trial budget, with no fellow wallet.
Session replay, advertising trackers and automatic recurring billing are inactive in these flows. Marketing email requires unsubscribe handling and a valid postal address before activation.