MMILESAAShare the journey

Privacy Policy

This policy describes the limited personal data MILESAA uses to verify customers, fulfil shared-taxi bookings, verify payments and handle admin-assisted cancellations.

Who this policy covers

This policy applies when a person browses MILESAA, verifies a phone number, creates or pays for a booking, travels as a passenger, contacts support, or receives a manual refund.

MILESAA is designed for use in India. The person completing a booking must be at least 18 years old. An adult may provide necessary passenger details for children or other travellers included in the same booking and must be authorised to do so.

Data we collect

  • Lead passenger details: name, age, gender, Indian mobile number, optional email and special requirements; passenger count and cab preference, including a women-only preference where selected. Individual details for every passenger are not collected in this booking form.
  • Booking details: route, date, time, passenger count, fare, booking status and assigned trip or cab references.
  • Verification and security details: OTP hash, expiry and attempt information. MILESAA does not store the plain OTP.
  • Payment records: Razorpay order ID, payment ID, verification time and payment status. Payment credentials are entered in Razorpay Checkout, not stored in MILESAA's Booking record.
  • Cancellation and refund records: reason, time, administrator, restored-seat record, recipient UPI ID, full refund amount and UPI transaction reference or UTR.
  • Technical records reasonably needed to secure and operate the API, diagnose errors and prevent misuse.

Why we use the data

  • To show available trips and create the requested booking.
  • To verify the booked phone number and prevent OTP abuse.
  • To create and verify payments and prevent double seat deduction.
  • To communicate booking, schedule, cancellation and refund information.
  • To give the assigned operator or driver the information needed to fulfil the journey.
  • To provide support, investigate disputes, reconcile payments and maintain security.
  • To comply with applicable legal, tax, accounting and regulatory obligations.

When data is shared

Phone verification sends the booked Indian mobile number and a verification code through Meta WhatsApp Business services. MILESAA shares only the information reasonably needed for the relevant purpose. This may include the assigned taxi operator or driver, Razorpay and its payment partners, hosting and database providers, professional advisers, and authorities where disclosure is lawfully required.

MILESAA does not sell passenger names, phone numbers, UPI IDs or booking histories for unrelated advertising.

Payments and manual refunds

Razorpay Checkout processes online payment credentials under Razorpay's own terms and privacy practices. MILESAA receives the payment references needed for backend verification.

A manual UPI refund is performed outside Razorpay after the customer confirms an alternate UPI ID. That UPI ID and transaction reference are retained as a protected admin-visible audit record.

Retention

MILESAA keeps personal data only for as long as reasonably necessary for booking fulfilment, support, fraud prevention, payment and refund reconciliation, legal claims, and applicable tax, accounting or regulatory requirements. Data that is no longer required should be deleted or anonymised using a controlled process.

Security

  • Admin operations require a verified, revocable admin session.
  • OTP values and Razorpay signatures are not returned by normal booking APIs.
  • Sensitive writes are performed by protected backend routes rather than by changing frontend labels.
  • Reasonable safeguards are used, but no internet service can promise absolute security.

Your choices and rights

Subject to applicable law and necessary identity verification, a customer may ask what personal data MILESAA processes, request correction of inaccurate data, request erasure where retention is no longer necessary, withdraw consent where consent is the applicable basis, and raise a grievance.

Some booking, payment, refund or security records may still need to be retained where required for an existing journey, legal obligation, fraud prevention or dispute.

Third-party services

A third-party service linked or opened from MILESAA may apply its own privacy policy. Customers should review the relevant provider's policy, particularly when completing payment through Razorpay.

Questions, grievances and changes

Use Contact MILESAA support below for privacy questions or to raise a grievance. MILESAA may update this policy when its features, data use or legal obligations change, and will display the updated version and effective date.

Contact MILESAA support

Keep a copy of your booking ID and payment or refund reference for support.