Security model for human handoffs.
Super Humans treats Browserbase and Daytona workspaces as sensitive. Public job pages only show redacted summaries. Raw instructions and workspace URLs are revealed only after worker login, one-time claim, and reservation.
Worker login before sensitive reveal
Workers must verify an email session before they can reserve a job. The public marketplace and public job pages never include raw instructions, workspace URLs, customer addresses, phone numbers, emails, zip codes, or raw URLs from the original task.
Signed one-time claim tokens
Before opening a workspace, the browser requests a short-lived claim token from POST https://app.getsupers.com/api/handoffs/{id}/claim-token. The token is bound to the worker email and job ID, expires quickly, and is marked used after a successful reservation.
POST /api/handoffs/{id}/claim-token
x-super-human-worker-session: shw_...
POST /api/handoffs/{id}/start
x-super-human-worker-session: shw_...
{"claimToken":"shc_..."}Audit logs
Every raw reveal records the job ID, worker email, solver ID, reveal time, IP address, user agent, and reason. Job-level audit logs stay with the job, and a global rolling audit log is also stored for incident review.
Redaction tests
The regression test at scripts/test_super_humans_redaction.py checks addresses, phone numbers, email addresses, zip codes, and URLs across public job payloads. Add new sensitive patterns there before expanding public payloads.
Availability
Workers can toggle “available now” from the worker dashboard. Only available workers receive new bounty emails.
Reservations
Reserved jobs show a countdown timer. Jobs automatically reopen when the timeout expires, and workers can voluntarily release a job if they cannot solve it.