Terms of Service

You must be at least 18 and legally able to enter a contract. One person, one account. You are responsible for what happens under your account and for keeping your password to yourself.

You must give us a working email address. We use it for things you need to know about — a bid accepted, work approved, a payment that failed. Some of those messages cannot be turned off, because not receiving them would cost you money.

A project owner posts a task with a description, acceptance criteria and a bounty. Posting it is an offer to pay that bounty for work that meets those criteria.

A developer bids. A bid is an offer to do that work for that bounty. Accepting a bid forms an agreement between the owner and the developer — not between either of them and us.

A tester on a QA test plan agrees to run the described test and report honestly what happened. A tester is paid the same whether they find a problem or not. The bounty pays for the test being run. Reporting a problem that the owner confirms improves your reputation; it does not change the payment. Fabricating a problem is a breach of these terms.

When an owner accepts a bid on a task with a bounty, we charge the owner’s saved payment method at that moment and hold the funds. The task is not assigned until that charge succeeds. If it fails, the task returns to the open market and nobody is charged.

When the owner approves the submitted work, we release the bounty to the developer’s connected Stripe account. If the owner instead releases the assignment before approving, the held funds are refunded to the owner.

Approval is the trigger for payment, and it is the owner’s decision. An owner who approves work has agreed to pay for it. An owner who requests changes has not, and the developer may revise and resubmit.

Payments are processed by Stripe. Payouts are made through Stripe Connect, and you must complete Stripe’s onboarding — including identity verification and, where required, tax forms — before you can be paid. Stripe’s own terms apply to that relationship. We never see or store your full card number or your bank details.

We may charge a platform fee, deducted from the bounty before payout. The fee in effect when a bid is accepted is the fee that applies to that job, and it is fixed at that moment even if we change it later. The fee is currently zero.

Developer Pro is an optional paid subscription that raises the number of tasks you can hold at once. It renews automatically until cancelled. You can cancel at any time and keep the benefits until the end of the period you have paid for.

Subscription fees are not refundable for a period already begun, except where the law says otherwise. If a renewal payment fails, we will tell you and your account returns to the free limits.

Disagreements about whether work meets the acceptance criteria are between the owner and the developer. We are not a judge of work quality and we do not arbitrate.

We may step in where these terms are being broken — fabricated test reports, work that was not the developer’s to submit, attempts to move payment off the platform, or abuse of another user.

If a cardholder disputes a charge with their bank, Stripe’s dispute process governs the outcome, and we may withhold or reverse a related payout while it is open.

• Submit work that is not yours to give, or that infringes someone else’s rights.
• File a test report you know to be untrue, in either direction.
• Arrange payment outside the platform to avoid fees, escrow, or the protections both sides get from it.
• Post unlawful, harassing, or deliberately misleading content.
• Attempt to access accounts, data, or systems that are not yours.
• Automate account creation, bidding, or scraping at a scale that degrades the service.

You can report any of this from the task or the user in question. We may suspend an account that breaks these rules. A suspension does not take money someone has already earned — work already in progress is completed and paid as normal.

You keep ownership of what you post. Once an owner approves a submission and it is paid for, ownership of that deliverable passes to the owner, unless the two of you agreed otherwise in writing in the task itself.

Screenshots attached to a test report belong to the owner of the project being tested. They are stored privately and shown only to people involved in that task.

You give us permission to store and display what you post, only so far as is needed to run the service.

You can close your account at any time from your profile. We will not let you close it while money is in flight or while someone is mid-way through work you commissioned — finish or release those first.

Closing removes your personal details. It does not erase the record of payments that were made, reviews you left about other people’s work, or deliverables an owner paid for — those are other people’s records as much as yours, and we are required to keep financial records. See the Privacy Policy for exactly what is kept and what is removed.

The service is provided as it is. We do not promise that any task will attract bids, that any bid will be accepted, or that any developer or owner will perform well.

To the extent the law allows, our total liability to you for any claim is limited to the greater of the fees we earned from your transactions in the twelve months before the claim, or one hundred dollars. We are not liable for lost profits or indirect losses.

Nothing here limits liability that cannot legally be limited.

We may update these terms. If a change materially affects you we will tell you by email before it takes effect. Continuing to use the service after that means you accept the new version. A change never applies retroactively to a bounty already accepted.

Questions about these terms: legal@example.com (replace before launch).