Privacy Policy

Two different people use Menuket, and their data is nothing alike: the store owner who opens an account and runs a menu, and the customer who opens that menu on their phone.

Owners have accounts. Customers never do — someone can browse an entire menu without us learning who they are.

• From the store owner: phone number (your identity here), name, gender, and a profile picture if you upload one.
• About the store: its name and link, logo and cover photo, description, contact links, branches and their addresses, and products with prices and images.
• From a menu customer: nothing that identifies them while browsing — only anonymous visit data for measurement, described under Measurement and analytics below. Only when they place an order do we ask for a phone number, plus a table number or delivery address depending on the kind of order. Their phone and address are also kept on their own device so they do not have to type them again, which is covered under Cookies and browser storage.
• System logs: actions taken in the dashboard — who changed what and when — for security and for supporting you.

Subscriptions are paid by hand through InstaPay, Fawry or Vodafone Cash, and you send us the transfer receipt. That means your card details never pass through us and are never stored here.

What we keep is the subscription itself: the plan, the amount, and its start and end dates.

• Running the service: showing your menu to your customers and managing your store, branches and products.
• Signing in: we send a verification code to your phone instead of using a password.
• Orders: passing order details to the store so it can prepare the order and reach the customer.
• Support and security: answering your questions and spotting misuse.

We do not sell your data or your customers' data to anyone, and we do not use it for advertising.

• The store: sees its own orders and the contact details a customer entered, so it can fulfil them.
• Service providers: server hosting, image storage, and the service that delivers verification codes over WhatsApp or SMS.
• Authorities: where a legal obligation requires it.

A menu customer deals with the store directly. We carry the order; we are not a party to the sale.

We use Google Analytics and Microsoft Clarity to see which pages get opened and how people move through a menu or the site. It tells us what to improve and what is not working.

These tools see the page opened, the device and browser, and an approximate location derived from the IP address; Clarity also records pointer movement, clicks and scrolling. We do not send them your name, phone number, address or order details — that data stays with us.

• On a menu: we send the store and branch the menu belongs to, so we know which menu was opened — nothing about the customer.
• On the site: we send the kind of page only (home, privacy, terms).
• In the dashboard: Clarity runs so we can improve how the dashboard works. Your own data and your store's data are not sent to it.

These are separate companies with their own privacy policies, and they control the data they collect under their own terms.

We store things in your browser so the platform works, not to follow you around other sites. We do not sell data and there are no ads on the platform.

• Essential: your dashboard sign-in token, the language you picked, the menu's light or dark mode, and a customer's cart. Without these the platform does not work.
• On a menu customer's phone: the last phone number and delivery address they actually sent with an order, so the next one fills itself in, and random references for their current orders so they can follow them. These stay on that device and are never sent anywhere except inside an order the customer sends themselves.
• Analytics: cookies set by Google Analytics and Clarity that tell one visit apart from another so the counts are right.

You can clear or block cookies in your browser at any time, and Google also offers a browser add-on that turns Google Analytics off entirely. A menu customer can clear their saved phone, address and order references from the menu's own settings whenever they like. Blocking the essential ones will break signing in and the cart.

All traffic runs over HTTPS. Signing in uses a short-lived verification code rather than a password, and permissions are set per staff member so not everyone sees everything.

A customer's cart is stored in their own browser and holds product ids and quantities only — never prices. The price is calculated on the server when the order is placed, so there is no stale or edited price sitting on a phone.

Order tracking works through a long random reference generated for each order rather than the order number the customer sees, so nobody can guess their way into someone else's order. The tracking view shows an order's status, its contents and its table number — no phone number, no address, and nothing that says who placed it.

We keep your store's data for as long as your account exists. If a subscription lapses the menu stops showing to customers, but your data stays exactly as it was, so renewing brings everything back in place.

Orders stay with the store as its sales record. If you ask us to delete your account, we delete your personal data and your store's data.

• Access: find out what data we hold about you.
• Correction: fix anything inaccurate, directly from the dashboard.
• Deletion: ask us to delete your account and its data.
• Objection: stop any use of your data you do not agree with.

As we add features we may update this page. The last-updated date is shown above, and if how we handle your data changes materially we will tell you.

If you have a question about your privacy, or want to exercise any of the rights above, talk to us.