MealVersity Delivery Partner Privacy Policy

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

This Privacy Policy explains how MealVersity Technologies Private Limited, operating under the brand name "MealVersity", collects, uses, stores, shares and protects information relating to applicants and approved Delivery Partners.

In this Policy, "Delivery Partner", "Rider", "you" or "your" refers to an individual applying for or performing delivery services through the MealVersity Delivery Partner App.

1. Information We Collect

1.1 Identity and contact information

We may collect:

• Full name;
• Mobile number;
• Email address;
• Date of birth;
• Gender, where required;
• Profile photograph;
• Current and permanent address;
• Emergency contact;
• Signature or declaration;
• Account and application ID; and
• Authorised communication records.

1.2 Identity and compliance documents

We may collect:

• Aadhaar or another legally permitted identity document;
• PAN;
• Driving licence;
• Address proof;
• Police or background-verification document, where lawful;
• Vehicle registration certificate;
• Vehicle insurance;
• Pollution certificate;
• Vehicle permit, where applicable;
• Vehicle photographs; and
• Other documents required by law or operational policy.

MealVersity will not require a document that is unnecessary for Rider registration, safety, payment or legal compliance.

1.3 Vehicle information

We may collect:

• Vehicle type;
• Registration number;
• Make and model;
• Vehicle colour;
• Fuel or power type;
• Registration validity;
• Insurance status;
• Pollution-certificate status;
• Ownership or authorised-use information; and
• Vehicle photographs.

1.4 Bank and financial information

We may collect:

• Bank account-holder name;
• Bank account number;
• IFSC code;
• Bank and branch details;
• Cancelled cheque or bank proof;
• Payout and settlement history;
• Wallet balance;
• COD collection and deposit records;
• Incentive and bonus records;
• Fines and deductions;
• Tax and statutory deductions;
• Payment references; and
• Financial disputes.

MealVersity does not require your UPI PIN, card PIN or internet-banking password.

1.5 Location information

MealVersity may collect:

• Current location;
• Precise latitude and longitude;
• Location timestamps;
• Movement during an active delivery;
• Pickup and delivery routes;
• Restaurant arrival;
• Customer-location arrival;
• Return-to-Restaurant route;
• Distance travelled;
• Location-permission status;
• GPS accuracy; and
• Location interruptions during an active order.

Location may be collected while:

• You are online and available for orders;
• You are considering or handling an active delivery;
• You are returning an order;
• A delivery remains operationally open; or
• An emergency or safety feature is active.

Background location must not be collected when it is unnecessary for an active, online or safety-related purpose.

1.6 Delivery and operational information

We may collect:

• Delivery offers;
• Accepted, rejected and expired offers;
• Pickup and delivery orders;
• Order-status updates;
• Restaurant arrival;
• Pickup confirmation;
• Customer arrival;
• Delivery completion;
• Contact attempts;
• Customer refusal reports;
• Failed-delivery reasons;
• Return and handover records;
• Waiting time;
• Delivery proof;
• Payment collection status; and
• Operational notes.

1.7 Customer and Restaurant communications

We may process:

• Masked or authorised call records;
• Call-attempt timestamps;
• Support messages;
• Delivery instructions;
• Customer or Restaurant complaints;
• Rider explanations;
• Dispute messages; and
• Communication metadata.

MealVersity should not record the content of a telephone call unless lawful notice and required consent are provided.

1.8 Device and technical information

We may collect:

• Device type and name;
• Operating system;
• App version;
• Push-notification token;
• Device or installation identifier;
• IP address;
• Login and session information;
• Network status;
• Location-permission status;
• Device security signals;
• Application logs;
• Crash and diagnostic information; and
• Suspected app manipulation or location spoofing.

1.9 Safety and incident information

We may collect:

• Accident reports;
• Breakdown reports;
• Emergency-support requests;
• Photographs or videos;
• Medical information voluntarily supplied for an accident claim;
• Police or insurance reports;
• Harassment or violence complaints;
• Food-damage or tampering reports; and
• Investigation outcomes.

Medical and safety information will be restricted to authorised purposes and personnel.

1.10 Performance and derived information

MealVersity may calculate:

• Offer-acceptance rate;
• Accepted-order completion rate;
• Pickup time;
• Delivery time;
• Waiting time;
• Distance;
• On-time performance;
• Customer ratings;
• Restaurant ratings;
• Complaint rate;
• COD reconciliation status;
• Return completion;
• Location-compliance indicators;
• Safety incidents; and
• Fraud or operational-risk indicators.

Automated indicators should not be the sole basis for imposing a financial penalty or terminating an account without appropriate review.

2. How We Use Rider Information

We may use Rider information to:

1. Register and authenticate the Rider account.
2. Verify mobile number and email through OTP.
3. Verify identity, age, driving licence, vehicle, bank and compliance documents.
4. Conduct lawful background or safety checks.
5. Detect duplicate or fraudulent accounts.
6. Approve, reject or request correction of an application.
7. Assign the Rider to an active service zone.
8. Show delivery opportunities.
9. Calculate distance, ETA and expected payout.
10. Coordinate Restaurant pickup and customer delivery.
11. Provide live order tracking.
12. Verify arrival, pickup, delivery, refusal and return.
13. Coordinate COD collection and reconciliation.
14. Calculate Rider earnings, incentives, bonuses, fines and adjustments.
15. Transfer payouts to the approved bank account.
16. Provide support and safety assistance.
17. Investigate customer, Restaurant and Rider disputes.
18. Detect account sharing, theft, payment abuse and location manipulation.
19. Monitor service quality and safety.
20. Send delivery, payment, security and account notifications.
21. Administer insurance or accident-support programmes, where available.
22. Comply with legal, tax, transport and regulatory requirements.
23. Establish, exercise or defend legal claims.
24. Improve Rider App reliability and operations.

3. Location Collection and Background Tracking

Location is essential when the Rider is online or handling an active order.

MealVersity may use location to:

• Identify nearby delivery opportunities;
• Assign orders;
• Calculate payout and distance;
• Navigate to the Restaurant and customer;
• Show ETA;
• Display live tracking to the customer;
• Confirm Restaurant arrival;
• Confirm customer-location arrival;
• Verify waiting time and contact attempts;
• Verify returned orders;
• Protect Rider and customer safety;
• Detect false delivery reports; and
• Investigate disputes.

The Rider may disable location permission through device settings, but this may prevent online availability, order assignment or active-delivery completion.

MealVersity must not use precise Rider location for unrelated purposes after the Rider is offline and no delivery or safety event remains active.

4. Information Displayed to Customers

During an active delivery, the customer may receive limited Rider information such as:

• First name or approved display name;
• Profile photograph;
• Vehicle type;
• Vehicle registration information where appropriate;
• Rating;
• Approximate or live delivery location;
• Delivery status;
• Estimated arrival; and
• Masked or authorised contact facility.

Private identity documents, bank information and residential address will not be displayed to customers.

5. Information Shared with Restaurants

For an assigned delivery, the Restaurant may receive:

• Rider name;
• Profile photograph;
• Vehicle information where appropriate;
• Pickup status;
• Estimated arrival;
• Order reference;
• Contact facility; and
• Return or handover status.

Restaurants must not use Rider information for unrelated marketing or personal contact.

6. Information Shared with Service Providers

MealVersity may use third-party providers for:

• Bank payouts and payment processing;
• SMS and OTP delivery;
• Email delivery;
• Firebase push notifications;
• Mapbox maps, routing and navigation;
• Cloud hosting and databases;
• S3-compatible document and media storage;
• Identity or document verification;
• Background verification;
• Insurance or accident support;
• Security and fraud detection;
• Analytics and diagnostics; and
• Support operations.

Each provider should receive only the information required to perform its authorised service.

7. Information Shared with Authorities

MealVersity may share information with:

• Transport authorities;
• Police or law-enforcement agencies;
• Courts and tribunals;
• Tax authorities;
• Insurance providers;
• Government departments;
• Food-safety authorities;
• Social-security or welfare authorities, where applicable; and
• Other legally authorised recipients.

Disclosure will be made where required by law, valid legal process, accident investigation, safety needs or protection of legal rights.

8. Identity and Document Verification

MealVersity may verify submitted information by:

• Comparing information across applications;
• Contacting the applicant;
• Reviewing original or uploaded documents;
• Checking document validity;
• Consulting authorised verification providers;
• Conducting physical or video verification; and
• Requesting updated documents.

The Rider must not submit another person's personal information without lawful authority.

9. Photograph and Face Verification

MealVersity may collect profile photographs or selfies for identity and account-security verification.

If facial recognition or biometric-template processing is introduced:

1. The Rider must receive a separate clear notice.
2. The exact purpose and retention period must be disclosed.
3. Legally required consent must be obtained.
4. The verification provider must be identified.
5. The Rider must receive an appropriate alternative or review process where required.
6. Biometric templates must not be used for unrelated advertising or profiling.

A standard photograph must not be described as biometric processing unless biometric analysis is actually performed.

10. Duplicate Account and Fraud Prevention

MealVersity may compare:

• Mobile number;
• Email;
• PAN;
• Identity document;
• Driving licence;
• Bank account;
• Vehicle number;
• Device;
• Location patterns; and
• Previous account history

to detect duplicate accounts, account sharing, identity fraud, COD misuse and incentive manipulation.

A flagged record should receive appropriate human review before permanent termination or a financial penalty.

11. Rider Performance Information

Performance information may be used for:

• Operational feedback;
• Training;
• Incentive eligibility;
• Safety review;
• Order assignment;
• Account review; and
• Dispute resolution.

MealVersity must reasonably distinguish Rider responsibility from:

• Restaurant delay;
• Customer unavailability;
• Customer refusal;
• Platform failure;
• Traffic;
• Severe weather;
• GPS failure; or
• Another cause outside the Rider's control.

The Rider may request correction of materially inaccurate performance information.

12. Automated Decisions

MealVersity may use automated systems to assist with:

• Delivery assignment;
• Route and distance calculation;
• Fraud detection;
• Duplicate-account detection;
• COD-risk review;
• Performance alerts; and
• Safety monitoring.

Automated systems may assist but should not independently make a final decision involving:

• Permanent account termination;
• Significant financial penalty;
• Serious misconduct finding; or
• Fraud finding

without appropriate human review and an appeal route.

13. Consent and Rider Choices

Where processing is based on consent:

1. The purpose will be explained before or when information is collected.
2. Consent will require an affirmative action.
3. Optional marketing consent will be separate from delivery-service processing.
4. Consent may be withdrawn through available settings or Rider Support.
5. Withdrawal will not affect lawful processing already completed.

Some information is necessary for identity verification, location-based assignment, delivery completion, COD reconciliation, payout, safety or legal compliance.

Refusal to provide necessary information may prevent approval or use of the relevant service.

14. Communications

MealVersity may send essential communications concerning:

• OTP;
• Application status;
• Delivery opportunities;
• Active orders;
• Customer or Restaurant contact;
• COD;
• Payout;
• Incentive;
• Document expiry;
• Safety;
• Account security;
• Suspension;
• App updates; and
• Support.

Optional promotional or educational communications may be separately controlled where required.

Opting out of marketing will not stop essential operational or security messages.

15. Data Accuracy

The Rider must keep information current, including:

• Phone number;
• Email;
• Address;
• Driving licence;
• Vehicle documents;
• Insurance;
• Pollution certificate;
• Bank details; and
• Emergency contact.

Certain verified fields may require additional verification before they can be changed.

16. Data Retention

MealVersity retains Rider information only for as long as required for the stated purpose or applicable law.

Different retention periods may apply to:

• Application and OTP records;
• Identity and compliance documents;
• Approved or rejected applications;
• Bank and payout records;
• Delivery and location records;
• COD records;
• Tax records;
• Customer and Restaurant complaints;
• Safety and accident records;
• Fines and disputes;
• Fraud and duplicate-account records;
• Device and security logs; and
• Suspension or termination records.

Information may be retained longer where required for:

• Tax and accounting;
• Payment or COD disputes;
• Accident or insurance claims;
• Fraud prevention;
• Legal proceedings;
• Government investigations; or
• Another legal obligation.

When no longer required, information will be deleted or irreversibly anonymised, subject to backups and legal holds.

17. Rejected Applications

For a rejected application, MealVersity may retain limited information necessary to:

• Record the decision and reason;
• Permit correction or reapplication;
• Detect duplicate or fraudulent applications;
• Handle disputes; and
• Comply with legal obligations.

Rejected-application data will not be retained indefinitely without a documented purpose.

18. Account Closure and Deletion

A Rider may request account closure through Rider Support.

After verifying the request, MealVersity may:

• Disable account access;
• Revoke active sessions;
• Remove notification tokens;
• Delete or anonymise information no longer required;
• Retain delivery, COD, payout, tax and compliance records where necessary;
• Retain information connected to unresolved complaints, accidents, fraud or legal claims; and
• Inform the Rider about the request outcome.

Account closure does not erase outstanding COD obligations, earned-payout records or legally required transaction records.

19. Rider Privacy Rights

Subject to applicable law, the Rider may request:

1. Information about personal data being processed.
2. Correction of inaccurate information.
3. Completion of incomplete information.
4. Updating of outdated information.
5. Erasure of information no longer required.
6. Withdrawal of consent where consent is the processing basis.
7. Information about categories of organisations with which personal data has been shared.
8. Grievance redressal.
9. Nomination of another person to exercise applicable rights in the event of death or incapacity, where legally available.

MealVersity may verify identity before processing a rights request.

Erasure may be restricted where retention is required for delivery, COD, tax, safety, fraud, insurance or legal purposes.

20. Customer Data Obligations

Customer information provided through the Rider App may be used only for the assigned delivery.

The Rider must not:

• Save customer phone numbers;
• Contact the customer after delivery;
• Use customer information for marketing;
• Share or publish customer information;
• Revisit the customer's address;
• Use the information for personal purposes; or
• Retain screenshots containing unnecessary customer data.

Violation may result in suspension, termination and legal action.

21. Data Security

MealVersity may use safeguards such as:

• Encryption during transmission;
• OTP and password authentication;
• Device and session controls;
• Role-based access;
• Secure document storage;
• Audit logs;
• Payment verification;
• Fraud monitoring;
• Backup and recovery; and
• Incident-response procedures.

The Rider must:

• Protect the registered device;
• Use a strong password;
• Keep OTP confidential;
• Use only the official Rider App;
• Avoid rooted or compromised devices where prohibited;
• Report device loss;
• Report suspicious login; and
• Remove access before giving the device to another person.

22. Personal-Data Breaches

If a personal-data breach occurs, MealVersity will:

1. Investigate and contain the incident.
2. Assess the possible impact.
3. Take reasonable corrective measures.
4. Preserve required incident records.
5. Notify affected persons and authorities where legally required.
6. Provide available protective instructions.

The Rider must immediately report loss, unauthorised access or disclosure of customer or MealVersity data.

23. International Processing

Some technology providers may process information outside the Rider's state or outside India.

Where international processing occurs, MealVersity will apply safeguards and restrictions required by applicable Indian law.

24. Minimum Age

Delivery Partner accounts are available only to individuals aged 18 or above.

MealVersity does not knowingly approve a child as a Delivery Partner.

25. Changes to This Policy

MealVersity may update this Policy when services, technology or legal requirements change.

Material changes will be communicated through the Rider App, email, SMS or another appropriate channel.

Fresh consent will be obtained where legally required.

26. Contact and Grievance Officer

Company / Data Fiduciary: MealVersity Technologies Private Limited

Registered Address: 59 Uttar Sithi Road, Barasat, Kazipara, North 24 Parganas – 700125, West Bengal, India

Rider Privacy Email: business@mealversity.com

Rider Support Number: +91 8900099783

Rider Support Email: business@mealversity.com

Grievance Officer: Tarik Anowar

Designation: Founder, CEO & Director

Email: business@mealversity.com

Telephone: +91 8900099783

Postal Address: 59 Uttar Sithi Road, Barasat, Kazipara, North 24 Parganas – 700125, West Bengal, India

MealVersity will acknowledge and resolve privacy grievances within the period required by applicable law.

— End of Delivery Partner Privacy Policy —