MealVersity Delivery Partner Terms & Conditions
Entity: MealVersity Technologies Private Limited
CIN: U62099WB2025PTC284465
Effective Date: 1 August 2026
Last Updated: 1 August 2026
Registered Office: 59 Uttar Sithi Road, Barasat, Kazipara, North 24 Parganas – 700125, West Bengal, India
Contact: business@mealversity.com | +91 8900099783
Introduction and Parties
These Terms and Conditions govern the registration and use of the MealVersity Delivery Partner application and delivery services.
These Terms form an agreement between:
MealVersity: MealVersity Technologies Private Limited, having its registered office at 59 Uttar Sithi Road, Barasat, Kazipara, North 24 Parganas – 700125, West Bengal, India, referred to as "MealVersity", "we", "us" or "our"; and
Delivery Partner: The individual registering or working through the MealVersity Delivery Partner application, referred to as "Delivery Partner", "Rider", "you" or "your".
By applying, selecting "I Agree" or using the Delivery Partner App, you confirm that you have read and accepted these Terms.
1. Eligibility
A Delivery Partner must:
- Be at least 18 years old.
- Be legally permitted to work and perform delivery services.
- Hold a valid driving licence for the applicable vehicle.
- Own or be authorised to use the registered vehicle.
- Maintain valid vehicle registration, insurance and pollution certificate where required.
- Have a valid PAN and bank account.
- Have a working smartphone, mobile number and internet connection.
- Operate within an active MealVersity delivery zone.
- Complete identity, document and background verification.
- Meet applicable safety and legal requirements.
2. Registration Information
MealVersity may require:
- Full name;
- Mobile number and email;
- Current and permanent address;
- Date of birth;
- Profile photograph;
- Aadhaar or another permitted identity document;
- PAN;
- Driving licence;
- Vehicle registration certificate;
- Vehicle insurance;
- Pollution certificate;
- Bank account and IFSC;
- Emergency contact;
- Police or background-verification information, where lawful;
- Vehicle photographs; and
- Other legally required documents.
All information and documents must be genuine, current, readable and belong to the Delivery Partner or authorised vehicle owner.
3. Mobile and Email Verification
- Mobile and email OTP verification may be required.
- An OTP must not be shared with another person.
- MealVersity may block repeated or suspicious OTP requests.
- Registration cannot be completed until required verification succeeds.
4. Duplicate and Fraudulent Accounts
- A person may maintain only one approved Delivery Partner account unless MealVersity expressly permits otherwise.
- A Rider must not create another account to avoid suspension, fines, COD obligations or document review.
- MealVersity may detect duplicate accounts using phone, email, identity, PAN, bank, driving licence, vehicle and device information.
- False identity, forged documents or account rental may result in permanent rejection or termination.
- Suspected criminal fraud may be reported to an authorised authority.
5. Application Review
MealVersity may:
- Approve the application;
- Reject the application with a reason;
- Request correction;
- Request additional documents;
- Conduct physical, video or background verification;
- Require training; or
- Keep the application pending while verification continues.
Application submission does not guarantee approval.
6. Account Activation
- Delivery work may begin only after approval and activation.
- Approval is linked to the verified Rider, vehicle, bank account and service zone.
- An activated account must not be transferred, rented or shared.
- A material change in identity, vehicle, phone, address or bank details must be reported and verified.
7. Relationship Between the Parties
- The Rider performs delivery services under the applicable Partner Agreement and law.
- Unless applicable law determines otherwise, these Terms do not create ownership, partnership or authority to bind MealVersity.
- Nothing in these Terms removes employment, social-security, welfare or gig-worker rights that cannot lawfully be waived.
- The Rider must not represent that they can make contracts or promises on behalf of MealVersity.
8. Online Availability
- The Rider may mark themselves online only when ready and legally able to accept deliveries.
While online, the Rider must:
- Keep the registered device available;
- Maintain internet and location access;
- Keep required notifications enabled;
- Use a roadworthy registered vehicle; and
- Remain reasonably available in the active zone.
- The Rider should go offline when unavailable, resting or unable to drive safely.
- MealVersity may automatically mark a Rider offline because of inactivity, expired documents, safety risk or technical reasons.
9. Delivery Offers
A delivery offer may show:
- Pickup Restaurant;
- Approximate pickup and delivery area;
- Estimated distance;
- Expected payout;
- Payment method;
- Order requirements;
- Offer-expiry time; and
- Other material information.
The Rider should accept only when able to complete the delivery safely.
A Rider must not repeatedly accept orders and abandon them without a genuine reason.
10. Order Acceptance
After accepting an order, the Rider must:
- Proceed toward the Restaurant without unreasonable delay.
- Follow the authorised route where reasonably practical.
- Keep location and status information current.
- Communicate through authorised channels.
- Complete the delivery unless prevented by safety, emergency or another genuine reason.
Accepting an order does not permit unsafe driving or violation of traffic law.
11. Restaurant Pickup
At the Restaurant, the Rider must:
- Confirm arrival using the Partner App.
- Verify the Restaurant and order ID.
- Collect only the correctly assigned order.
- Check the number of packages without opening sealed food.
- Confirm pickup only after physically receiving the order.
- Keep vegetarian and non-vegetarian or food and non-food packages appropriately separated.
- Report missing packages, damaged packaging or unreasonable delay.
- Not demand unauthorised payment from the Restaurant.
The Rider must not open, consume, replace or tamper with food.
12. Delivery Status
The Rider must update statuses accurately, including:
- Accepted;
- Reached Restaurant;
- Picked up;
- On the way;
- Rider nearby;
- Arrived at customer location;
- Payment collected, where applicable; and
- Delivered.
False or premature status updates are prohibited.
13. Location and Tracking
- Location information is required while the Rider is online or handling an active delivery.
MealVersity may use location for:
- Delivery offers;
- Assignment;
- Navigation;
- ETA;
- Customer tracking;
- Safety;
- Performance;
- Fraud prevention;
- Pickup and delivery verification; and
- Dispute investigation.
- The Rider must not falsify, spoof or manipulate location.
- Disabling required tracking during an active delivery may trigger a safety or operational review.
- Temporary genuine GPS or network failure must be reported when it materially affects delivery.
14. Customer Contact
- Customer information may be used only to complete the assigned delivery.
The Rider may contact the customer for:
- Address clarification;
- Access instructions;
- Arrival notification;
- Payment coordination; or
- Immediate delivery problems.
The Rider must not:
- Contact the customer for personal reasons;
- Save customer contact details;
- Send promotional messages;
- Visit the customer later;
- Share customer information; or
- Harass, threaten or discriminate against a customer.
- Masked calling or authorised in-app contact should be used where available.
15. Delivery at Customer Location
- The Rider must travel to the confirmed address.
- Arrival must be recorded only after reaching the delivery location.
- The Rider must make reasonable efforts to locate and contact the customer.
- The Rider must wait for 10 minutes after verified arrival before requesting failed-delivery or refusal review.
- During the waiting period, the Rider must make at least three reasonable contact attempts.
- One unanswered call is not sufficient to classify a customer as unavailable.
- The Rider must follow support instructions before leaving with an undelivered order.
16. Delivery OTP and Proof
Where delivery OTP is enabled:
- The OTP must be requested only after the order physically reaches the customer.
- The Rider must not ask for the OTP in advance.
- The OTP must not be entered without customer confirmation.
- The Rider must not retain or share the OTP.
MealVersity may also use location, timestamps, contact attempts, payment confirmation or lawful delivery evidence.
False delivery proof may result in suspension or termination.
17. Cash on Delivery
- The Rider must collect only the exact amount displayed in the app.
Payment may be collected through authorised:
- Cash;
- Rider QR;
- MealVersity QR; or
- Another approved method.
- The Rider must not use an unauthorised personal QR or bank account.
- COD must be confirmed as paid before marking the order delivered.
- Cash and QR collections must be accurately reported.
- COD money is collected on behalf of the authorised party and does not belong to the Rider.
- Collected funds must be deposited or adjusted according to the Rider Finance Policy.
- Misappropriation of COD funds may result in recovery, suspension, termination and legal action.
18. Customer Refusal
If a customer refuses an order, the Rider must:
- Remain professional and avoid argument.
- Select the correct refusal reason.
- Record reasonable contact attempts.
- Provide required location or other evidence.
- Contact support.
- Keep the package sealed and protected.
- Follow the approved return or closure instruction.
The Rider must not falsely report customer refusal to avoid completing delivery.
19. Return to Restaurant
Where support approves a return:
- The Rider must return to the specified Restaurant or return point.
- Required location tracking must remain active.
- The package must remain protected.
- Handover must be recorded only after physical return.
- The Restaurant may confirm receipt or raise a supported dispute.
- The Rider must cooperate with return verification.
- Return payout and charges will follow the Rider Finance Policy.
20. Failed Delivery
A failed delivery may be attributed to the Rider where the Rider:
- Did not reach the correct address;
- Made insufficient contact attempts;
- Falsely reported arrival;
- Abandoned the order;
- Refused to follow reasonable support instructions;
- Used false location;
- Damaged or tampered with the order; or
- Collected payment without completing delivery.
A Rider will not be held responsible for failure caused solely by:
- Incorrect Restaurant order;
- Customer refusal;
- Customer unavailability after proper attempts;
- Platform failure;
- Unsafe conditions;
- Verified vehicle breakdown;
- Medical emergency;
- Government restriction; or
- Another event outside reasonable control.
21. Food Safety and Handling
The Rider must:
- Maintain a clean delivery bag.
- Protect food from contamination, rain, dust and direct exposure.
- Keep packages upright where necessary.
- Avoid placing food with unsafe or contaminating items.
- Not open sealed packages.
- Not smoke near customer food.
- Follow applicable hygiene and food-transport instructions.
- Report leakage, damage, tampering or contamination immediately.
22. Vehicle and Road Safety
- The Rider must use the approved, legally compliant vehicle.
- The Rider must wear required safety equipment.
- Traffic laws and speed limits must be followed.
- The Rider must not use the app unsafely while driving.
- The Rider must not drive under the influence of alcohol, drugs or impairing substances.
- The Rider must not allow an unauthorised person to perform a delivery.
- Accidents, serious breakdowns and safety incidents must be reported immediately.
- Delivery speed or incentives do not override road safety.
23. Earnings and Financial Rules
- The Rider should be shown the expected delivery payout before accepting an offer where operationally possible.
Rider earnings may include:
- Base delivery payout;
- Distance payout;
- Approved waiting payout;
- Return payout;
- Surge share;
- Incentive;
- Bonus; and
- Approved adjustment.
Earnings may be reduced only by disclosed and valid:
- COD adjustment;
- Verified fine;
- Duplicate payment correction;
- Advance or wallet recovery;
- Statutory deduction; or
- Approved negative adjustment.
- MealVersity must not make unexplained deductions.
- Complete financial rules will be governed by the Rider Finance Policy.
24. Fines
A fine may be imposed only when:
- The applicable rule was disclosed;
- A specific incident occurred;
- Evidence supports the incident;
- The Rider had responsibility;
- The amount is proportionate and capped;
- The same loss is not deducted twice; and
- An appeal route is available.
A performance score alone will not create an automatic financial fine.
25. Performance Monitoring
MealVersity may monitor:
- Offer acceptance;
- Accepted-order completion;
- Pickup time;
- Delivery time;
- Location compliance;
- Contact attempts;
- Customer complaints;
- Restaurant complaints;
- COD reconciliation;
- Return completion;
- Cancellation or abandonment; and
- Safety incidents.
Performance calculations should distinguish Rider fault from Restaurant, customer and platform fault.
The Rider may request review of materially incorrect records.
26. Ratings and Complaints
- Customers and Restaurants may submit ratings or complaints.
- A complaint does not automatically establish Rider fault.
MealVersity may review:
- Location history;
- Status timestamps;
- Contact attempts;
- Payment records;
- Support communications;
- Restaurant evidence; and
- Rider response.
- The Rider should be allowed to provide an explanation or evidence.
- Verified serious misconduct may result in warning, training, suspension or termination.
27. Prohibited Conduct
A Rider must not:
- Use false documents or identity.
- Share, rent or sell the account.
- Perform delivery through another person.
- Create fake orders.
- Manipulate location or delivery status.
- Steal or tamper with an order.
- Misappropriate COD funds.
- Use an unauthorised payment QR.
- Harass or discriminate against customers or Restaurant staff.
- Misuse customer information.
- Demand unauthorised tips or charges.
- Carry prohibited or unlawful items through MealVersity.
- Drive dangerously.
- Submit false accident, breakdown or refusal evidence.
- Manipulate incentives, distance or payout calculations.
- Interfere with app security.
28. Account Suspension
MealVersity may temporarily suspend a Rider account because of:
- Expired documents;
- Safety risk;
- COD mismatch;
- Suspected account sharing;
- Serious customer complaint;
- Delivery abandonment;
- Location manipulation;
- Fraud investigation;
- Customer-data misuse; or
- Material breach of these Terms.
Except in urgent safety, fraud or legal situations, the Rider should receive:
- Reason for suspension;
- Incident reference;
- Required corrective action;
- Suspension duration, where applicable; and
- Appeal route.
29. Account Termination
MealVersity may terminate the account for:
- Fraudulent identity or documents;
- Repeated account sharing;
- Theft or COD misappropriation;
- Serious customer-safety incident;
- Food tampering;
- Repeated material delivery abandonment;
- Customer-data misuse;
- Violence, harassment or unlawful conduct;
- Repeated location manipulation; or
- Another serious breach.
Termination will not remove the Rider's right to undisputed earned payouts, subject to lawful COD reconciliation, deductions and holds.
30. Insurance and Accidents
- The Rider must maintain legally required vehicle insurance.
- Any accident-support or insurance programme offered by MealVersity will be governed by its separate policy.
- The Rider must promptly report an accident occurring during an active delivery.
- MealVersity may request a police report, medical record, photograph or insurance information where reasonably required.
- Nothing in these Terms removes insurance, compensation, social-security or statutory rights that cannot lawfully be waived.
31. Rider Data and Privacy
MealVersity will process Rider information according to the Rider Privacy Policy.
The Rider must protect customer, Restaurant and MealVersity information received through the app.
A suspected data breach or lost registered device must be reported immediately.
32. Intellectual Property
- MealVersity owns or licenses the Rider App, software, trademarks and platform content.
- The Rider receives a limited, revocable and non-transferable right to use the app for authorised delivery services.
- The Rider must not copy, modify, reverse-engineer, sell or misuse the app.
- MealVersity may use an approved Rider name and photograph for customer and Restaurant identification during delivery.
33. Limitation and Responsibility
Each party remains responsible for loss reasonably caused by its own fraud, negligence, misconduct or legal breach.
No clause should improperly exclude liability for:
- Fraud;
- Wilful misconduct;
- Personal injury;
- Data breach;
- COD misappropriation;
- Unpaid earned payout; or
- Rights that cannot legally be limited.
Product requirement: final liability limits must be approved by legal counsel before this document is relied upon for a signed Rider agreement.
34. Changes to These Terms
- MealVersity may update these Terms for legal, security, technical or operational reasons.
- Material changes will be notified through the Rider App, email, SMS or another authorised channel.
- Changes will apply prospectively.
- Fresh acceptance may be required for a material change.
- Completed-delivery financial terms will not be changed retrospectively.
35. Support and Disputes
Rider Support Email: business@mealversity.com
Rider Support Number: +91 8900099783
Support Hours: 24 hours a day, 7 days a week
Escalation Officer: Tarik Anowar, Founder & CEO
Email: business@mealversity.com
Postal Address: 59 Uttar Sithi Road, Barasat, Kazipara, North 24 Parganas – 700125, West Bengal, India
The Rider may raise disputes concerning:
- Delivery status;
- COD;
- Earnings;
- Fines;
- Incentives;
- Suspension;
- Customer complaints; or
- Account termination.
MealVersity should issue a ticket number and provide a reasoned decision.
36. Governing Law
These Terms are governed by the laws of India.
Disputes that cannot be resolved through Rider Support will be referred to and finally resolved by arbitration under the Arbitration and Conciliation Act, 1996, by a sole arbitrator appointed by mutual agreement of the parties. The seat and venue of arbitration will be Kolkata, West Bengal, and proceedings will be conducted in the English language.
Subject to the arbitration clause above, courts at Kolkata, West Bengal will have exclusive jurisdiction over any matter not referable to arbitration (such as interim relief).
Nothing in this clause removes any employment, social-security, welfare, gig-worker or other statutory right of the Delivery Partner that cannot lawfully be waived or restricted by agreement.
— End of Delivery Partner Terms and Conditions —
MealVersity Technologies Private Limited · CIN: U62099WB2025PTC284465