Privacy Policy
Last updated: 4 November 2026
The Arabic version is the reference in case of any difference in translation.
Responsible developer and additional data
The responsible developer is THULFEKAR.Z.DARWEESH, developer of Wassalni; contact dthulfekar@gmail.com. The service is for people aged 18 or older. You can request access to and correction of your data, contact us about privacy and request account deletion subject to the conditions below.
The service retains dates of birth previously supplied through older versions under the existing retention policy; the current version does not ask you to enter one. Identity information visible in verification-document images remains subject to the existing document-protection and retention policy. Service data includes emergency contacts you enter about third parties, meeting-point images, ratings and comments, parcel descriptions, reports, call records without audio recordings, and withdrawal account details.
We use Google Firebase as a technical processor: Analytics for usage analytics, Crashlytics for crash reports and FCM for notifications, with installation identifiers needed by those services. The captain's location broadcast never starts by itself: it starts when the captain taps "Live Trip Tracking" or "Resume live tracking" on a ride that has not ended, which may be before departure. A notice appears on first use, and after you agree the system may ask for location permission. Broadcasting continues with the screen locked or the app in the background until the ride ends or is cancelled or the captain leaves the screen. This location is visible to passengers with a confirmed or onboard booking, administration accounts authorized for fleet tracking, and holders of a tracking link a user chooses to share; it is also used for operations and safety, and to determine proximity, off-route travel and no-show evidence. A passenger may optionally share their location with their captain and the administration while the screen is open. Service records remain under the retention periods described in this policy.
1. Introduction and privacy commitment
- This policy explains how Wassalni users’ data (captains and passengers) is used, stored and protected, including ride data, meeting points and local copies on devices. THULFEKAR.Z.DARWEESH develops the platform.
2. Data we collect
Account information: Account data includes phone number, name and language preferences, gender if you choose to provide it, and address and profile photo if provided.
Verification data: identity information, national ID images and selfies for passengers and captains, plus driving licence, registration and vehicle photo for captains.
Location data: location needed for search, rides, meeting and tracking, depending on permissions and connectivity.
Meeting card: proposed and agreed point coordinates, landmark name, optional note and photo if added, who proposed the point and when each party reported arrival.
Payment and wallet data: wallet records, top-up receipt images, withdrawal requests and transfer references.
Data also includes captain document expiry dates, available drop-off location and observation time (no location is invented when missing), a short approach trace for arrival checks, parcel states, declared values and settlements, ride edit history, and notification tokens for up to 5 devices per account with language and delivery-capability information.
3. Data encryption and security
Uploaded verification documents and ID images are encrypted with AES-256-GCM before storage on the server. Administrative access is restricted to verification-review permissions. Uploaded meeting-card images use the same encryption and are accessed through an authenticated request that verifies the user is a party to the booking.
Meeting card and its image
The card and image are shared between the captain and passenger linked to the booking to identify the meeting point. Changing an agreed point requires the other party’s acceptance. Either party can request deletion of card images in the app; once the request is saved, the image becomes unavailable through the card and its file enters a persistent deletion queue that retries failures. The same applies to a replaced image no longer used by the confirmed point or current proposal; removing an image from the card does not mean its physical file is deleted immediately.
Default server retention is 7 days after the booking or ride ends or is cancelled, measured from the latest update to the booking or ride record. An hourly cleanup job removes expired cards and images, so reaching the retention period does not mean instant deletion. This period applies to meeting cards and images, not ride records or wallet transactions.
Ride copy and publishing draft on your device
To let you review a ride offline, the app keeps the last saved copy of rides you opened, including ride details, booking status, necessary contact information and the meeting card. Data is held in encrypted secure device storage separately for each account. The meeting-card image itself is not included in this copy.
The ride publishing draft is stored in the same way, including the route, time, seats, price, notes and preferences you entered. Local copies and drafts are valid for 7 days from the last save; on reading them, the app checks their age and removes expired data instead of showing it. Local copies and drafts are cleared on logout; publishing drafts are also cleared after successful publication or deletion from the publishing screen. Offline data reflects the last update, not live tracking.
Verification draft on your device
To preserve progress, the app keeps a separate draft per account and role for up to 7 days after the last save. Text data and image paths are saved in secure device storage, while images remain in the app’s private space without being added to the gallery. The draft and its local image copies are deleted after successful submission or logout. Returning to verification cleans expired drafts and old files; the app does not claim additional encryption of local image files before upload.
4. Sharing with third parties
THULFEKAR.Z.DARWEESH does not sell or rent any personal data to third parties. Sharing includes the following cases, in addition to the technical services described below:
Sharing location and name with the other ride participant (passenger with driver and vice versa) to provide the service.
Complying with official requests from competent judicial and security authorities in Iraq.
5. User rights and account deletion
You can request deletion from app settings or follow the official account-deletion instructions. Deletion is blocked until any positive or negative balance, pending top-ups and withdrawals are settled, ongoing participation ends and any received parcel is delivered or returned. Once conditions are met, the account is anonymised and personal data and documents removed through the deletion mechanism, with scheduled participation and pending requests cancelled under the approved flow. Certain records listed on the account deletion page remain, and some may identify you. Ride, booking and financial records remain for accounting purposes, without a promise to erase them all or a 48-hour deadline. Sender names are removed from chats, and self-service deletion does not create a personal copy in the administration archive.
Deletion is also blocked until pending or disputed no-show fees, top-up reversal requests and lost-parcel responsibility are resolved; forced administrative deletion cannot bypass these blockers. Only for administrative deletion for abuse, phone and identity fingerprints protected by a secret key may be retained to prevent re-registration, with no automatic expiry until the super administrator lifts the block with a recorded reason. These fingerprints are not readable copies of the phone or identity. Self-deletion and ordinary deletion do not create a re-registration block.
Self-deletion does not create a personal administrative archive. Administrative deletion saves a snapshot of account data, documents and deletion reason in an administrative archive for review and restoration, rather than immediately erasing them; the current implementation has no automatic deletion period for this archive.
Account deletion instructions and support
Data and retention
Service data includes account and language, verification documents, rides, bookings, parcels, messages, support reports, location needed for rides and meeting, push tokens, wallet records, top-up receipts, withdrawal requests and transfer references. Rejected verification documents are kept until replacement or account deletion under its workflow; no additional time limit has been approved. Replaced documents not linked to another request are deleted through cleanup, not necessarily immediately after their reference is removed. Meeting-card and local-draft retention remains 7 days as explained in their sections. Full withdrawal account details are removed after approval or rejection; the masked number, reference and financial record remain.
The temporary approach trace keeps the latest 10 minutes and at most 120 points; its cached copy expires 10 minutes after its last update, and temporary arrival evidence lasts up to 24 hours. Drop-off snapshots and edit and settlement records remain as service records with no automatic deletion period specified in the current implementation. Booking events are cleaned after 90 days, read notifications after 90 days from creation, and finished notification queue rows after 7 days, through periodic rather than instantaneous cleanup. Registering a sixth device removes the oldest registration; invalid tokens are removed when reported by the notification provider, and device registrations are cleared on logout, suspension or deletion. We do not claim an automatic deletion period for every device record.
Permissions and technical services
Verification documents are available to SUPER_ADMIN, ADMIN, MANAGER and KYC_OFFICER, not SUPPORT or FINANCE. Necessary ride, contact and location data is shared with authorised parties; a user may share a tracking link with people they choose. The app uses Firebase for notifications, crash reports and usage analytics enabled in the production release, and may use STUN/TURN services for calls. These technical services operate the functions described; your data is not sold or rented.
We send verification codes through the messaging provider OTPIQ via WhatsApp or SMS. The provider receives only the phone number and code for the purpose of sending the message.
Location, calls and notifications
Location and tracking updates depend on permission, connectivity and device data availability; the map does not guarantee continuously instant updates. SOS sends your report to the Wassalni team with your location if available. The report is not automatically sent to your emergency contacts or government authorities, and an immediate response is not guaranteed. In immediate danger, call 911; SOS is not a substitute for local emergency services. In-app calls need connectivity, microphone permission and an enabled service; the server does not record their audio under the current implementation. New notifications are in Arabic, English or Sorani according to language and supporting client, with Arabic for older clients and old notifications; names, reasons and free text remain as written by their authors.
Chat uses a secure connection, without a claim of end-to-end encryption. Off-route alerts depend on a verified route and recent locations and notify administration and passengers already onboard; they do not automatically stop a ride or send a government report.
Contact us
For questions about the privacy policy, contact THULFEKAR.Z.DARWEESH technical support by email: dthulfekar@gmail.com