Privacy Policy

This policy covers EZ Orders - our marketing site, the ordering pages we host for restaurants, the order status pages, and the dashboards restaurants use. It does not cover a restaurant's own website, its social accounts, or anything it does with your details outside our service.

Two different answers, depending on which data you mean.

If you want a restaurant to forget you, ask the restaurant - it is their list, and we will help them do it. If you want us to delete your platform account, ask us.

The customer list belongs to the restaurant. We do not sell it, rent it, share it with other restaurants on the platform, or use it to market anything of our own to you.

• Order details - items, notes, totals, pickup or delivery time, and the restaurant you ordered from.
• Contact details - your phone number always, because that is how an order update reaches you; your name and email if you give them.
• Messaging consent - whether you agreed to marketing texts, the exact wording you were shown, and the time you agreed. We keep this because consent has to be provable, and it is the record that protects you as much as us.
• Payment status - whether a charge succeeded, the amount, and the last four digits and brand of the card. We never receive or store your full card number; Stripe handles the card itself.
• Account details - if you sign in with Google or Apple, the name, email address and stable identifier those providers return. We never receive your password with them.
• Usage analytics - pages viewed on a restaurant's ordering page, how long a visit lasted, and whether it ended in an order. See section 5.
• Support messages - anything you send us through the contact form or a support ticket.
• Technical data - IP address, browser and device type, and timestamps, kept for security and fraud prevention.

We do not collect precise device location, and we never sell personal information. If you ordered from a restaurant, nothing about you is shared for advertising: there are no third-party trackers on any restaurant's ordering page, and there is no setting anywhere that turns them on. The one exception applies only to visitors of our own marketing site, where we advertise to restaurant owners - see section 6.

We measure how restaurant ordering pages are used so owners can see which items get looked at and where people give up. Three limits are built into how this works, not just promised here:

1. 1.The identifier used to group a visit is random, generated in your browser, different for every restaurant, and never joined to your customer record. It tells a restaurant that one person visited four times rather than four people visited once, and nothing else. It is not a fingerprint and we do not attempt device fingerprinting.
2. 2.Analytics events carry a fixed set of typed fields. There is no free-form field, deliberately, so a phone number or an order note cannot end up in an analytics table and from there into every backup.
3. 3.Restaurants see their own numbers. We see platform totals and per-restaurant summaries. No restaurant can see another restaurant's data.

• The restaurant you ordered from - your order, name and contact details, so they can make and hand over your food.
• Service providers who run parts of the platform for us. The current list, and what each one receives, is on the Subprocessors page.
• Law enforcement or regulators, where we are legally required to, and only to the extent required.
• A buyer, if the business is sold or merged - with notice to you beforehand, and with this policy continuing to apply until it is replaced.

That is the whole list for anyone who ordered from a restaurant. We do not share your data with advertisers, data brokers, or other restaurants.

Visitors to our own marketing site are the single exception, and it does not reach diners. If you accept cookies on that site, Google and Meta receive the pages you viewed and a random identifier so we can tell which of our adverts brought a restaurant owner to us. Under US state privacy laws that counts as sharing for cross-context behavioural advertising. Declining the cookie notice, or sending a Global Privacy Control signal, stops it before anything loads, and you can change your mind from the Cookie choices link in the footer at any time. None of this happens on a restaurant's ordering page, whether or not you accepted anything on ours.

Depending on where you live, you can ask for a copy of your data, ask us to correct it, ask us to delete it, object to some uses, or ask us not to sell or share it. We never sell it. The only sharing we do for advertising is on our own marketing site, and you can switch that off yourself from the Cookie choices link in the footer without emailing anyone.

Email hello@ezorders.shop and say which restaurant you ordered from. We answer within 45 days, usually much sooner, and we will not treat you differently for asking. If you ask us to delete data a restaurant controls, we pass the request to them and confirm when it is done.

If you are in the EU or UK: our legal bases are in section 4, you may lodge a complaint with your supervisory authority, and where data is transferred outside your region we rely on Standard Contractual Clauses.

The service is not directed at children under 13 and we do not knowingly collect their data. If you believe a child has given us information, email hello@ezorders.shop and we will delete it.

Data is encrypted in transit and at rest. Passwords are stored hashed, never in a recoverable form. Access to production data is limited to staff who need it and is logged. Each restaurant's data is separated at the query layer so one cannot read another's.

No system is perfect. If you find a vulnerability, email hello@ezorders.shop rather than disclosing it publicly, and we will not pursue you for a good-faith report.

We update this page when what we do changes. The date at the top changes with it. Material changes get notice through the service before they take effect.