Your shop’s records stay your shop’s records.
Benchback is a hackathon application created by Shivam Gupta. It prepares and tracks parts-core returns; suppliers decide acceptance and credit. The public example contains fictional data and resets when refreshed.
What is stored
Signed-in workspaces store purchase identifiers, supplier policies, inspection observations, correction history, dispatch and receipt references, credit-memo entries and final conversation transcripts. Identity comes from Firebase Authentication. Records are scoped to the signed-in account.
Voice processing
Starting a voice conversation sends microphone audio to AssemblyAI for speech recognition, reasoning and spoken responses. Benchback does not retain audio files. AssemblyAI’s own processing and retention terms apply. The browser submits transcript text and tool requests to Benchback; these are not cryptographically authenticated recordings.
Hosting and access
The application runs on Firebase Hosting and Google Cloud Run. Records are stored in a dedicated Firestore database. Firebase Authentication verifies sign-in; a secure, HTTP-only session cookie protects your workspace. Guest accounts are tied to this browser until linked to an email account. API keys are held in Google Secret Manager. Voice uses short-lived, single-use tokens, bounded sessions and issuance quotas.
Control and retention
Export your records as CSV and individual evidence packages as JSON. Records remain until removed through workspace deletion or the hosting administrator’s retention process. Download anything you need before deleting a workspace. Provider logs or backups may follow separate retention schedules.
What the agent cannot do
The agent cannot approve returns, initiate shipments, issue refunds, post financial credits, access bank accounts or override supplier requirements. Human users confirm those records against their actual source documents. Do not enter payment credentials, customer personal data, hazardous-material instructions or secrets into a conversation.
For project questions or a data request, use the repository’s contact guidance. Do not publish private business records in public GitHub issues.
Last updated: September 17, 2026.