Restaurant Privacy Policy

Sharm Eats (“we”, “us”) operates a food and shop delivery service in Sharm el-Sheikh, Egypt. This policy covers the Sharm Eats Restaurant app, which partner restaurants use to receive incoming orders, accept or reject them, and update kitchen progress until an order is ready for pickup. It explains what the restaurant app collects, why, and the choices you have. It is separate from our customer Privacy Policy and our driver Privacy Policy.

What we collect from you

• Staff account details. Your work email address and a password (stored as a secure hash by our infrastructure provider), your staff role, and the restaurant your account is linked to. Accounts are created by the Sharm Eats team as part of the restaurant partnership — the app has no self-serve sign-up.
• A device push token. If you allow notifications, we store an app-scoped push token for your device so a new order can alert your kitchen tablet or phone the moment it arrives. The token is removed when you sign out.
• Order actions. When you accept, reject, or advance an order (preparing, ready), that action is recorded against your staff account in the order’s audit history so order handling stays accountable.
• Verification documents. When you upload them to get your restaurant verified, we collect photos of your business documents (such as commercial registration, tax card, and food licence). These are stored privately, used only to confirm your restaurant is eligible to sell on the platform, and are visible only to your staff and our review team.

Customer information the app shows you

To prepare an order, the app displays the order’s items, quantities, kitchen notes and allergy notes, the order total and payment method, and a delivery address summary (for example a hotel name and room number). This information belongs to the customer and is shown to your restaurant solely so the order can be fulfilled. It must not be copied, retained outside the app, or used for any other purpose. The restaurant app does not show customer phone numbers.

What we do not collect

• No location data — the app never requests your device location.
• No advertising identifiers, no ads, and no third-party analytics SDKs.
• No payment-card data — cash settlement and card processing happen outside this app.
• No contacts, photos, files, microphone, or camera access.

How we use this information

• Deliver incoming orders to your queue in real time and notify you of new ones.
• Record who accepted, rejected, or progressed each order (audit and dispute handling).
• Keep customers informed — your status updates (accepted, preparing, ready) drive the customer’s live order tracking.
• Operate, secure, and improve the Sharm Eats platform.

Sharing and processors

We do not sell personal information. Data is processed by Supabase (our database and authentication provider) and Expo (push notification delivery), acting as processors on our behalf. Your order-handling actions are visible to Sharm Eats operations staff and, as status updates, to the customer who placed the order.

Security and retention

All traffic between the app and our servers is encrypted in transit (HTTPS/TLS), and database access is restricted with row-level security so your account can only see your own restaurant’s orders. Staff accounts and order history are retained for as long as the restaurant partnership is active and as needed for bookkeeping and dispute resolution.

Your choices

• Notifications can be disabled in your device settings at any time (you’ll then need to check the app for new orders manually).
• Account removal. To deactivate a staff account or request deletion of personal information, email support@sharmeats.online from the account’s email address. We may retain records we are legally required to keep.

Changes and contact

We will update this page when the policy changes and bump the date above. Questions? Contact privacy@sharmeats.online. Sharm Eats, Sharm el-Sheikh, South Sinai, Egypt.