SavorZ Privacy Policy

1. If you run a restaurant

1.1 What we hold. Your email address; your name if you gave one; a hashed password if you set one, never the password itself; your Google profile name, email and photo if you chose to sign in with Google. We never see a Google 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.

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

1.4 If you subscribe, Stripe holds your payment details. 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 run your account, to show you your own data, to send you the emails the service needs to send, and to bill you. Nothing else.

2. If you are a diner at a restaurant using SavorZ

2.1 The restaurant decides. It chose to use SavorZ, it controls what is collected and how long it is kept, and it is who you ask about your own data. We process it for them and under their instruction.

2.2 What is collected when you order. Your first name; what you are eating for; your sex, age and height; your weight if you choose to give it, which is optional and never asked at the table; how active you have been recently and today; anything you tell us to avoid and any diet you follow; and the dish and quantities you ordered.

2.3 None of that requires an account and none of it requires an email address. If you choose to save your answers so a future visit is quicker, the restaurant stores them against an email address you give, for that restaurant only. A profile saved at one restaurant is never visible to another.

2.4 If you leave feedback, the restaurant receives your message, the table and the name you gave.

2.5 Why. To size a plate to you and to put that on a kitchen ticket. The figures are arithmetic over the restaurant's own ingredient data.

3. Allergies and dietary requirements

3.1 What you tell us to avoid, and any diet you follow, is health information. It gets more protection than the rest, and we treat it accordingly.

3.2 It is always optional. You can order without answering, and a guest who is never asked is not treated as a guest who answered nothing. You give it because you chose to, for the single purpose of what appears on your plate.

3.3 It is used to decide what you are offered and what is left off the ticket, and for nothing else. It is never used for marketing, never combined across restaurants, and never sold.

3.4 It is not a medical record and SavorZ is not medical advice. Tell the restaurant's staff about a serious allergy. A kitchen is a shared space and software does not change that.

4. What we do not do

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

4.2 We do not build a profile of a diner across restaurants. There is no account that follows you between them.

4.3 We do not use your restaurant's menu, prices, costs, order volumes or diner records for anything other than running the platform for you, supporting you when you ask, and calculating your invoice.

5. Who else touches the data

5.1 Hosting and the database. Our servers and our Postgres database, which is where everything above is stored.

5.2 Stripe, for payments and subscriptions, if a restaurant subscribes.

5.3 Our email provider, for sign-in links and codes, trial reminders and statements. It sees the recipient's address and the message.

5.4 Google or Apple, only if a restaurant owner chooses to sign in that way.

5.5 Each of these is a processor acting on instruction, not a party we sell to. Some are outside the UAE, so data is transferred internationally with the protections their own agreements provide.

6. How long it is kept

6.1 A restaurant's account data is kept while the account exists. Close the account and we delete it, except what we must keep: the terms acceptance record, and whatever tax and accounting law requires us to hold about payments.

6.2 Diner data is kept for as long as the restaurant keeps it. Deleting a restaurant deletes its menus, orders, saved guest profiles and feedback with it, because they belong to that restaurant and to nobody else.

6.3 Sign-in codes and links expire in minutes and are deleted after use.

7. Security

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

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

7.3 A restaurant's API key and printer token are secrets. Treat them like passwords; anyone holding one can read that restaurant's menu and receive its orders.

8. Your rights

8.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.

8.2 If you are a diner, ask the restaurant first: they hold the data and they can act on it immediately. If they cannot, write to us and we will help them.

8.3 Depending on where you live you may also have the right to complain to a data protection authority.

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. We are Zen Vitality Partners FZ-LLC, registered in Ras Al Khaimah, United Arab Emirates.