Privacy Policy

PRIVACY POLICY & DATA NOTICE

Privacy policy for Milbaz website and Driver and user apps 

This document forms an itemized, clear, and unambiguous notice explaining the specific personal data parameters Milbaz collects, the lawful basis of processing, and your rights as a Data Principal. By clicking "Accept", performing an in-app registration, or utilizing our services, you carry out an intentional affirmative action providing unconditional consent to all processing rules herein.

LANGUAGES / भाषाएं / نابزᑒᓝᒄᒇںینابز) SECTION 5(3)): English is configured as the default automated platform language. In strict accordance with regional translation mandates under Indian law, Data Principals can toggle this document and localized user notices into Urdu, Hindi, Tamil, or any other regional language integrated via our localized translation interfaces.

Effective Date: May 20, 2026

Name: Milbaz

Office address : Bemina, Srinagar, Jammu & Kashmir - 190018

Grievance Desk: Mr. Younis Mehdi

Hotline: +919103150903

Email: info@milbaz.com

1. Comprehensive Personal Data Processing Inventory To operate a compliant digital matchmaking marketplace for passengers, commercial riders, and logistics shippers, Milbaz limits data capture to the following itemized matrix:

DATA CLASS TYPE

COLLECTED DATA FIELDS (MANDATORY & NON-

MANDATORY)

LAWFUL PROCESSING

PURPOSE BASIS

Passengers & Users Mandatory: Legal First Name, Last Name, Valid Mobile

Phone Number, Active Foreground Telemetry

Coordinates when processing transit matching requests.

Non-Mandatory/Optional: Valid Email ID, Custom

Location Aliases (e.g., Saved Home/Work Coordinates),

User Profile Image, Identification Metadata numbers

(Passport, Voter ID, or Driving License parameters if voluntarily submitted).

Contractual Execution:

Authentication, algorithmic ride-

allocation, invoice routing, fraud-

mitigation, and in-app

messaging.

Independent Drivers Mandatory: Full Legal First and Last Name, Verifiable

Email ID, Active Contact Number, High-Resolution

Profile Face Snapshot, Physical Document Photographs

and Alphanumeric Numbers of Government-issued

Identity instruments: Driving License (DL), Permanent

Account Number (PAN) Card, and Aadhaar Card. Full

Bank Routing/Settlement Information.

Statutory Compliance & KYC:

Obligatory background

verification, authentication

audits, tax-withholding

compliance, and electronic

weekly bank withdrawal routing.

Registered Vehicles Mandatory: Commercial Asset Model, Manufacturer/

Brand, Vehicle Category (Cab, Taxi, Auto Rickshaw, or

2-Wheeler), License Number Plate Alphanumerics,

Registration Certificate (RC) Photographic Images, Valid

Third-Party Commercial Insurance Copies, Fuel Source

Class, and Document Expiry Dates.

Public Safety Mandates:

Validation of regulatory vehicle

fitness, transport aggregator

compliance, and active statutory

third-party road insurance

monitoring.

2. Telemetry Coordinates, Geolocation, and Background Asset Tracking

2.1 Passenger Geolocation Controls Precise coordinate telemetry is captured only when the user interface is active in the foreground or executing a requested transaction. Background coordinate processing is strictly disabled for passengers, except when a user consciously hits the Red SOS Emergency Trigger Asset on the right side of the active trip screen. Upon activation, live background coordinate maps are instantly streamed to internal safety desks and emergency servers. Shippers and passengers retain full authorization to split and share active transit telemetry strings directly with external third parties or family members.

2.2 Driver Telemetry Obligations

Precise background and foreground geolocation capture runs continuously if and only if the Driver App is toggled to "Online Mode". This background data tracking is required to handle route availability matching, calculate distance charges, and log travel safety. The moment a driver toggles the app interface to "Offline Mode", all active background location tracking terminates instantly.

3. AWS Biometric Processing & Manual Data Verifications

3.1 Automated Profile Audits (Amazon Web Services Rekognition API) To enforce profile integrity and prevent account renting or vehicle swapping, Milbaz processes facial signatures. During initial signup and at random intervals during active operations, drivers are forced to provide a live face selfie. This asset is transiently securely processed via the AWS Rekognition API to cross-examine facial metrics against the driver’s authorized government identification photograph. This biometric evaluation is executed to prevent identity impersonation across the network.

3.2 Manual Storage & Aadhaar Handling Rules Physical images of PAN Cards, Aadhaar Cards, Registration Certificates, and Licenses are restricted and audited manually by the internal Milbaz verification desk. Aadhaar metrics are stored securely within our cPanel database infrastructure located inside the physical borders of India, following UIDAI directives and national data protection benchmarks.

4. Hard Restrictions on Account Deletion & Security Data Escrow

4.1 Explicit Account Erasure Pre-Requisites In strict deviation from generic open data platforms, Data Principals cannot delete their profile if they have outstanding digital wallet balances, negative overdraft balances, or active uncompleted trip assignments. Drivers must pay any outstanding administrative balance to the admin, or execute a clean final withdrawal of legitimate positive credits before the deletion interface unblocks. Passengers with positive wallet assets must exhaust their credits or contact the manual support desk at info@milbaz.com to clear the account before closure.

4.2 The 15-Day Safety Escrow Retention Window

Once a clean profile erasure request is initiated via the app settings or dispatched manually through https://milbaz.com/contact-us, all identifying records are removed from public operational matching servers. However, to fulfill public safety mandates, the entire data parcel is locked in an offline, encrypted security escrow archive for **exactly fifteen (15) days**. This 15-day hold period is strictly utilized to respond to law enforcement lookup warrants, check late-reported roadside accidents, or verify sudden passenger safety alerts. Following the 15- day duration, all personal metrics are permanently deleted from all server drives.