How Operators work

Behind every task is a real person. Hannu calls them Operators — KYC-verified humans who accept offers, do the work in the real world, and submit proof. This page is a conceptual picture of how they work. There's no Operator-facing API to reference here; the Operator surface is not developer-facing.

Verified before they can work

Every Operator completes KYC before they're eligible for any task. The platform holds the sensitive identifiers this requires — and handles them under strict rules: hashed and encrypted, never logged, never displayed, never in a prompt. See safety and policy. By the time an Operator can accept an offer, they've been verified; what reaches you is that fact, not the underlying data.

WhatsApp-first, with a workspace

Operators are met where they already are. The primary channel is WhatsApp — offers, instructions, and reminders arrive there — backed by a PWA workspace for the parts of a task that need more than a chat: capturing proof, reviewing task detail, tracking payouts. This is why tasks reach the field quickly and why the experience works on the phones Operators actually carry.

The task loop, from their side

1. An offer is matched to an eligible Operator, who accepts it — emitting assignment.accepted.
2. They complete the work in the real world.
3. They submit proof — geotagged photos, a form, a recording. Capture timestamps are recorded server-side, not trusted from the device.
4. The proof is verified, and on your approval, escrow releases and the Operator is paid.

See Task lifecycle for the full state machine.

What you see of an Operator

Never their contact details or government IDs. You don't see an Operator's full name, phone number, email, or government identifiers — Operator contact is never exposed, and there's no endpoint that returns it. What you get is:

• A public projection — for a task, its state and progress; for the workers search, an Operator's first name and last initial, languages, coverage, and reputation tier. Enough to match, price, and act, with no contact details or government IDs.
• A signed Verified report — a statement of what was checked and found, designed to be filed and independently verified.

When a visit needs on-site authentication, a Pass confirms a real Operator is present under a real task — showing the on-site verifier the Operator's first name, photo, and tier, but never their contact details or government IDs.