Privacy policy

This policy explains how U-Dispatch of Cairo, Egypt (“we”, “us”) handles personal data in U-Dispatch.

We handle personal data in two different roles, and the distinction matters for who to ask about what.

• As a controller, for the people who deal with us directly: an operator’s staff, and anyone who contacts us through this website.
• As a processor, for the data inside an operator’s workspace: its customers, its restaurants’ staff and its riders. That data is the operator’s. We process it on their instructions, and requests about it are answered by them.

If you ordered food from a marketplace running on U-Dispatch, the operator of that marketplace — not us — is who to contact. Their own privacy policy is published on the domain you ordered from.

1. What we handle, and why

Operator staff accounts. Name, email address, phone number where given, role, second-factor settings, and a record of sign-ins and of any impersonation carried out for support. We need these to provide the service and to keep it secure.

Website enquiries. What you send us when you get in touch, so we can answer.

Inside a workspace, on an operator’s behalf. Customer names, phone numbers, email addresses, delivery addresses and their coordinates; order history; rider identity, vehicle and documents, and location while on shift; restaurant staff accounts. The purpose is set by the operator: taking orders, delivering them and settling the money behind them.

2. Where it comes from

Directly from the person, from the operator who created the account, or from the operator’s own systems where they have connected one.

3. Who it is shared with

• Infrastructure providers hosting the service and storing its data.
• Delivery channels — email, SMS and push notification providers — for messages the platform sends.
• Payment gateways connected to an operator’s workspace, where an order is paid online. Card details are handled by the gateway; the platform stores a reference to the payment, never card numbers.
• Nobody else. Personal data is not sold, and it is not shared for advertising.

Each operator’s data is isolated from every other operator’s. One operator is never given access to another’s.

4. Where it is kept

On infrastructure in the regions named in the operator’s subscription agreement. Where a provider processes data outside Egypt, that transfer is covered by the safeguards required by applicable law.

5. How long it is kept

Staff accounts and enquiries: while the relationship lasts, and then for as long as we are required to keep records.

Workspace data: for as long as the operator keeps it, subject to their own retention rules. When a subscription ends, data is available for export during the agreed wind-down period and is then deleted.

6. Rights

Depending on where you are, you may have the right to ask for a copy of your data, to have it corrected or deleted, to object to or restrict its processing, and to complain to a supervisory authority.

For data inside a marketplace, ask that marketplace’s operator. For data we hold as a controller, ask us at hello@u-dispatch.com and we will respond within the period the law allows.

7. Security

Access to production systems is restricted and authenticated. Staff accounts carry a second factor. Support access to an operator’s workspace happens through an impersonation mechanism that is recorded and visible to the operator. Financial records are append-only: a correction is a new entry, never an edit.

The security page on this site describes these measures in more detail.

8. Cookies

The public pages of this site set a cookie only to remember the language you chose. Signed-in areas set a session cookie that is necessary for you to stay signed in. There is no advertising or cross-site tracking on this site.

9. Changes

We will update this page when our handling of personal data changes, and will tell operators directly where the change affects them.

10. Contact

Privacy questions go to hello@u-dispatch.com, or by post to U-Dispatch, Cairo, Egypt.