Bahiran Driver App
Privacy Policy
How we collect, use, and protect your personal information as a delivery driver on the Bahiran platform.
Introduction
This Privacy Policy applies to the Bahiran Driver App — the progressive web application used by approved delivery drivers to receive and fulfill delivery orders, manage their earnings, and navigate to restaurants and customers on the Bahiran Delivery platform.
As a driver, you are a key partner in our platform. We collect more sensitive location and operational data than customer apps due to the nature of delivery services. This policy explains exactly what we collect, why, and how we protect it.
🚦 Important: Real-time GPS location tracking is active while you are online and accepting orders. This is essential for connecting you to nearby orders and enabling customers to track their delivery.
Data We Collect
We collect the following personal and operational data from drivers:
Real-Time Location Tracking
Location tracking is the core technical requirement of the Driver App. Here is exactly how it works:
- While Online: Your GPS coordinates are updated continuously and stored in Redis (in-memory cache) for fast driver-matching and live tracking by customers
- Last Known Position: Your most recent location is stored in MongoDB under your driver profile
- Geo-Indexing: Your location is geo-indexed to enable nearby driver searches using a 2dsphere index
- Going Offline: When you go offline, your location is removed from the active driver pool in Redis
- Customer Visibility: While assigned to an active order, your real-time location is visible to the customer tracking their delivery
⚠️ Location data is only actively tracked when you set yourself as online in the Driver App. You are always in control of your online/offline status.
How We Use Your Data
| Purpose | Data Used | Legal Basis |
|---|---|---|
| Matching you to delivery orders | Location, vehicle class, online status | Contract performance |
| Order navigation and routing | GPS location, restaurant/customer addresses | Contract performance |
| Enabling customer live tracking | Real-time GPS coordinates | Contract performance |
| Driver approval and vetting | Identity, vehicle, phone verification | Legal obligation / Legitimate interest |
| Earnings and wallet management | Delivery count, order amounts, fees | Contract performance |
| Withdrawal processing via Chapa | Wallet balance, bank/mobile details | Contract performance |
| Performance ratings | Rating scores from customers | Legitimate interest |
| Push notifications (new orders) | FCM tokens, device info | Consent / Legitimate interest |
| Fraud prevention & bans | Account data, device ID, behavior logs | Legitimate interest |
Earnings, Wallet & Withdrawals
Your financial data within the Driver App includes your wallet balance (net ETB), total earnings, and full transaction history. When you request a withdrawal:
- Withdrawal requests are processed via Chapa Transfer (Chapa's payout API)
- Your bank account number or mobile money details are transmitted to Chapa to process the transfer
- Bahiran retains records of withdrawal requests and their status for accounting and dispute resolution
- Applicable platform fees are deducted before transfer per the driver earnings policy
Push Notifications
We use Firebase Cloud Messaging (FCM) to send drivers push notifications about:
- New order assignments and delivery requests
- Order updates (customer cancellations, payment confirmations)
- Wallet credits and earning summaries
- Account status changes (approval, suspension notices)
The Driver App supports multiple logged-in devices simultaneously. Each device's FCM token is registered separately. Tokens are purged on logout or app removal.
Third-Party Services
| Service | Purpose | Data Shared |
|---|---|---|
| Chapa Transfer | Driver earnings payout | Wallet balance, bank/mobile details |
| Firebase (Google) | Push notifications | Device push tokens |
| Cloudinary | Profile photo storage | Profile images |
| AfroMessage | SMS OTP verification | Phone number, OTP |
| Google Maps | Navigation and map display | Route coordinates |
| Redis (RedisLabs) | Real-time location caching | GPS coordinates (while online) |
Driver Approval & Account Status
The Bahiran Driver App requires account approval by Bahiran administrators before a driver can accept orders. During and after the approval process:
- Identity, vehicle information, and phone verification status are reviewed by our team
- Approved drivers are assigned an
isApproved: truestatus in our system - Drivers who violate platform policies may have their account suspended (
isBanned: true) - You will be notified of account status changes via push notification and SMS
Data Retention
- Account & profile data — retained while account is active; deleted within 30 days of deletion request
- Delivery history & earnings — retained for up to 3 years for dispute resolution and tax compliance
- Real-time location (Redis) — cleared immediately when you go offline; no long-term location history is stored
- Last known location (MongoDB) — retained as part of your profile; cleared upon account deletion
- Financial/withdrawal records — retained for 5 years per Ethiopian financial regulations
- Push notification tokens — removed when you log out of a device
Your Rights
Security
- Passwords hashed with bcrypt (12 salt rounds)
- All API traffic encrypted via HTTPS/TLS
- JWT access tokens expire in 15 minutes; refresh tokens in 30 days
- Rate limiting on authentication endpoints
- SMS OTP for phone verification before account activation
- Geo-index queries never expose raw coordinates to other drivers
Changes to This Policy
We may update this policy when we change how we process driver data. Material changes will be communicated via in-app notification and SMS at least 7 days before taking effect.
Contact Us
Questions about driver privacy?
Reach the Bahiran Delivery privacy team at Gebeta Tech.
✉️ bahiran@gebetatech.com