Protection without public identities
Each control has one job and appears at the stage where it is useful.
Private discovery
Journey cards use traveler initials. Direct contact remains unavailable until the traveler accepts and GD confirms the platform payment.
Journey integrity
Posting-pattern checks limit duplicate and overlapping journeys, while paid bookings reduce the capacity shown to future senders.
In-person verification
The sender checks the traveler's original ticket, resident ID match and alternate trusted contact during the physical meeting.
Payment confirmation
M-Pesa and card payments rely on provider confirmation and idempotent references, not screenshots or repeated button presses.
Two milestone codes
A sender handover code confirms physical receipt by the traveler. A separate recipient delivery code closes the journey.
Accountable resolution
Risk flags, notifications, audit history, disputes and administrator review preserve a timeline when a delivery needs attention.
Meet, compare, inspect
- Meet in a safe, public or familiar location.
- Compare the traveler with the original ticket and resident ID.
- Confirm the exact route, dates and alternate contact.
- Open and inspect contents together where lawful.
- Check airline, customs and destination restrictions.
- Never share a code before the physical milestone.
Control your account information.
Review the privacy policy, close your account, or submit a tracked request to remove selected data.