Terms and Conditions for RefineRack

1. Who these terms bind

These terms are between the restaurant operator and the operator of RefineRack ("RefineRack", "we", "us"). [Counsel: name the contracting party. The grievance contact is RefineRack at connect@refinerack.com. If a company or firm will contract, insert its legal name, GSTIN, and registered office.]

RefineRack is software for restaurants in India. It covers digital menus, table and session tools for hosts, waiters, and cooks, bill summaries in Indian rupees (₹), an AI waiter ("Raju"), and a web and WhatsApp concierge used to set up a restaurant. RefineRack is not a restaurant, not a food business, and not a payment provider.

Four parties matter:

• RefineRack. The platform. We provide the software. We do not cook, serve, or take payment for a meal.
• Restaurant operator. The person who creates a restaurant workspace, accepts these terms for that business, and is responsible for the menu, the staff, and the guests.
• Staff. Waiters, cooks, and hosts the operator adds to the workspace. Staff sign in with a phone. They do not accept these commercial terms, and they do not connect Google. The operator is responsible for what staff do on that workspace.
• Diner. A guest at the table, or a person who messages the restaurant on WhatsApp. A diner has no RefineRack account and does not accept a click-through contract.

The operator accepts these terms once for that business, after the phone code and before we create the workspace. If you accept, you confirm you have authority to bind that business. If you do not agree, do not create a workspace.

Staff use the workspace under the operator's acceptance. A diner uses the table page on the terms posted that day. The restaurant, not RefineRack, serves the guest, including when the guest is a child. Staff accounts are for adults.

2. The service we provide

The software lets a restaurant:

• turn an uploaded menu into a digital menu, including by sending those files to a model provider for extraction;
• run the floor: tables, sessions, a one-time table code, waitlist by name, kitchen tickets, and a bill summary in INR;
• let a diner at the table give a name, see the menu, and talk to Raju, and let someone message the restaurant on WhatsApp;
• let the operator add staff and limit what each role can do.

A restaurant workspace goes live after the setup fee is agreed, then the monthly plan applies. What the workspace can hold follows the plan. Fees are as quoted in writing or in the product when the operator accepts them. These terms do not set a price list.

We may change, suspend, or withdraw features, including during a trial, and we may set fair-use limits. We do not promise uninterrupted or error-free operation. Demo and sample restaurants are illustrations. They are not a promise that a live restaurant will work the same way.

3. Accounts

• Everyone who works the restaurant signs in with an Indian mobile number and a one-time password. That phone is the account. The operator and the staff are responsible for that phone, for codes sent to it, and for what is done from a signed-in session on that device.
• After the phone code, an operator who wants a restaurant must accept these terms once for that business, then connect a Google account. We store that Google account's email, name, and profile photo. We open Google's own account picker. We do not read other Google accounts in the browser.
• The operator confirms that the Google listing is their restaurant, and whether the Google account is a business account or a personal account. If the operator does not connect Google, we do not create a restaurant workspace. The phone login remains.
• The operator adds staff. Staff do not accept these commercial terms and do not connect Google. The operator is responsible for what those staff do on the workspace, including orders, cancellations, and bill changes. The product keeps an audit trail of those actions for the restaurant.
• Tell us promptly at connect@refinerack.com if you lose the phone tied to the operator's account.
• Do not take a role you were not given, and do not use a demo or preview on a live guest service.
• We may refuse, suspend, or close access that breaks these terms, creates a security risk, or is unused. Where a paying operator can fix the breach, we will give notice and a reasonable chance to fix it, unless delay would create a security, legal, or guest-safety risk.

4. Restaurant operators

If you operate a restaurant on RefineRack, you agree that:

• You run the restaurant. Food, FSSAI compliance, licences, service, and guest safety stay with you. RefineRack does not prepare, sell, or serve food.
• Menu truth is yours. You are responsible for item names, prices in INR, taxes, veg / non-veg / egg marks, ingredients, and allergen information shown to guests and staff. Correct anything that is wrong before guests rely on it.
• You check AI output. We may build a menu from files you upload. You must review it before guests see it. Do not put an unchecked menu in front of guests.
• The bill is yours. The amount on screen is a summary. You decide what is payable, including taxes, discounts, and any service charge. You collect payment. We do not take card or UPI payment.
• Guest and staff data. You decide why guest and staff data are needed for your service. You are responsible for how your staff use what they can see. Our privacy policy explains what the platform does with that data. The table flow collects a diner's name, not a phone number.
• Your listing. When you pick a Google listing you confirm it is your restaurant, and you tell us whether the connected Google account is a business account or a personal account.
• Your content. You confirm you have the right to upload menus, photos, and other material, and that they do not infringe anyone else's rights.
• Staff. You will not ask staff or guests to do anything unlawful through the product. You are responsible for staff you add, including waiters, cooks, and hosts.

5. Diners

• A diner scans the table QR and gives a name. The product does not ask for a phone number. There is no guest-phone field, including on a waitlist. A waitlist, if the restaurant uses one, is name only.
• The waiter gives the party a one-time code. That code locks the table session to that party. Do not share a live code outside the party. The diner has no RefineRack account.
• The bill on screen is a summary. The restaurant decides what is payable, including taxes, discounts, and any service charge. The diner pays the restaurant. RefineRack does not take card or UPI payment, does not hold the diner's money, and is not the seller of the food.
• A dispute about price, quality, or payment is between the diner and the restaurant.
• If a person messages the restaurant on WhatsApp, WhatsApp supplies the sender's phone number. That is WhatsApp's channel, not the table QR. The QR table flow still does not collect a phone number. WhatsApp's and Meta's terms also apply. The carrier may charge for data.

6. Raju and other automated features

Raju and menu extraction are automated. They can be wrong, incomplete, or out of date. They are not a chef, a doctor, or a member of the restaurant's staff.

• Suggestions and answers come from the restaurant's menu and from what is typed. They are not a guarantee that a dish is safe.
• Allergy and dietary needs must be confirmed with restaurant staff before ordering. Do not rely on Raju alone.
• The restaurant must keep dietary marks and ingredients accurate. A wrong menu produces wrong answers. The operator must review AI menu output before guests see it.
• Do not send unlawful or abusive messages, and do not try to override the assistant. We may drop those messages and suspend access.

To run these features we send menu text and chat text to Google Cloud, Firebase, and Google Gemini, and to WhatsApp when that channel is used. The privacy policy says the same thing.

7. Fees

A restaurant workspace goes live after the setup fee is agreed, then the monthly plan applies. Paid plans, setup fees, and extra capacity are the amounts quoted in writing or in the product, in INR. Unless that quote says otherwise, fees are exclusive of GST and other taxes, which the operator pays.

[Counsel: add short renewal and refund rules. Fees for a period already started are a starting point for discussion as non-refundable, except where Indian law requires a refund.]

We may change the quoted price for a later period by notice to the operator. The change applies from the next period unless the operator ends the plan before that date.

8. Your content and our software

The operator keeps ownership of menus, photos, and other material submitted for the restaurant. The operator grants RefineRack a non-exclusive licence to host, reproduce, parse, display, and transmit that material, including to the providers named in the privacy policy, only as needed to provide, secure, and support the service for that workspace. The licence ends when the material is deleted from the service, except copies we must keep for law, security, or a short backup cycle.

RefineRack, the product design, and our software stay ours. During a trial or paid plan we give the operator a limited, revocable, non-transferable right to use the service. You may not copy, resell, or reverse engineer the service except where the law does not allow that restriction.

If you give feedback, we may use it without obligation to you.

9. Acceptable use

You will not:

• break the law, or use the service to mislead guests about food, price, or who they are talking to;
• upload malware, or probe, overload, or bypass access controls, rate limits, or file limits;
• scrape the service or pull other restaurants' data;
• send spam or repeated table-code, sign-in-code, or WhatsApp requests;
• use the service to build a competing model from our prompts or from other customers' data;
• present an AI reply as a guaranteed statement by a human employee of RefineRack.

The operator is responsible for staff use of the workspace. Guest data for a visit is for that restaurant's staff, not for other restaurants.

10. Privacy

Personal data is handled as described in the Privacy Policy. That policy sits beside the Digital Personal Data Protection Act, 2023. It is not a finished opinion on the Act. The restaurant decides why guest and staff data are needed. We process guest data on the restaurant's instructions. Questions and rights requests go to the grievance contact in the privacy policy.

11. Ending use

An operator may stop at any time and may ask us to close the workspace by email to connect@refinerack.com. Staff lose access when the operator removes them or the workspace closes. We may stop the service if these terms are materially broken, if the law requires it, or if we discontinue the product. Where a paying operator can cure the breach, we will give notice and a reasonable chance to fix it before closure, unless delay would create a security, legal, or guest-safety risk.

After closure we delete or return restaurant content on a reasonable schedule, except records we keep for disputes, tax, security, or the audit log described in the privacy policy. The operator may ask for an export of menu and bill data before closure. [Counsel: set the retention periods so this section and the privacy policy match.]

12. Liability

The restaurant is solely responsible for food safety, allergen disclosure, menu accuracy, prices, taxes, and the decision to serve a guest. To the extent Indian law allows, RefineRack is not liable for allergic reactions, dietary harm, food quality, or a guest's reliance on Raju or on menu data the restaurant supplied or failed to correct.

The service is provided on an "as available" basis. We exclude implied warranties to the extent the law allows. We do not exclude liability for death or personal injury caused by our negligence, for fraud, or for any liability that Indian law does not allow a contract to exclude.

Subject to the previous sentence, we are not liable for lost profits, lost goodwill, lost data, or indirect or consequential loss. Our total liability arising out of the service in any twelve-month period is limited to the fees the operator paid us for that workspace in the three months before the claim, or INR 5,000 if no fee was paid. [Counsel: the cap is a discussion figure. Confirm consumer-law carve-outs under the Consumer Protection Act, 2019, including diner claims, and confirm that death and personal injury sit outside the cap.]

The operator will indemnify RefineRack against claims by guests, staff, or third parties arising from the restaurant's food, menu content, pricing, unlawful instructions, or breach of these terms, except to the extent caused by our fraud or wilful misconduct.

13. Law and disputes

These terms are governed by the laws of India. Courts in Bengaluru, Karnataka, have jurisdiction. [Counsel: confirm the consumer-law carve-out so a diner who is a consumer is not barred from the remedies in the Consumer Protection Act, 2019.]

14. Changes to these terms

We will post the current terms on this page. A material change is accepted again by operators only, not by staff. We will ask the operator to accept the new version for that business before the workspace continues, and we will send notice to the operator's Google account email. Staff are not asked to accept. Diners have no account. The table page is covered by the terms posted when the diner uses it. If the operator does not agree to a new version, they must stop using the service.

15. Other

• These terms, the privacy policy, and any fee quote the operator accepts in writing or in the product are the whole agreement on this subject.
• If a court holds one clause unenforceable, the rest stay in force.
• The operator may not assign these terms without our consent. We may assign them to a successor of the business.
• Failure to enforce a term once is not a waiver.
• Notices to us go to connect@refinerack.com. Notices to an operator go to the Google account email and the Indian mobile number on the account.

16. Contact

RefineRack
Email: connect@refinerack.com
Grievance contact: RefineRack, connect@refinerack.com