Who provides WassalX
WassalX is operated by Ahmed Emad El Din Mahmoud Abdel Meguid at Haret El Gamea, Darb El Agamy, West Assiut, Assiut, Egypt. The English name is a transliteration and must be checked against official documents before it is treated as an official English legal name. Contact: +201019030515 or ahmedemadm90@gmail.com.
Our role and service scope
WassalX provides software for delivery companies, including order management, dispatching, driver management, tracking, cash-on-delivery records, driver custody, settlements, reporting and subscriptions. Subscriber companies operate their own delivery businesses and are responsible for the customer, driver and order data they enter. WassalX is not automatically the direct delivery provider for those orders.
Information handled by the platform
The information processed depends on the features used and may include:
- Company and account data such as names, contact details, logo, address, users, roles and login records.
- Driver data such as contact and employment details, national ID and licence information and images, profile images, availability, location and activity records.
- Customer data such as names, usernames, contact details, saved addresses and profile images.
- Order data such as pickup and delivery contacts, addresses, coordinates, notes, package details, proof of delivery, signatures, OTP verification and status history.
- Operational and financial records such as COD amounts, delivery fees, driver custody, settlements, invoices, subscription plans, discounts and gateway references.
- Notification tokens and messages, session records including IP address and user agent, application logs, language/theme preferences and interface settings.
Why information is used
Information is used to create and secure accounts, provide subscribed functionality, route and monitor delivery work, maintain financial and operational records, process and verify subscription payments, enforce plan limits, deliver notifications, provide support, prevent misuse, troubleshoot the service and meet applicable legal obligations.
Access and sharing
Data may be accessible to the subscriber company and its authorized users, assigned drivers and relevant customers according to their roles. Necessary data may be shared with infrastructure and communications providers, XPay for hosted subscription checkout and payment verification, Google Firebase Cloud Messaging for configured push notifications, and configured real-time notification providers. Information may also be disclosed when required by law or needed to protect users, the service or legal rights.
Payment information
Subscription prices and discounts are calculated by WassalX. XPay hosts the card/payment checkout. WassalX stores invoice amounts, currency, checkout/payment references and payment status needed for billing and reconciliation; the audited application does not collect raw card numbers in its own checkout form.
Security
The application uses account authentication, role and tenant access controls, hashed passwords, server-side billing calculations, signed payment webhooks and restricted document routes. No system is risk-free, and this policy does not claim end-to-end encryption, a security certification or absolute security.
Retention and deletion
Records are retained while needed to provide accounts and operations, preserve transaction and subscription history, resolve disputes, protect security, maintain backups and comply with applicable obligations. The current codebase does not define one verified retention period for every category or an automatic complete-account deletion workflow. A detailed retention and deletion schedule requires owner approval; requests can be submitted using the contact details below and will be assessed against operational and legal requirements.
Your choices and rights
Depending on applicable law and the requester’s relationship with the subscriber company, individuals may request access, correction, restriction, objection, portability or deletion. Identity and authority may need to be verified. Some records may need to be retained for billing, security, legal claims or subscriber-company obligations. Drivers and customers may also need to contact the delivery company that entered or controls their operational data.
Cookies, local storage and analytics
WassalX uses session and security cookies needed for authentication, CSRF protection and language/session continuity. Browser local storage is used for interface preferences such as theme or saved table settings. No third-party marketing analytics integration was found in the audited code as of this update. If analytics or non-essential cookies are introduced, this policy and any required consent controls should be updated first.
Policy changes and unresolved details
Material updates will be published on this page with an updated date. Items still requiring owner confirmation include the formal category-by-category retention schedule, final subprocessors and hosting locations, cross-border transfer arrangements, and confirmation of the English legal-name transliteration against official documents. No commercial registration number, tax ID, entity type or KYC approval is asserted here.