Dispute & anti-scam policy

Paying does not start the work. A successful payment puts the order into awaiting requirements, not in progress. You fill in the requirements; the platform drafts them into a numbered list of contract items.

The freelancer must actively accept. They press “I accept these requirements” — or bounce them back once with questions, which sends the requirements form back to you to resubmit. The delivery clock is set at that acceptance, never at payment. A freelancer cannot silently start the clock on work they haven't read.

The accepted snapshot is frozen and hashed. On acceptance the contract items are hashed (SHA-256) onto the order. That hash is what makes “this is what we agreed” checkable later instead of arguable.

Nobody gets stuck in limbo. Whoever the order is waiting on gets nudged at 24 hours and again at 72. If requirements are never submitted at all, either side may cancel penalty-free after 7 days and the client is refunded in full.

Either side can propose a split of the escrow. Release 70% and refund 30%, or any other division. The other party accepts in one tap.

Acceptance executes instantly on the wallet ledger. The freelancer's share is floored, the remainder goes to the client, and the two shares sum to the escrowed amount exactly. The order closes as settled and both sides can still review each other.

Offers have limits, so negotiation can't stall the money. Up to three rounds of offer and counter-offer; every offer expires after 72 hours, swept automatically.

Settling costs you nothing. Both parties record a positive trust event when a settlement executes. Settling is the outcome the platform wants, so it is never penalised on either side.

The respondent has 48 hours. One 24-hour extension is available, once, on request. If they never respond, the evidence window closes automatically and the silence is recorded on their trust ledger and shown to the reviewer.

Evidence closes, then nothing more is added. Statements, uploads and links are locked at that point. The case is decided on that record.

AI reads the file, and only reads it. When evidence closes, the system extracts the documents and checks the delivery item-by-item against the frozen scope contract, producing a checklist, red flags and a triage tier. It is advisory. It cannot execute a verdict, and its analysis is shown to the dispute desk only — never to either party.

A human decides, in writing. Only an admin can issue a verdict, and the server rejects it unless it carries both a written rationale and the specific contract or checklist rows that rationale rests on. Prose alone is not accepted. The verdict — release, refund, or a split — executes from escrow automatically, and both parties receive the reasoning.

One appeal, to a different admin. Within 72 hours of the verdict, and only on genuinely new evidence or a new argument — restating your case is rejected by the server. The admin who decided the case is blocked from reviewing its appeal.

An appeal corrects, it doesn't claw back. Money that already moved is never reversed out of someone's wallet. A successful appeal posts a correcting ledger entry for the difference.