Clear answers before you start.

This local build is a product sandbox. It never sends money or personal information. Production terms would identify the contracting entity, rates, and support channel.

Only configured higher-risk tasks or payout rules require verification. The reason appears before collection begins.

A reward moves from pending to available only after approval. Every ledger line links back to its task and submission.

No. Open tasks show their reservation window, estimated duration, quota, and expiry so contributors can choose when to participate.

Review the versioned brief, confirm eligibility and consent, reserve capacity, complete preflight, capture, inspect warnings, and submit for review.

The marketplace explains safe eligibility reasons such as country, language, level, equipment, verification, or exhausted quota without exposing fraud controls.

Reviewers receive only the task media and metadata needed for a decision. They do not receive payout details or unnecessary account identity.

Settings can schedule deletion, revoke sessions immediately, and show which limited audit or financial records must remain.

Yes. Requirements, review timing, remediation options, and dispute windows are disclosed on the task before reservation.

Eligible decisions show a time-bounded dispute path with evidence, an independent resolver, and an auditable outcome.

After both people consent and start, encrypted isolated chunks upload continuously to private quarantine storage for malware scanning, QA, and review.

Account settings include withdrawal, export, and deletion requests. Retention consequences are shown before confirmation.

Stop immediately. Leave or cancel the session and open a safety support ticket; safety reports receive the shortest response target.