Safety standards

Clear operating standards for local access.

ProxyLife keeps requests focused on permitted places, products, businesses, and environments. The goal is calm coordination and clear proof, not surveillance, pressure, or risky work.

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.

Proof over assumption

Proxies document visible facts, permitted observations, and clear checklist responses.

Permissioned access

Work stays in public, accessible, or clearly permitted spaces.

No people checks

The platform does not investigate, follow, identify, or evaluate private individuals.

Calm escalation

Unclear requests are clarified, adjusted, or declined before a Proxy is put in the field.

What ProxyLife can coordinate

Requests should produce practical Local Proof that supports a decision.

Property exterior, entry, street context, and visible condition checks.

Local item availability, condition, price, and receipt proof.

Business, supplier, venue, or inventory checks in permitted areas.

Live walkthroughs where recording and access are allowed.

How Proxies should operate

Proxy standards are designed to keep field work clear and professional.

Follow the request scope and checklist instead of improvising risky actions.

Capture proof with timestamps, captions, and useful context.

Use in-app messaging for coordination and proof history.

Stop and ask for clarification if access, recording, or scope is unclear.

Related standards

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

Safety standards Prohibited tasks Platform rules Terms Privacy