ProxyLife
Prohibited tasks

Work ProxyLife will not coordinate.

Restricted requests are redirected before submission whenever possible. The standard is simple: no unsafe, illegal, invasive, deceptive, or off-platform activity.

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.

No surveillance

No following, tracking, hidden recording, or attempts to identify private people.

No restricted goods

No weapons, illegal substances, counterfeit documents, or other restricted items.

No impersonation

No pretending to be the requester or using private credentials.

No unsafe pressure

No harassment, intimidation, trespass, or attempts to access non-public spaces.

Blocked categories

These categories should be declined or rewritten before a request can move forward.

People investigation, surveillance, stalking, or relationship checks.
Illegal, regulated, counterfeit, or dangerous goods.
Credential use, account access, hacking, phishing, or private data gathering.
Trespass, hidden recording, harassment, threats, or coercion.

Allowed alternatives

Many requests can be reframed into safe, useful Local Proof.

Verify a public business address instead of investigating a person.
Photograph a storefront or permitted product display instead of entering private areas.
Confirm item condition and price instead of bypassing seller or platform rules.
Document neighborhood context without filming people or private spaces.

Related standards

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