How it works Buy Send Carry Hubs Trust Track Item GuideQuestions
Create accountSign in

Delegate › Trust and safety

Trust is not a badge. It is what happens at each step.

Delegate is designed so that the people involved see the right information, the item follows the required evidence path, and every important handoff creates a record.

The exact protections available depend on the corridor, request type, item, traveler capability, Hub route, and release stage.

The Trust Stack

Identity

A person must complete the verification required before they can accept custody, purchase for someone, operate a Hub, or receive a payout.

Item clarity

Every request starts with a structured description, value, quantity, category, and evidence appropriate to that item.

Capability

Opening Carry mode does not make someone an approved traveler. Risk-bearing actions require server-controlled capability approval.

Custody proof

Approved scans, timestamps, photographs, package references, and actor records show who handled the item at each stage.

Recipient confirmation

The final handoff uses the proof method assigned to the request, such as a code, Hub release, signature, or approved photograph.

Issue recovery

When a serious mismatch or safety issue is reported, the request can be paused so the next custody or payment action does not continue blindly.

Why proof, and not promisesNot because people are untrustworthy. Because proof is what lets strangers help each other.

Your information is revealed by stage, not by curiosity.

  • Public marketplace viewers see only the information needed to understand the opportunity.
  • A selected traveler sees operational details only when the stage requires them.
  • Hub staff see only packages assigned to their approved Hub and task.
  • Recipients see their own handoff information.
  • Private evidence is not placed on the public tracking page.
  • Administrative actions are logged and restricted.

The traveler’s golden rule

If you did not see it packed, do not carry it.

Never accept:

  • an item that does not match the app record;
  • a mystery sealed package;
  • undeclared additions;
  • a request to skip inspection, scanning, or payment controls;
  • cash or off-platform compensation;
  • pressure to hide, misdescribe, or abandon an item.

If something goes wrong

A reported issue affects the next custody or payment action. What happens now:

  • the current custodian keeps the item secure;
  • no one changes the package or handoff privately;
  • evidence is preserved;
  • the assigned reviewer owns the next update;
  • the timeline shows when the request may continue.
Never hand over a package without the recordIf Delegate is temporarily unavailable, do not complete a handoff without the approved verification and record. A handoff with no record is the exact problem Delegate exists to remove.

Know before you send.

Search an item and route before you create a request.

Open the Item GuideRestricted items