1. Scope and Controller
Sabu Driver is the delivery-partner application for the Sabu local-commerce platform. It supports partner onboarding, assignment offers, pickups, delivery navigation, proof of delivery, trip history, earnings, payouts, safety, and support.
“Sabu Driver”, “Sabu”, “we”, “us”, and “our” refer to SIMINO LABTEST PRIVATE LIMITED. This driver-specific policy applies to delivery partners and applicants. Customers using Sabu are covered by the separate Sabu Privacy Policy.
Use of Sabu Driver is also governed by the Driver Terms & Conditions.
2. Information We Collect
- Account and contact data: name, phone number, email address, authentication identifiers, profile photo, address, city, and communication preferences.
- Partner and verification data: vehicle type, government-issued identity document images, Aadhaar last four digits and a one-way hash of the Aadhaar number, application status, eligibility information, and verification results.
- Delivery and work data: offered, accepted, rejected, completed, returned, or cancelled assignments; pickup and drop events; timestamps; delivery proof; trip routes; availability; earnings; incentives; payout records; and support history.
- Location data: approximate and precise device location when you request nearby work, mark yourself available, or start an active trip.
- Device and technical data: device identifiers used for account/device security, device model, operating system, app version, FCM push token, network information, crash and performance logs, and security or fraud signals.
- Customer and order data: limited recipient, contact, address, item, payment-on-delivery, and fulfilment information necessary for an assigned delivery.
3. Precise Location and Active-Trip Tracking
Sabu Driver collects and transmits approximate or precise location to find relevant assignments, route an accepted delivery, record trip progress, support pickup and handover evidence, calculate trip distance, protect partners and customers, prevent fraud, and resolve delivery disputes.
On Android, active-trip tracking uses a location foreground service with a persistent notification. It may continue while the app is not visible or the screen is off after you deliberately start a trip. The app does not declare Android's ACCESS_BACKGROUND_LOCATION permission. Tracking is tied to a visible, user-started delivery session and stops when the trip ends or the service is stopped.
Location is not used for advertising and is not sold. Denying location may prevent nearby assignment, routing, and active-delivery features from working. You can change permission access in device settings.
4. Device Permissions and Why They Are Used
- Precise and approximate location: nearby assignments, pickup and delivery navigation, trip recording, delivery evidence, safety, and dispute resolution.
- Camera: scan delivery barcodes and capture a profile photo, identity document, pickup evidence, or proof of delivery when you choose that feature.
- Photos and media: select only the profile, verification, or delivery image you choose to upload. Sabu Driver does not need to browse or use unrelated photos.
- Notifications: alert you to assignment offers, delivery status changes, security messages, payout updates, and support communications.
- Biometric authentication: use fingerprint or face authentication supported by your device to unlock the app. Sabu does not receive or store your biometric template.
- Foreground service and wake lock: keep an active, user-started delivery trip recording reliably while the screen is off, with an ongoing system notification.
- Internet and network state: authenticate your account, retrieve assignments, upload delivery events and proof, synchronize offline trip events, and detect connectivity.
Runtime permissions are requested when a related feature needs them. You may deny or later revoke optional permissions, though the related feature may be unavailable.
5. Identity Verification and Aadhaar
We use partner identity and verification information to review applications, confirm eligibility, prevent duplicate or fraudulent accounts, protect the delivery network, and comply with applicable obligations.
The app is designed to transmit the last four digits of the Aadhaar number and a one-way hash rather than storing or transmitting the full number as plain text. A document image you intentionally submit is stored in restricted cloud storage for authorised verification. Do not upload documents unless requested in the onboarding flow.
6. Customer and Merchant Information
For an assigned delivery, the app may show the recipient's name, phone number, delivery address, order notes, merchant details, item information, and collection amount. This information is…8876 tokens truncated…ax, and audit records may be retained for the period required by applicable law or a legitimate dispute. Local trip points older than 90 days are designed to be pruned from the device; server-side delivery records may be retained longer for the purposes above.
When information is no longer required, we delete it, anonymise it, or isolate it from ordinary use as appropriate.
11. Account Deletion
You can request deletion inside Sabu Driver by opening Menu → Compliance → Delete Account, confirming the request, and completing any required identity verification. The app records the request and signs you out. You may also initiate a request outside the app by emailing [email protected] from your registered email address with the subject “Sabu Driver account deletion” and your registered phone number.
Deletion removes or anonymises the partner profile, authentication data, verification materials, device registrations, and other personal data that we are not required to retain. Records required for tax, payout reconciliation, fraud prevention, safety, dispute resolution, or legal compliance may be retained for the applicable period and then deleted or anonymised. Account deactivation alone is not treated as a completed deletion request.
12. Your Choices and Rights
Subject to applicable law, you may request access, correction, updating, deletion, consent withdrawal, or grievance redressal. You can change permissions in device settings and stop active-trip tracking by ending the trip or stopping the visible service. Withdrawing required data access may make delivery work unavailable.
Send requests to [email protected]. We may verify your identity before acting on a request.
13. Security
We use reasonable safeguards including encrypted transport, authentication, access controls, restricted document storage, database policies, monitoring, and device-level secure storage. No system is completely secure; protect your device and credentials and report suspected misuse promptly.
14. Children
Sabu Driver is only for approved delivery partners who are at least 18 years old. We do not knowingly permit children to create driver accounts.
15. Changes to This Policy
We may update this policy as the app, law, or our processing changes. We will post the revised version here and update the date above. Material changes may also be communicated in the app or through registered contact details.
16. Privacy Contact and Grievance Redressal
SIMINO LABTEST PRIVATE LIMITED
Sabu Driver Privacy and Grievance Contact
House No-3, Kokila Garden Phase 1, Pokhariput, Bhubaneswar, Odisha, India
Email: [email protected]
Phone: +91 8895383198
Please identify your Sabu Driver account and describe the privacy request or complaint. We will acknowledge and address it in accordance with applicable law.