SavorZ Provider Terms

Effective 09/10/2026 · version 2026-10-09 · Zen Vitality Partners FZ-LLC

These terms are the agreement between Zen Vitality Partners FZ-LLC, licence no. 45032031, of VUPR0073 Compass Building, Al Hulaila Industrial Zone FZ, Ras Al Khaimah, United Arab Emirates ("we"), which operates SavorZ, and the business for which we open a restaurant account on this platform (the "Restaurant", "you"). By accepting these terms in the dashboard (pressing Accept the terms, or ticking the acceptance box and pressing Agree & Continue), the person doing so confirms they are authorised to bind the Restaurant.

SavorZ provides a software tool and sets it up for the Restaurant. The Restaurant provides the food. Everything below follows from that.

1. What the platform is

1.1 The platform lets the Restaurant publish a customer menu, which we set up with each dish's main protein, carbohydrate and fat ingredient, and offer diners a plate whose ingredient quantities are sized to figures computed from the diner's own answers (goal, sex, age, height, recent and same-day activity).

1.2 The sizing is computed from the recipes and standard portions the Restaurant gives us or sets in its dashboard, and from the per 100g figures in 1.2a. The quantities on a kitchen ticket are recommendations produced by that computation. The Restaurant decides what it serves.

1.2a Per 100g figures for an ingredient come from its supplier's label where the Restaurant gives us one. Otherwise they come from an official national food composition database chosen for the Restaurant's country: USDA FoodData Central for the UAE, the rest of the Gulf and anywhere not named here, UK CoFID for the United Kingdom, ANSES Ciqual for the rest of Europe, Fineli for the Nordic countries and the Canadian Nutrient File for Canada. We read USDA FoodData Central through its API and the others from their published data. A food the chosen database does not hold is taken from USDA FoodData Central, and a food none of them holds from a standard reference value we look up once and keep. None of these publishers has reviewed or endorsed SavorZ.

1.3 The platform is provided as a service. We may improve or change features; we will not remove the core function described in 1.1 during a paid period without notice. If a change takes away something the Restaurant relies on, it may end the agreement as 11.2 describes.

2. Our role: a tool provider

2.1 We are not a party to any sale between the Restaurant and its diners. We do not decide, and take no share of, the Restaurant's menu prices or the customisation charge the Restaurant sets. We enter prices only as the Restaurant gives them to us, and those figures are stored so the menu and the kitchen ticket can show them, and so the Restaurant's reports and our invoice statement can count them.

2.2 We do not use the Restaurant's menu, prices, ingredient costs, order volumes, savings figures or diner records for any purpose other than setting up and operating the platform for the Restaurant, supporting the Restaurant when it asks us to, and counting the personalised dining experiences we invoice it for under 6.1. We do not sell them, share them with other restaurants, or use them to compete with the Restaurant.

2.3 Our staff may view the Restaurant's data only to set up and change its menu, to put it live or turn it off, to prepare its invoice, when the Restaurant asks for support, when investigating a fault or misuse, or when the law requires it. Automated systems process it to render pages, size plates, send the Restaurant's reports and alerts, and count billable plates.

2.4 We may keep aggregate statistics from which no restaurant and no diner can reasonably be re-identified (for example, total plates served across the platform) to run and describe the service. We also reuse food facts across the platform, such as what an ingredient is and its per 100g figures, with no restaurant's name or prices attached.

3. The Restaurant's responsibilities

3.1 We set up the menu from what the Restaurant gives us: its menu, recipes, standard portions, prices, supplier labels and allergen information. The Restaurant is responsible for the accuracy of what it gives us, for its prices and standard portions, and for checking its menu before it goes live and after every change we make. Sizing is only as accurate as those recipes and portions and the figures in 1.2a.

3.2 The Restaurant is solely responsible for food safety, allergen disclosure, dietary and religious labelling, and compliance with every law applying to serving food in its jurisdiction, including any approval its food authority requires before nutrition figures or claims appear on its menu. The platform does not detect allergens, does not check the allergen information the Restaurant gives us, and must not be relied on to do either.

3.2a Halal, vegetarian, plant based and pescatarian are the Restaurant's own declarations. The platform never infers them from a photograph, a recipe or an ingredient name: we mark a dish only where the Restaurant's own menu or documents mark it or the Restaurant tells us to, and the menu shows a diner only those markings and attributes them to the Restaurant. A halal marking is a religious and, in some jurisdictions, a certified claim; the Restaurant must hold whatever certification or approval its jurisdiction requires before a dish is marked, and must tell us to remove the marking as soon as that ceases to be true. Where its jurisdiction requires dishes that are not halal, or that contain pork or alcohol, to be listed or labelled in a particular way, the Restaurant must tell us how before those dishes go on the menu, and remains responsible for that listing.

3.2b Keto is not a declaration and is not asked of the Restaurant. The platform computes it from the per 100g figures in 1.2a and the Restaurant's standard portions, applied to the plate as that diner's plate is sized, and presents it as that computation. Its accuracy therefore follows from 3.1.

3.2c Allergens. The platform gives the Restaurant tools to help it communicate allergens: each dish's page lists the allergens recorded for it; a diner can declare their allergens, and they are printed on that diner's kitchen ticket; a dish recorded as containing one of those allergens is taken off that diner's menu (they can still choose to see it) and cannot be ordered by them; a dish recorded as possibly containing an allergen ("may contain") carries a warning; and the menu asks every diner to tell the Restaurant's staff about their allergies as well. These tools only repeat the allergen information recorded for each dish, which the Restaurant gives us and verifies. The Restaurant alone is responsible for the accuracy and completeness of its allergen information, for checking a diner's allergies with the diner before serving, and for what it serves. A dish with no allergen recorded is not a statement that it is free of any allergen, and a dish marked as checked and free of the listed allergens is the Restaurant's own declaration.

3.2d The Restaurant must keep each dish's allergens up to date: whenever it changes a dish's ingredients, recipe or supplier, it must tell us and verify that dish's allergens again in the dashboard before the dish is next served. Once the menu is live, a dish whose allergens are not verified is hidden from diners: when we change a dish's ingredients or allergens, or add a dish, it stays hidden until a member of the Restaurant verifies its allergens in the dashboard, and we email the Restaurant's owner and managers to ask them to. The dashboard records which member of the Restaurant verified each dish's allergens and when, and a dish whose allergens were entered by us remains the Restaurant's responsibility once the Restaurant has verified it.

3.3 The Restaurant is responsible for what its staff do with a kitchen ticket, including any decision to serve a different quantity from the one shown.

3.4 The Restaurant is responsible for its own notices to diners. The platform shows one on the Restaurant's menu, carrying the Restaurant's name, at the point a diner is asked for their answers. The Restaurant must satisfy itself that it is adequate for its jurisdiction and its menu, and tell us if it needs different wording.

3.5 The Restaurant must not give us or enter content it has no right to use, such as photographs, logos or text, and must keep its people's login credentials secure. It decides which of its people have access to its account, and must remove anyone who should no longer have it. Everything done by the Restaurant's own people signed in to its account is treated as done by the Restaurant; what our staff do in it is ours, and the activity log records which.

4. Nutrition figures are estimates, not advice

4.1 A diner's targets are estimated from a handful of self-reported answers using published formulas, with a typical weight for the diner's height in place of their own, which is never asked. They are general wellness guidance for portioning one meal. They are not medical, dietary or clinical advice and are not individualised nutrition therapy. Anyone managing a medical condition, pregnancy, an eating disorder or a prescribed diet should not rely on them without professional advice; the platform does not screen for any of these.

4.2 Plate macronutrient figures are computed from the reference values in 1.2a, which come mainly from official food composition databases, and from the Restaurant's own recipes and portions. They are not measured. Actual values vary with produce, preparation and cooking.

4.3 The Restaurant agrees not to present the figures to diners as medical advice or as measured facts, and to leave the platform's estimate wording in place.

4.4 The platform is not for diners under 16. Age is self-declared by the diner; the platform refuses an age under 16 but cannot verify it. The Restaurant must not promote the tailored menu to children.

5. Diner data

5.1 A diner may enter a first name, a table number, the answers in 1.1, their allergies and diet, a note for the Restaurant and, if they choose to save a profile, an email address and whether they want the Restaurant's offers. The Restaurant is the controller of that data: it chooses to offer the tailored menu and the questions on it, and we process the answers on its instructions, only to provide the service, and for no purpose of our own. If the law treats us as sharing that role for any of it, each party remains responsible for what these terms give it to do, and a diner may ask the Restaurant first.

5.2 Saved diner profiles are held per Restaurant and are never shared with another restaurant, except the other venues of a group we link at the Restaurant's request, which share them. We never use them to contact the diner, except to send a code the diner asks for to load their profile. A diner who ticks Send me offers joins the Restaurant's offers list, which the Restaurant downloads to send its own offers: it must send them only to the diners on its current list, give a simple way to stop in each one, and stop at once for a diner who asks.

5.3 The menu asks each diner for consent before their plate is sized, and records it with the order. The Restaurant must have a lawful basis for collecting this data from its diners and must handle diners' requests about their data. We will assist on request and will delete a diner's record when asked to by the Restaurant.

5.4 A diner's allergies, diet, sex, age, height, activity and goal are health-related data and are treated as sensitive; a halal diet can also reveal a religious belief. We act as the Restaurant's processor for them and for every other diner record, on the Restaurant's documented instructions (which these terms and the platform's settings constitute), and we: keep them confidential and restrict staff access as in 2.3; protect them with encryption in transit, access controls and the security measures of our hosting providers; notify the Restaurant as soon as we become aware of a personal-data breach affecting its data; assist the Restaurant with diners' access, correction and deletion requests; and delete or return the data as in 5.6.

5.5 Sub-processors. We use a small number of sub-processors to host the platform, send email, collect payment and provide technical services. Each is bound by data protection obligations equivalent to ours under this section, and if one of them fails to meet them, we answer to the Restaurant for it as if we had failed ourselves. Which sub-processors we use, and what each one receives, is published in our privacy notice at savorz.co/privacy. Data may be hosted outside the Restaurant's country; where it is, our contract with that sub-processor binds it to protect the data as this section requires. We will give 30 days' notice before adding or replacing a sub-processor, and the Restaurant may end the agreement if it objects.

5.6 On termination the Restaurant may ask us, within 30 days, for a copy of its menu, orders, statements and savings figures, after which we delete the Restaurant's menu, orders, savings figures and diner records, except what we must keep for invoicing and legal obligations.

6. Subscription and billing

6.1 The Restaurant pays a fixed monthly subscription and an AI layer charge as usage billing for each personalised dining experience. Both are in the Restaurant's own billing currency, at the rates agreed with us and shown on its billing page and on savorz.co/pricing. The AI layer is charged once per diner per meal, for an order in which at least one dish was personalised to that diner. A further order by the same diner in the same meal is not charged: the same diner means the same name (ignoring capital letters and spaces at either end) and identical answers, and the same meal means within 4 hours of the order that diner was charged for. An order made up entirely of dishes ordered as on the menu is not charged, and a cancelled order is not charged.

6.2 We invoice monthly, the subscription in advance and the AI layer in arrears, payable on the terms the invoice states, or charge a card on file where agreed with us. Invoices are sent by email, or through the UAE electronic invoicing system once the law requires it. Prices exclude VAT and similar taxes. Where the law requires us to charge one, we add it to the invoice; where it requires the Restaurant to account for it itself, the Restaurant does.

6.3 We set the menu up and put it live once the Restaurant has accepted these terms in the dashboard and verified the allergens of every dish. Before that the Restaurant can review its menu through its preview link, set up its kitchen ticket and, once every dish is ready and its allergens are verified, print its QR codes, but the public menu is not available to diners. There is no free trial unless we agree one with the Restaurant in writing.

6.4 Charges are non-refundable except where these terms or the law say otherwise. We may change our prices with 30 days' notice; the change applies from the next billing period, and the Restaurant may end the agreement under 7.1 before it does.

6.5 If a payment fails, the public menu keeps serving for 3 days and then stops until the payment goes through; while it is stopped, the dashboard shows the bill in place of the Restaurant's tools. Nothing is deleted. If an invoice is unpaid when due, we may also turn the public menu off until it is paid.

7. Term and termination

7.1 The agreement starts when accepted and continues month to month. Either party may end it at any time by telling the other in writing, effective at the end of the current billing period.

7.2 We may suspend or end the account immediately if it is used unlawfully or in a way that puts diners at risk. For any other breach of these terms, or fees unpaid for 30 days, we may do so if the Restaurant has not put it right within 7 days of our telling it in writing. 6.5 applies to a failed or late payment in the meantime.

8. Intellectual property

8.1 The platform, its code and its sizing method are ours. The Restaurant gets a non-exclusive, non-transferable right to use them through the platform for the term. The reference data in 1.2a belongs to its publishers and is used under their open licences.

8.2 The Restaurant's name, logo, menu, dish content, prices and data are the Restaurant's. The Restaurant grants us only the licence needed to set them up, translate them and display them on the Restaurant's own menu pages, QR cards, kitchen tickets and dashboard.

8.3 The menu a diner sees is the Restaurant's own and carries no SavorZ name or mark on its pages; its web address carries ours unless the Restaurant uses its own domain. The Restaurant may say it uses SavorZ if it wishes, and is not asked to. We will name the Restaurant as a customer only with its written consent.

8.4 We will defend the Restaurant against a third-party claim that the platform itself, used as intended, infringes that party's intellectual property, and pay the damages finally awarded, within the limit in 9.3, provided the Restaurant notifies us promptly and lets us control the defence.

9. Availability, warranties and liability

9.1 We aim for continuous availability but do not guarantee it. Maintenance and third-party outages happen; the Restaurant should keep a printed or other menu for those moments.

9.2 Except as stated here, the platform is provided as is. We do not warrant that sizing will meet any nutritional outcome or that any cost saving will be achieved; savings figures are computed from the Restaurant's own standard portions, ingredient costs and prices and are indicative.

9.3 To the fullest extent the law allows, we are not liable for indirect or consequential loss, lost profit, or any claim by a diner arising from food served, and our total liability under this agreement in any 12-month period is limited to the fees the Restaurant paid us in that period. Nothing in these terms excludes or limits liability for death or personal injury caused by negligence, for fraud, for gross negligence or wilful misconduct, or for anything that cannot lawfully be excluded, and nothing in them takes away a right the law gives the Restaurant that an agreement cannot.

9.4 The Restaurant indemnifies us against third-party claims arising from the food it serves, its menu content, its allergen, dietary and religious labelling (including any allergen information that is inaccurate, incomplete or out of date), its legal compliance, and its own handling of diner data, except to the extent a claim is caused by our breach of these terms.

10. Governing law and disputes

10.1 These terms are governed by the laws of the Dubai International Financial Centre ("DIFC Law").

10.2 The parties irrevocably agree that any dispute, controversy or claim arising out of or in connection with these terms, including their existence, validity or termination, shall be submitted to the exclusive jurisdiction of the DIFC Courts, Dubai, UAE.

10.3 The parties elect, in accordance with Rule 53.2(3) of the Rules of the DIFC Courts, that any such dispute where the amount or value of the claim does not exceed AED 1,000,000 shall be heard by the DIFC Courts Small Claims Tribunal (SCT). This election is made in this agreement and applies to all future disputes within that value.

10.4 This is an opt-in jurisdiction clause. Zen Vitality Partners FZ-LLC is registered in Ras Al Khaimah, United Arab Emirates and is not a DIFC-registered entity; the DIFC Courts have jurisdiction over parties inside or outside the DIFC who expressly agree to it in writing by specific, clear and express provisions (Article 14(B) of Dubai Law No. (2) of 2025 Concerning the DIFC Courts), as 10.2 and 10.3 do. Accepting these terms in the dashboard is the Restaurant's agreement in writing.

11. General

11.1 Confidentiality. Each party keeps the other's non-public information (for us: the platform's internals and pricing offered to the Restaurant; for the Restaurant: its menu economics, order data and diner records as described in section 2) confidential, uses it only for this agreement, and discloses it only to staff and advisers who need it, or where the law requires. This survives termination for three years.

11.2 Changes to these terms. A change to prices follows 6.4 (30 days' notice, next billing period). Any other material change is notified in the dashboard and must be accepted again before continued use. A Restaurant that does not accept it may instead end the agreement at once by telling us in writing, and we refund the subscription paid for the rest of that billing period. Non-material changes (clarifications, contact details) take effect on notice.

11.3 No assignment. The Restaurant may not assign or transfer its rights or obligations without our prior written consent. We may assign to a successor of the business on notice.

11.4 Force majeure. Neither party is liable for failure to perform caused by events beyond its reasonable control, except for the payment of fees due.

11.5 Governing language. This agreement is made in English; any translation is for convenience only and the English version governs.

11.6 Notices to us go to contact@savorz.co. Notices to the Restaurant go to the account's email address.

11.7 No waiver, severability, entire agreement. A failure to enforce a clause is not a waiver of it. If any clause is unenforceable the rest stands. Sections 2, 4, 5, 8, 9, 10 and 11 survive termination. This is the whole agreement about the platform between us and the Restaurant.