Your privacy on Uyali

Uyali is operated by WeDigitlize Ltd, the company responsible for the personal information described in this notice. UK company number 17465598. Registered office: Crown House, North Circular Road, London, England, NW10 7PN. For privacy questions and requests, contact info@wedigitliz.com.

Information used by the service

• Accounts: your email, display name, sign-in records and preferences. Passwords are handled by the account provider; they are not stored in Uyali order records.
• Errands: requested items, chosen shop, agreed prices, your delivery address, offers, messages, purchase evidence, confirmations, ratings and support reports.
• Location: your device location only after you choose a location feature and grant permission. A runner can choose to share location with the assigned buyer during an active delivery. Uyali does not request background location for this release.
• Identity checks: an identity provider may collect your identity document and live selfie after a separate notice and consent. Uyali keeps the provider reference and verification outcome rather than raw ID photos or biometric templates.
• Payments: a payment provider handles card details. Uyali keeps order-specific payment references, currency, amounts and confirmed payment states.

Why the information is needed

For cash errands, Uyali records each participant's handover confirmations, disclosed platform fees, fee obligations and collection receipts. These bookkeeping records do not represent customer deposits or a spendable wallet balance. Authorised operators can reconcile verified receipts against completed errands, with an audit record.

Information is used to create accounts, match and fulfil errands, enforce agreed spending limits, verify eligibility, process supported payments, prevent abuse, and resolve complaints. Optional location sharing and identity-provider notices describe the choices available before collection. Uyali does not sell personal information.

Who can see an errand

Unassigned runners see the items, reward and approximate delivery area needed to decide whether to make an offer. The exact address, private chat and purchase photos are limited to the buyer and assigned runner, with authorised operational access for support and security. Support evidence may have additional access restrictions.

Maps and nearby search

Nearby search is optional. It uses a recent device position, your chosen transport and the cash you declare available for purchases. These search coordinates are processed for that request and are not saved as a location history or displayed to other users. Before assignment, distances to a customer’s delivery neighbourhood use a coarse area centre, not the private doorstep. Exact delivery points and any shared tracking position are limited to the participants.

Uyali serves its OpenStreetMap-derived regional map, map labels and public place-name index from Uyali's hosting. Requests for these public files give the hosting provider ordinary network information, including your IP address and the requested files. This map does not contact OpenStreetMap tile servers or a remote geocoding service. Text entered into the map's place search is compared with the public index on your device; the search text is not sent to a server.

Opening or moving the map does not request device location. Choosing a device-location control requests permission and uses the result as a candidate; you still confirm the delivery pin separately. The optional nearby-errand search described above sends a position to Uyali for matching, and optional runner tracking shares a position with the assigned participant during an active errand. These are separate from searching local map names.

A public regional map file may be downloaded while using the map or included in the native app. It contains map data, not Uyali account or tracking records. Map availability without a connection depends on the device and the public resources already available; live errands still require a connection. Road routing uses only an explicitly configured routing service; when enabled, confirmed waypoints and the selected travel mode are sent to that service. The map does not promise live traffic or a guaranteed arrival time.

Service providers and international processing

The implementation uses Netlify for hosting, Supabase for accounts, database and private files, and Stripe integrations for supported identity and payment functions when activated. These providers may process data outside Morocco. Live processing must use the applicable provider agreements and data-protection notification and transfer arrangements. This release does not claim a CNDP registration or authorisation that has not been obtained.

Cookies and storage

Account sessions use secure, host-only HttpOnly cookies. The web app's automatic offline cache stores its public interface and, after they are requested, public map-rendering, label and place-index assets. Account and marketplace API responses, private order photos and location-sharing responses are excluded from that cache. The regional map archive is loaded separately rather than downloaded when you first open the landing page. Native app sessions use the app's native cookie storage.

If you choose to save a shopping list or delivery address, it is stored on this device for the current account. Saved lists exclude photos, recordings and delivery addresses. You can delete saved lists from Saved lists and saved addresses from the delivery step. Signing out keeps these explicitly saved entries; requesting account deletion removes this account's saved entries from the current device. Entries saved on another device must be removed there.

Retention and deletion

After completing an errand, its assigned runner can confirm the shop's name and pickup pin for place search. At least three different accounts must confirm a nearby matching pin before it appears as "Confirmed by runners". Reports from the preceding year count toward that result; negative reports can hide it. Search results include the shop name, agreed pin and confirmation count, without reporter identities, order details or delivery addresses. This is community feedback, not a guarantee that a shop or entrance is correct.

When you post an errand you may add one photo of the shop and a Google Maps or Waze link to it. Only you and your assigned runner can see them. They help the runner find the shop. Uyali opens a shared short link only to read the place it points to; the link is stored when you post the errand. The proposed retention period is 90 days after the last activity on a completed or cancelled errand, subject to the approved policy before live service opens. An open problem report or dispute preserves the media until resolved. When cleanup starts, expired links and photo access are removed; storage deletion is queued and retried if unavailable. The scheduled cleanup runs every six hours when the live backend is configured.

Account deletion stops new trading and starts removal of the profile and associated private information. Data relating to active orders, disputes, fraud investigations or a required retention period may need restricted retention. Provider redaction and deletion jobs are tracked separately; a request is not described as complete until the required operations succeed. A shared position stops being shown after two minutes, when its sharing session is revoked or expires, when the runner becomes ineligible, or when the order is no longer active. Stopping sharing deletes the latest position when the request reaches the server; delayed uploads from that revoked session are rejected. A scheduled maintenance task also removes expired samples when the live backend and task are running. It runs every six hours; an outage can delay physical cleanup, while read-time expiry still hides the position.

You can request access, correction or deletion by contacting the privacy address above. You can also start account deletion in the app under Profile → Privacy & security → Delete my account, or use the web deletion page.

Changes to this notice

The final live-service notice will identify the actual activated providers, applicable retention periods and required regulatory references before live processing opens. Material changes will be shown before a new optional use of your information begins.