Before accepting work
Workers should read the full instructions, target data, proof requirements, payout, location, and available quantity. Questions should be resolved before work begins whenever the workflow allows.
Revision requests
A revision request should identify the unmet requirement and the correction needed. It must not introduce a materially different task after acceptance without a properly funded change.
Rejection requests
A rejection request should state the specific mismatch between the original requirement and submitted proof. Rejection must not be used to obtain valid work without payment.
Admin review
Admin may consider task text, saved dynamic fields, timestamps, proof files, revision history, user notes, wallet and escrow records, and relevant policy. Missing or contradictory evidence can affect the decision.
Abuse of the process
Threats, fabricated evidence, off-platform payment pressure, credential theft, review manipulation, or repeated bad-faith disputes may lead to restrictions and further investigation.