[UPDATE: inDrive statement on the tragedy]
We have removed a previously published statement from inDrive regarding the tragedy following a request from the organization. According to inDrive, the matter is still under investigation, and they are committed to providing clarity once all necessary information has been gathered. We will keep you informed and will share any updates as they become available.
The investigations have been concluded. Here’s inDrive’s final statement on the matter:
Zimbabwe Tragic Incident
We are deeply saddened by the passing of Mr. Artwell Nyamayaro due to a tragic incident earlier this past week. We extend our heartfelt condolences to his family and loved ones during this difficult time.
We wish to clarify that the incident occurred outside the use of our app. Our app is equipped with features that securely capture and store passenger and driver information, enabling us to assist authorities in ensuring justice is served when required. Had this ride been facilitated through our platform, we would have been able to provide all necessary details to support the investigation.
We strongly encourage all users—both passengers and drivers—to prioritize safety by only engaging in rides facilitated through our app. This is crucial in preventing such tragedies and ensuring the protection of all parties involved.
Unfortunately, this confirms our worst fears that the ride was not initiated via the inDrive platform. Had it been, inDrive would have the following information, which would make the investigation easier for the police:
Rider information
InDrive should at least have the hailer’s name, phone number, and trip information. The criminals wouldn’t have been able to hail a ride without an inDrive account, and creating one requires providing such information.
We often dislike Know-Your-Customer (KYC) protocols and having to input personal details, but in cases like these, they can be invaluable. Law enforcement can request this information from inDrive via subpoena.
In addition to the account name and phone number, trip information would be critical.
InDrive would know the ride’s starting point and intended destination. If that leads nowhere, other trip details could provide insights. For example, if there were regular pickup or drop-off addresses, those would be good places to start.
So, in summary, this is the information inDrive could have:
- Phone Number: Used to sign up for the app, which could help the police trace the criminals.
- Profile Details: Name, profile picture, and email. (While I don’t have a profile picture on mine, my name and number would lead to my ID card, which has my photo.)
- Trip History: Logs of the ride, including pickup and drop-off locations, date, time, GPS tracking, timestamped route, and in-app communication.
- Payment Information: Card details or mobile money accounts for non-cash payments. However, cash rides common in Zimbabwe might not leave a financial trace.
- In-App Chats/Calls: Messages or calls made within the app between the rider and driver.
Riders could game the system
Unfortunately, riders with nefarious intentions can somewhat game the system. If criminals preplan their crimes, they could have created an account using fake details. Or stolen IDs.
You can sign up with any name and use a stolen or improperly registered phone number. Additionally, our lax approach to KYC and SIM card registration plays into criminals’ hands. So, the next time you replace your SIM from the guys in the street, just know you’re putting yourself in danger.
Cash rides also mean no linked financial accounts for traceability. Criminals could carry out such plans from their very first trip on the platform.
Wake-up call?
InDrive should mandate ID checks for both drivers and riders during account creation, leaving no loopholes. It might be inconvenient for users and may cause a little friction but it could be that there are no rides until your ID has been verified.
Payment restrictions for first-time users could also help. Requiring a linked mobile money or bank account and limiting initial payments to traceable methods would ensure accountability.
Drivers putting themselves in danger
I’ve spoken to many inDrive drivers who game the system to avoid paying commissions. They often give riders their personal numbers for direct bookings, bypassing inDrive entirely.
Such trips leave no rider information or GPS records for law enforcement. All that remains is a call log, which might be from a stolen phone and SIM card.
Drivers might want to consider paying commissions for their own safety and avoid bypassing the system.
This also raises concerns for traditional taxi drivers who accept walk-ins. If something happens, there’s no record of who they picked up. A possible solution could be taking pictures of riders upon entry and sharing them with a trusted third party.
Share
Home
3 comments
A good article but left out one crucial point, when you book a ride, the driver calls you you save their number, next time you call them directly, unbeknownst to indrive.
The guys also want to save that bit that indrive takes so… Hapana kwatiri kuenda
Indrive driver shouldn’t take direct calls,
Client : hey you picked me last time, come pick me up at this location,
Driver: ok sure please book your ride through the app, thanks
I think POTRAZ must make sure that our mobile network operators must make that all subscribers are registered. However it seems even our state has been a big flouter of the law as we have read several news about opposition members and human rights activists receiving calls from anonymous numbers which are untraceable. E-hail operators must also just install cameras in their cars for their own safety
Where they don’t use the app to offer a ride I think they have to notify their colleagues of such unbooked trips and make these arrangements with riders they and their colleagues are familiar with.