Information used by the service
Account information includes your name, email, role, organisation, GitHub username and access approval. Passwords are stored as hashes, not readable passwords. Task and audit records can contain repository identifiers, source revisions, proposals, PR/check results, trial outcomes and review evidence. Security logs record requests and authentication events.
Submit only material you are authorised to share. Avoid personal data, client secrets and credentials in tasks, prompts, proposals and logs. Private repository access is limited by the account and project permissions granted to the service.
Purpose and service providers
We use this information to approve access, manage projects and claims, inspect submitted sources, run configured checks, preserve evidence, investigate failures and respond to support requests. GitHub supplies repository and CI integration; Vercel and AWS host the platform. Configured model providers receive the inputs your workflow or trial sends them.
The independent Tbench runner reads approved local Git objects and keeps source and execution logs on the enrolled device. The hosted organization control plane stores approved command policies and bounded result metadata. GitHub-integrated jobs retain their GitHub logs and configured artifacts. Hosted benchmark audits and expert trials use their separately authorized source and evidence paths.
Cookies, fonts and recordings
An essential host-only, HTTP-only session cookie keeps your account signed in; browser scripts do not receive the credential. A readable non-credential hint avoids unnecessary anonymous session requests. Your browser may also remember the project you selected; that preference is not an access permission. The reviewed interface uses local/system typography, with no Google Fonts integration or active session-replay integration. No advertising or marketing cookies are required for these flows.
Analytics or recording integrations require privacy review, consent assessment and exclusion of sensitive inputs before activation.
Retention and public certificate records
Operational task and audit evidence is retained to support review, reproducibility, security and disputes. Certificate expiry does not automatically delete the underlying evidence. No universal automatic deletion schedule is promised by this notice. Retention and deletion requests are assessed against the service relationship, evidence integrity and applicable obligations.
The public certificate lookup shows status, coverage and validity. Private repository contents, customer contact details and internal task data remain access-controlled.
Privacy requests and children
Email support@tbench.in with the subject “Privacy request” to ask about access, correction, deletion or account closure. Identify the account and request, but do not send passwords or API keys. We may need to verify your identity and authority before changing or disclosing records. No response deadline or automatic erasure is promised here.
Tbench is for adults acting professionally, not children. If you believe a child has supplied personal information, contact support with the minimum information needed to investigate. Access can be restricted and the data assessed for removal. Do not create an account for a child.