Exactly how money is held, who can see what, and what happens when a job goes sideways.
Nothing is listed until it is paid for.
One tester, one workroom, nothing public.
Disputes are read by a qahuman admin.
No job is listed until it is paid for, and nothing is paid out until the founder approves.
The budget plus the 10% platform fee is charged through Stripe before the job is ever listed.
qahuman holds the money while the tester works. Neither side can touch it mid-job.
The tester submits a structured report: severity, repro steps, devices, evidence.
You approve once the report matches the brief — after revision rounds if it does not.
Approval releases the payment. The tester receives 90%; the report stays yours.
Most jobs never need an umpire — the revision loop settles them.
Every job reaches this point, then takes one of three paths.
The report answers the brief.
The held payment is released and the job closes.
Say exactly what the report missed.
The tester re-runs and resubmits.
Most jobs end approved right here.
Either side can escalate after revisions.
A qahuman admin reads the whole record.
Payout released, or budget refunded.
What an admin actually reads: the brief's focus areas, the workroom messages, the report content, and every revision note — then the payout is released or the budget refunded.
Private information stays between the founder, the one accepted tester, and — only during a dispute — an admin.
| What | Public | Assigned tester | qahuman admin |
|---|---|---|---|
| Job briefTitle, tier, budget and platform are public. The full brief and attachments are not. | Limited access | Full access | Full access |
| App credentialsEncrypted at rest, decrypted only inside the accepted tester's workroom. | No access | Full access | Limited access |
| Report contentsYours to keep. It only goes public if you publish it as a verified page. | No access | Full access | Limited access |
| MessagesWorkroom threads stay between the founder and the one accepted tester. | No access | Full access | Limited access |
| Payment detailsCards and payout accounts live with Stripe — qahuman never stores the numbers. | No access | No access | Limited access |
One exception, controlled entirely by the founder: an approved job can be published as a public verified page to showcase the work. Nothing else goes public.
Test-account credentials never appear in a listing or a proposal — only in the workroom of the one accepted tester.
Seed a test tenant with fake data. A tester should never sign in as a real customer.
Testers need the flows named in the brief, not the keys to your business.
Change the password or bin the sandbox account once the report is in your hands.
Sealed server-side by lib/credentials.mjs before anything reaches the database.
Never in the public listing, never in proposals — decrypted inside one workroom.
The job closes and workroom access ends with it.
Every job picks one. When an NDA applies, the tester signs before credentials or the private brief unlock.
Nothing sensitive to protect? Skip the NDA and keep the job friction-free.
A mutual NDA covering builds, credentials, reports, and messages — signed before access unlocks.
Upload your company's NDA. Same rule: signed before anything private is revealed.
The same payment rails protect both ends of the job — from opposite directions.
qahuman holds the budget. Nothing moves to the tester until you approve.
Report missed the brief? Send it back with notes instead of arguing.
An admin reads the recorded evidence and decides — payout or refund.
Cancel an unstarted job and the tester budget comes straight back.
Every job on the board is already paid for. No chasing invoices.
Approval releases your 90% payout through Stripe automatically.
Ratings, XP and level are earned on-platform and travel with your profile.
If a founder disputes unfairly, an admin reviews the same evidence you filed.
No anonymous inboxes. Everything a founder hires on is public and earned on the platform.
Every tester has a public profile: completed jobs, devices, specialties, and level.
All reports follow one format — severity, repro steps, evidence — so quality is comparable.
Founders rate every job across traits like report clarity. Averages and counts are public.
Deep Dive briefs only open to Pro level and above — XP is earned from approved reports, not claimed.
Read a real report format end to end, or open a job a founder chose to publish.