Client applications
The form sends your name, work email, company, country, optional website, password, and workload description to Tbench’s existing account service. The workload description is labeled as an Actions application. Tbench administrators review it to decide whether to approve client access and discuss a pilot.
The account service hashes the password rather than storing it in readable form. Do not submit repository source, access tokens, customer datasets, or other secrets in the description. Submitting does not subscribe you to paid compute.
Sign-in and essential session storage
The frontend is hosted on Vercel and sends authentication requests server-to-server to the existing Tbench account service. Hosting and account infrastructure may process request metadata, such as IP addresses and timestamps, to operate and protect the service.
After approved client sign-in, Actions stores an authentication token in an HTTP-only, secure, host-only cookie. Browser JavaScript cannot read that cookie. The session is separate from the main and experts websites. Signing out removes the Actions browser cookie; the underlying token remains subject to the existing account service’s expiration policy.
This frontend does not add advertising, session replay, or third-party analytics scripts. Essential hosting logs are distinct from application analytics.
Calculator inputs stay in the browser.
The cost calculator performs arithmetic locally. Its inputs are not sent to an API or saved to your account. Exporting creates a JSON file on your device containing the assumptions and computed result. Sharing that file is your choice.
Questions, corrections, and deletion requests
Contact support@tbench.in for account-data questions or to request a correction or deletion. Include the account email and request, but never your password. Identity verification may be needed before changes are made.
Applications and account records are held in the shared Tbench account system. This preview does not promise a specific automated retention or deletion period. Any pilot involving customer code, logs, or infrastructure requires a separate agreed data-handling scope.