Platform rules

Simple rules for clean coordination.

These rules keep requests, messages, payment, proof, and review in one clear operating record.

Operating standard

ProxyLife verifies places, products, businesses, and environments — not people.

Requests should produce observable Local Proof: media, notes, checklist answers, timestamps, and clear context.

Messages, files, proof, and request changes stay inside ProxyLife.

A Proxy should understand location, timing, checklist, and proof expectations before accepting.

V1 uses one requester-set offer, no bidding, and no counteroffers.

Completion depends on checklist responses and required media.

Good requests make field work safer and more useful.

Provide accurate location, timing, and access instructions.

Do not ask Proxies to contact people outside the permitted scope.

Keep communication and files in the request thread.

Review delivered proof during the review window.

Proxies operate as structured local operators, not casual gig workers.

Accept only work you can complete clearly and responsibly.

Respect access rules, recording rules, and local context.

Submit accurate Local Proof with captions and timestamps.

Cancel only when necessary and give operations clear context.

Related standards

Safety, platform rules, and legal placeholders are connected so users can understand the operating model without reading a wall of policy text.