Wahda Zaman Driver Privacy Policy

Effective date: 17 November 2026

Wahda Zaman Driver is used by authorised delivery drivers to receive assignments and update delivery work for Wahda Zaman. For support, email [email protected] or call +9647701942462.

Information used

The app sends sign-in credentials to the Wahda Zaman service to authenticate an authorised Driver. It processes Driver profile information (such as name, email, telephone number and profile image), Driver account identifiers, authentication tokens, assigned parcel and delivery information, recipient/pickup information supplied by the courier operation, and delivery evidence such as a signature or delivery image where a delivery action requires it.

While the Driver dashboard is active, the app can collect precise location using foreground location permission and sends it to the Wahda Zaman service for the Driver's active assigned deliveries. The Android app does not request Android background-location permission and this release does not include a background location service.

Why we use it

We use this information to authenticate Drivers, present and carry out assigned pickup/delivery work, update parcel status, record delivery evidence, provide operational support, prevent unauthorised actions, and maintain required accounting and audit records.

Sharing and SDKs

Information is transmitted to the Wahda Zaman courier backend to provide the service. The current Android Driver release includes Google Firebase Analytics and Firebase Cloud Messaging (FCM). Unless disabled on a device, Analytics may collect app-usage events, approximate geography, app and device information, and mobile or app-instance identifiers, including the Android advertising identifier where available. FCM and Firebase Installations collect Firebase installation and app identifiers, app version, and service metadata. The backend uses FCM to deliver direct Driver notifications; depending on the delivery event, a notification can contain assignment or tracking information and Merchant contact or pickup details. Google Firebase processes the applicable Analytics and messaging data under its applicable service terms. The release does not include the Firebase Crashlytics SDK. We do not use these services to display ads or sell personal information.

Security

Authentication tokens are stored using platform-backed secure storage on the device. Network communication uses HTTPS. Access to delivery data is controlled by authenticated Driver, hub, and parcel-assignment checks in the backend.

Retention and deletion requests

A Driver may submit a request through the account-deletion page, selecting “Wahda Zaman Driver.” A request is identity-verified against the selected Driver account before it is linked or processed; selecting a Driver request cannot delete a Merchant account.

Verified requests are targeted for completion within 30 calendar days. Unverified public-request contact data is retained for 30 days; verification metadata for 90 days after completion; and minimal deletion-request audit metadata for 12 calendar months after completion. Financial and accounting records are reviewed 12 calendar months after the later final relevant transaction or settlement. Backups are retained for 12 calendar months from creation. Outstanding balances, active assignments, unsettled cash custody, and reconciliation holds are documented and resolved through the normal workflow before account closure.

On completed Driver account closure, current Driver profile/contact data, tokens, current location, and unshared Driver licence/profile files are removed or anonymised and access is disabled. After a reliable Driver delivery-completion event, Driver-specific historical coordinates, direct Driver links in parcel-event history, and delivery proof images/signatures are retained for 30 days. At expiry, the service removes the Driver-specific coordinates, minimises direct Driver links while preserving parcel and financial records, and deletes eligible proof files and their application references. It does not promise complete anonymisation where other retained operational data can still identify a Driver.

Expiry is paused only for a recorded open delivery dispute, unresolved financial settlement, or legal-preservation request. An authorised administrator records the hold and its release reason; after release, overdue data is eligible for cleanup. Backups follow the separate 12-calendar-month backup lifecycle and are not changed immediately. The 30-day Driver lifecycle is approved policy but becomes operational only after the deployed cleanup configuration and scheduler are enabled and verified. These periods are operational policies, not statements of statutory retention requirements.

Contact

Email [email protected] or call +9647701942462.