SavorZ Privacy Policy

Version 2026-11-14 · Zen Vitality Partners FZ-LLC

This policy explains what Zen Vitality Partners FZ-LLC ("we"), which operates SavorZ, does with personal data.

It is written for the restaurants who are our customers and the people who work there. We decide what happens to their data and we answer for it.

A diner who scans a code at a table is the restaurant's guest, not ours. The restaurant decides what happens to their answers and we hold them on its behalf, so that notice carries the restaurant's own name and sits on the restaurant's own menu. A diner who wants their data changed or deleted asks the restaurant, and we help the restaurant do it.

1. Your account and your restaurant's content

1.1 What we hold. Your email address and your role at the restaurant; your name if you gave one; a hashed password if you set one, never the password itself; a hashed PIN if you set one to tap in on a shared tablet; your Google or Apple name and email, and your Google photo, if you chose to sign in that way. We never see a Google or Apple password.

1.2 When you accept the Provider Terms we record that you accepted, which version, when, your IP address and your browser's user agent. That record is the proof the agreement exists, so we keep it for as long as the agreement matters. We also log what each person does in the dashboard, under their email address, so the restaurant can see who changed what.

1.3 Your restaurant's own content: its name, menu, recipes, dish descriptions, ingredient figures, prices, ingredient costs, allergen sheets, branding and the photographs you or we upload. That is your business information rather than personal data, and we treat it as confidential under the Provider Terms.

1.4 We bill through Stripe, by invoice or, where agreed, by card. Stripe holds the billing details and any card; we never see or store a card number. We store the customer and subscription identifiers Stripe gives us, so we know which restaurant is paid up.

1.5 Why. To set up and run your account, to show you your own data, to send you the emails, alerts and reports the service sends, and to bill you. Nothing else.

2. Health information a diner gives your restaurant

2.1 A diner's allergies, diet, sex, age, height, activity and goal get more protection than the rest of their data: some are health data, and a halal diet can reveal a religious belief. We treat them accordingly.

2.2 Your restaurant is the controller of them and we are your processor: we hold them on your instruction and use them only to size a plate, print the allergies on the ticket, count them into your reports, and tell a diner's second order in the same meal from a new diner's for billing (6.1 of the Provider Terms). Nobody at your restaurant sees one diner's answers: the kitchen gets the grams and the allergies, and your reports get counts. They are never used for marketing, never combined across restaurants other than the venues of a group you ask us to link, and never sold.

2.3 Telling a diner what happens to their answers is your duty, not ours, and it has to be done when you ask rather than when a diner asks you. The menu does it for you: one line under the questions, and a page of your own carrying your restaurant's name.

2.4 None of it is a medical record and none of it is medical advice. A serious allergy belongs with your staff. A kitchen is a shared space and software does not change that.

2.5 We hold the rest of a diner's record for you on the same terms: the first name and table they give, the dishes they order, a note they leave, and, if they save a profile, their email and whether they ticked Send me offers. The offers list is yours to download and use only for your own offers.

3. What we do not do

3.1 We do not sell personal data, and we do not share it for anyone else's advertising.

3.2 We do not build a profile of a diner across restaurants. There is no account that follows a diner between them, except across the venues of a group a restaurant asks us to link, which share a saved profile.

3.3 We do not use your restaurant's menu, prices, costs, order volumes or diner records for anything other than setting up and running the platform for you, supporting you when you ask, and counting the personalised dining experiences we invoice.

4. Who else touches the data

4.1 Vercel hosts the platform, and checks orders and code requests for automated abuse. Railway hosts the database. Cloudflare R2 stores photographs and logos. Between them they hold everything described above.

4.2 Stripe sends our invoices and takes card payments. It receives the restaurant's billing details and a count of personalised dining experiences, and nothing about any diner.

4.3 Resend sends our email: sign in links and codes, reports, alerts, kitchen tickets sent by email, and a diner's code to load a saved profile. It receives the address and the message.

4.4 Anthropic, our AI provider, reads the menus, recipes and allergen sheets we import for a restaurant, prices included, identifies foods, translates menus, and writes a short note in the monthly report from the report's counts. It receives no diner's name, email or answers.

4.5 Sentry receives error reports: what failed and where, with names, emails, answers and cookies left out.

4.6 Each of these is a processor acting on our instructions, not a party we sell to, and each is bound by data protection obligations equivalent to ours. Some are outside the UAE; their contracts with us bind them to protect the data we send them.

4.7 Other services a browser talks to directly. Google or Apple, if you sign in with them. Apple, Google or Mozilla's push services, if your team turns on alerts on a device: they pass on an encrypted alert they cannot read.

4.8 A printer, kitchen display or webhook your restaurant sets up receives each order as the kitchen sees it. It is your system, not ours.

5. How long it is kept

5.1 A restaurant's account data is kept while the account exists. When the agreement ends, the restaurant can ask us for a copy for 30 days, and then we delete it, except what we must keep: the terms acceptance record, and whatever tax and accounting law requires us to hold about payments.

5.2 A diner's name and answers stay on an order for 90 days; after that only their goal, allergies, diet and the plate sized to them stay with it. A saved profile is kept until the diner deletes it or it goes unused for 24 months. A note a diner leaves is kept until the restaurant's data is deleted. Deleting a restaurant deletes its menus, orders, saved guest profiles and notes with it, because they belong to that restaurant and to nobody else.

5.3 Sign in codes expire in 10 minutes and sign in links in 48 hours, and each is deleted once used. The counters that stop abuse hold an address only as a keyed hash, and are deleted within a day.

6. Security

6.1 Everything travels over HTTPS. Passwords are stored as hashes and never in a form anybody can read, including us.

6.2 Access to the production database is limited to those who need it to run the service.

6.3 A restaurant's printer token and webhook secret are secrets. Treat them like passwords; anyone holding one can receive that restaurant's orders.

7. Your rights

7.1 You can ask for a copy of your data, ask us to correct it, ask us to delete it, or object to what we do with it. Write to us and we will answer.

7.2 If you are a diner, ask the restaurant first: it decides what happens to your data, and we act on its instruction. If that does not work, write to us and we will help.

7.3 Depending on where you live you may also have the right to complain to a data protection authority. In the UAE, the Personal Data Protection Law gives that role to the UAE Data Office. In the UK, it is the Information Commissioner's Office (ico.org.uk).

8. If you write to us, or we write to you

8.1 If you ask us about SavorZ, or we contact your restaurant about it, we keep your name, role, work email and phone, your venue's name, city and public menu, and our notes.

8.2 They come from you; from your venue's own website and its Google listing; for a UK company, from the Companies House public register, which names its directors; and from articles that name you with your restaurant. We never buy lists of names or addresses.

8.3 We use them to offer you SavorZ: one email to an address your restaurant publishes, or a message on LinkedIn that one of us writes and sends by hand. Before we email an address, an email checking service confirms it can receive mail. Our AI provider may help us read a public menu, sort a reply or draft an answer, which a person checks before it is sent.

8.4 We do this on our legitimate interest in offering a service relevant to your restaurant. Every email says who we are and how to stop. Tell us to stop and we will not contact you again: we then keep only what we need to make sure of that.

8.5 Unless you become a customer, we keep these details for up to 12 months after our last contact, then delete them.

9. Changes and contact

9.1 If we change this policy materially we will say so in the dashboard. The version and date at the top of this page always tell you which policy you are reading.

9.2 Write to contact@savorz.co, or call +971 52 270 8553. We are Zen Vitality Partners FZ-LLC, VUPR0073 Compass Building, Al Hulaila Industrial Zone FZ, Ras Al Khaimah, United Arab Emirates.