Driver identity review
Driver partners submit identity, licence and vehicle records. Review is done by people through a secure workflow — and until it happens, nothing is called verified. In this phase the review is simulated and labelled.
Safety is a product discipline: what is checked, what is shown, and what is still planned. Below, the same plain-language approach answers the questions people actually ask.

The approach
Each commitment describes how the production product is intended to behave. Where the current demonstration differs, it says so.
Driver partners submit identity, licence and vehicle records. Review is done by people through a secure workflow — and until it happens, nothing is called verified. In this phase the review is simulated and labelled.
Helmet use on boda boda trips, seatbelts where fitted, and vehicles that are insured and roadworthy. Passengers can help by confirming the plate and vehicle before boarding.
Route previews come from real map data when a routing provider is connected. Every request shows pickup, destination, status transitions and amounts in one place.
Production accounts use provider-based sign-in with minimum data. Production accounts store no passwords or identity documents in the browser.
Trips, payments and applications are reviewable records. Support pathways are being built for launch; the contact page states exactly what is connected today.
Requests can be cancelled before the trip starts, cancellations stay in the history, and nothing is charged in this phase.
Journey safety
Four moments of any journey, and the expectation at each one. Expectations are ones the product is designed to meet — the demonstration shows the states, not a live service.
Pickup, destination and the road route — where routing data is reachable — appear in the request before it is accepted.
The plate and driver name shown against the request are what to expect. In the demo, driver partners are fictional.
Acceptance, arrival and completion stay visible to both sides. Helmet on a boda boda; belts where fitted.
Trips, records and cancellations stay in the history. Support pathways are planned for launch; none claim to be live.
These are product expectations for the launch phase, shown in a clearly labelled demonstration. There is no live emergency line in this build.
Capability status
A demonstration is useful only when its boundaries are visible. These two lists are the boundary.
Before you board
These are practical expectations for passengers and drivers alike — not guarantees, and not a substitute for local judgment.
Safety questions
Five questions specific to travelling safely. Booking, payments and account questions are answered in the full FAQ.

Driver partners submit identity, licence, vehicle and insurance records, and review is done by people through a secure workflow. In this pilot that review is simulated, so no driver on this site is presented as verified.
Trip status — requested, accepted, on the way, arrived, in progress, completed — is visible to both sides. Background live location tracking is not claimed in this build.
Match the driver name and vehicle plate shown against the accepted request. Wear a helmet on a boda boda and a seatbelt where one is fitted.
Use the contact page and choose the safety topic. The message is recorded with a reference in this pilot build. There is no live emergency line — for immediate danger, contact local emergency services.
A request can be cancelled before the trip starts, and the cancellation stays in the trip history. No cancellation fee is charged in the pilot.
If something on this site reads as a promise the product cannot keep, tell us. The honesty of the interface is part of the product.