Terms of service
Terms for using Craves.
Effective 15 August 2026. These terms apply to customer use of the Craves marketplace in Hyderabad, India. They should be read together with the Refunds & Cancellations and Privacy pages.
1. What Craves provides
Craves is a marketplace where customers can discover approved home chefs, view available dishes and meal plans, place orders, pay online, and track fulfilment. Craves coordinates the marketplace technology, payment workflow, and supported delivery workflow for eligible orders.
2. Accounts and secure access
- You must provide accurate account and order information.
- Phone possession is verified through Firebase Authentication. Craves then applies its own account roles and secure session controls.
- Do not share OTPs, passwords, session credentials, UPI PINs, card security codes, or other authentication secrets.
- You are responsible for activity performed through your account unless you report suspected unauthorised access to Craves support.
3. Menus, prices and checkout
- Dish and meal-plan availability can change as chefs update menus, capacity, and availability.
- Customer-facing prices and the final checkout amount are displayed in Indian rupees (INR).
- The amount shown in the final checkout is the amount Craves sends to the payment provider for that checkout.
- One checkout may contain chef-specific sub-orders. Each chef-specific order has its own fulfilment lifecycle after payment.
4. Payments
- Online payments are processed through Razorpay using its hosted payment experience.
- Craves does not ask customers to send card numbers, CVVs, UPI PINs, or banking passwords to Craves support.
- A browser success screen alone does not establish final payment status. Craves relies on verified server-side payment-provider status and signed provider events.
- Cash on delivery is not part of the current Craves launch payment flow.
5. Chef acceptance and fulfilment
- After verified payment, an order may wait for the assigned chef to accept it.
- Delivery is scheduled only after the relevant chef-specific order is accepted and based on its preparation timing.
- If a chef-specific order is declined or reaches the configured chef-acceptance timeout, the affected order follows the refund rules published on the Refunds & Cancellations page.
- Craves does not automatically substitute a different chef for a rejected or timed-out chef-specific order.
6. Cancellations and refunds
Refund eligibility and processing for the currently implemented order cases are described on the Refunds & Cancellations page. For an unlisted case, contact support rather than assuming that an automatic refund is available.
7. Acceptable use
- Do not misuse Craves to commit fraud, abuse a chef or customer, interfere with service operation, or attempt unauthorised access.
- Do not submit payment, account, delivery, or identity information that you are not authorised to use.
- Craves may restrict access when required to protect customers, chefs, the platform, or payment and delivery systems.
8. Support and updates
Questions about an order or these terms can be sent to support@craves.in. Material changes to these customer-facing terms will be published on this page with an updated effective date.