Help
Help and rights centre · 2026-09-09

Privacy

How current Wafrli features use data; not a claim of zero technical risk.

Data and access

Account, contact, address, order and support information is used to run purchases and fulfilment. Technical session and action logs support security and troubleshooting. Passwords use derived hashes. Stores and drivers receive task-related information. Configured email, payment and push providers process data under their own applicable policies. Never send card details to support.

Your device and choices

An essential session cookie maintains login. Local storage may retain carts, preferences, recent orders and checkout details. Shared-device users should avoid saving private information. Clearing browser data can remove guest order access, but not server-side account orders. Push is permission-based and can be disabled in browser settings. Tracking links and delivery codes are private.

Driver location and delivery maps

Drivers explicitly enable location sharing for the active delivery and can stop it. We keep the latest point, not route history. Only the owning customer can see the assigned driver location and phone during the delivery. The point is deleted on closure or reassignment.

Sharing stops when the driver app is backgrounded and must be resumed. Stale points are not shown as live. Opening the map requests visible tiles from OpenStreetMap, which receives the network address and viewed map area, but not customer names, order codes or driver phone numbers.

Data requests

Edit your profile and addresses in Account. Use a privacy support ticket for access, correction or deletion requests; identity must be verified without asking for passwords. Accounting, order or security records may need lawful retention. The response will explain what can be removed and why other records must remain. Clearing local data does not delete the server account. No unapproved universal retention period is promised.