Kousar 2447116
Nelofar 2347269
Muskan 2347268
Data Privacy and Consumer Trust: The Ethical Dilemma of inDrive Pakistan
A Night That Didn’t Feel Normal
It was already past 10:30 PM in Karachi, and the office lights of inDrive Pakistan were
slowly shutting down floor by floor.
Almost everyone had left.
But Sara Khan was still there.
She wasn’t planning to stay late that night, but something about the situation didn’t let her
leave.
Her laptop screen was open, showing an internal security alert. She had read it several
times, but it still didn’t feel real.
“Possible unauthorized access detected in user data systems.”
Sara leaned back in her chair and stared at the ceiling for a moment.
She had handled system alerts before. Bugs, delays, minor breaches, server issues — all part
of the job.
But this one felt heavier.
Because this wasn’t just system data.
This was people’s lives.
Millions of users depended on inDrive every day — students, office workers, late-night
travelers, families sending loved ones across the city.
And now there was uncertainty about whether their personal information had been
exposed.
Her phone vibrated again.
A message from senior management:
“Do not communicate externally yet. We need full confirmation before any announcement.”
Sara didn’t reply immediately.
She understood the intention behind it — avoid panic, avoid confusion, verify facts.
But one question kept repeating in her mind:
If users are potentially affected… shouldn’t they know?
Even if everything wasn’t fully confirmed yet?
⸻
Background: How inDrive Became Part of Everyday Life
inDrive had grown rapidly in Pakistan over the past few years.
What made it different from other platforms was its pricing system. Instead of fixed fares,
users and drivers could negotiate prices directly.
For many people, especially students and daily wage workers, this flexibility made it more
affordable.
Over time, the app became part of everyday routines:
• Going to university
• Traveling to offices
• Late-night rides home
• Emergency transport situations
But behind this simple experience was a large and complex system collecting continuous
user data.
Every ride generated information such as:
• Pickup and drop-off locations
• Travel routes
• Timing and frequency of trips
• User movement patterns
Most users never thought about it deeply. They just booked a ride and moved on.
But for the company, this data was essential — it helped improve efficiency, pricing, and
service reliability.
At the same time, it also created responsibility.
Because the more data a platform collects, the greater the risk when something goes wrong.
Industry Context: Rapid Growth, Limited Awareness
Pakistan’s digital ecosystem has been expanding quickly over the last decade.
More people now rely on apps for everyday tasks — transportation, food delivery,
shopping, and payments.
Ride-hailing companies such as:
• Uber
• Bykea
• inDrive
compete in a highly aggressive market.
The competition is not just about price anymore — it is also about trust, reliability, and
safety.
However, one major issue remains:
Most users in Pakistan do not fully understand how digital data works.
People often:
• Accept terms and conditions without reading
• Share location freely without hesitation
• Trust apps without questioning data usage
At the same time, regulatory frameworks are still developing.
This creates a grey zone.
Technology is moving fast.
But rules and awareness are still catching up.
The Incident: What Actually Happened
It started quietly.
The technical team noticed unusual activity in internal logs.
After deeper investigation, the team realized there might have been unauthorized access to
parts of the system.
The potentially affected data included:
• User names
• Phone numbers
• Email addresses
• Ride history
Financial data appeared safe, which reduced one layer of risk.
But ride history itself was still extremely sensitive.
Because ride history is not just information.
It shows:
• Where a person lives
• Where they work
• Their daily movement patterns
• Their habits over time
This was no longer just a technical issue.
It was a trust issue.
⸻
The Ethical Dilemma
Sara was faced with two options:
Option 1: Immediate Transparency
• Inform users quickly
• Share known information
• Accept public criticism
Option 2: Delayed Disclosure
• Wait for full confirmation
• Control messaging
• Reduce panic
Both choices had consequences.
END OF CASE