1. Information We Collect
Account & profile information
- Riders: full name, phone number, email address, account identifier, and account sign-in details. Riders may sign in with email/password, phone verification, or Google Sign-In.
- Drivers: full name, phone number, email, vehicle details (make, model, colour, and plate number), driver’s-licence and vehicle-registration document photos, and approval/verification status.
Location, trip & booking information
With permission, the Rider app accesses precise location while the app is in use to set pickup locations, match nearby drivers, calculate routes, ETAs and fares, show live trip positions, and send an SOS report. The Rider app does not request background-location permission. We also collect pickup, stop and drop-off locations; route, distance and duration; ride category; fare and payment method; ride status and history; ratings; and safety, lost-item, or support reports.
If a rider books for another passenger or requests a delivery, the rider enters the relevant passenger, sender, and/or recipient name and phone number. Delivery bookings can also include a package description and pickup or drop-off instructions.
Payment & financial information
We collect a Mobile Money (MoMo) phone number and network when a rider chooses a MoMo wallet top-up, together with transaction references, status, wallet balance, transaction history, and ride-payment records. Card checkout is hosted by Hubtel; card credentials are entered on Hubtel’s hosted checkout and do not pass through the HY3N Rider app or HY3N’s servers. HY3N does not collect or store a MoMo PIN or full card credentials.
Communications, safety & support
We store trip-scoped in-app chat messages, sender identifiers, timestamps, and delivery/read status so a matched rider and driver can coordinate a trip and HY3N can investigate a safety or support issue. A matched call opens the device’s mobile-network dialler; HY3N does not provide in-app voice calling and does not record call audio. Support and lost-item requests may include a subject, description, contact preference, and contact details that the rider chooses to provide. An SOS report can include the rider’s current location and active-trip details.
Contacts, photos & biometrics
The current Rider app does not request or access the device contacts, camera, photo library, or media picker. A rider may manually enter trusted-contact names and phone numbers in the Safety Center; those entries are stored locally on that rider’s device and are not uploaded to HY3N merely by being added. If biometric login is enabled, the device performs the biometric check locally; HY3N does not receive or store biometric templates. The Driver app uses document and vehicle photos for driver verification as described above.
Device & technical information
When notifications are enabled, we collect a push-notification token, device platform, and app version to deliver ride, wallet, and account notifications. We also receive the information required to operate Firebase Authentication and the Google Maps services used for sign-in, maps, place search, routing, and geocoding.