Privacy policy

Guest information (the details people give a restaurant through Eldour: order numbers, names, phone numbers, queue and booking details) belongs to the restaurant. The restaurant is the controller and [operating company] is its processor, acting on the restaurant's instructions. If you are a Guest and want to see, correct or delete your information, ask the restaurant first; we will help them respond.

Account information (staff and owner email addresses, sign-in records, audit logs) and information about visitors to our website: we are the controller of this.

• Digital Pager: the order number and status. A restaurant may also enter a first name, a phone number (only for opted-in alerts) and staff notes. The order page a Guest opens shows only the number, status, timings and pickup details, never phone numbers or notes.
• Live Queue: the name, party size and contact details the restaurant chooses to ask for, plus any notes or accessibility needs the Guest enters.
• Online Reservations: name, contact details, party size, date and time, and the other fields on the restaurant's form. A restaurant may configure optional sensitive fields; those are visible only to the roles the restaurant allows, every view is logged, and they are deleted sooner than other booking details.
• Staff accounts: email address, role, sign-in times and a log of important actions.
• Logos: images a restaurant uploads, stored publicly because they are shown on its pages.

We use only the cookies needed to keep staff signed in. We do not use advertising or analytics cookies. To limit abuse (for example guessing order numbers) we keep a short-lived, one-way scrambled form of a visitor's network address; the address itself is not stored.

• Names, phone numbers and notes on finished orders and queue entries are erased after a period each restaurant sets (default 30 days).
• Booking contact details are erased after the restaurant's retention period (default 90 days); sensitive booking fields after a shorter one (default 30 days).
• Guest links stop working a set time after an order is finished (default 24 hours).
• Notification subscriptions are deleted when they expire or the device stops accepting them.
• Audit logs and licence records are kept as long as needed to run and secure the service and to check licence compliance.

We use these providers to run the service (they act as our sub-processors): [Supabase: database, sign-in and file storage; Vercel: hosting]. If a restaurant turns them on, alerts go through the browser vendor's push service, the WhatsApp Business Platform (Meta) and an email provider. We do not sell personal data.

[region of the hosting project and any transfers outside Egypt / the EEA, with the safeguards used]

Depending on where you live (for example under Egypt's Personal Data Protection Law, Law No. 151 of 2020, or the GDPR) you may have the right to access, correct, delete, restrict or move your data, to withdraw consent and to complain to the data-protection authority. Restaurants have tools in the product to export and delete a Guest's information. [counsel to confirm the applicable laws and authority]

Each restaurant's data is separated from every other's by database access rules. Passwords are never stored in readable form. Guest links are long random codes that can be revoked. Access to sensitive fields is limited by role and logged. No system is perfectly secure; we will tell affected restaurants about a breach as the law requires.

[data controller details, representative if required] · [support email address]