Privacy Notice

FleetPrime Solutions Pvt. Ltd. operates JOR and determines why and how personal data is processed for the platform. This notice applies to website visitors, applicants, drivers, fleet-owner users, staff users and people who contact JOR.

• Account and contact data: name, mobile number, role, organisation and authentication records
• Driver onboarding data: profile, licence details, identity evidence, selfie and verification status
• Fleet and job data: vehicles, routes, pickup and destination, schedule, pay, messages and completion evidence
• Location data: availability location, active-trip updates and incident coordinates
• Payment data: amount, fee, tax, provider references, refunds, disputes and settlement status
• Device, security and usage data: IP address, session cookies, logs, browser and performance events
• Support and safety data: communications, ratings, incident reports and investigation records

• Create and secure accounts
• Assess pilot applications and verification evidence
• Match drivers to suitable jobs
• Coordinate trips, location visibility, support and safety
• Process and reconcile payments through authorised providers
• Prevent fraud, abuse and unauthorised access
• Comply with law, enforce terms and resolve disputes
• Measure and improve reliability with aggregated or appropriately protected data

Where consent is required, JOR should provide a clear notice and a specific choice before processing. Consent may be withdrawn as easily as it was given, subject to processing already completed and records JOR must lawfully retain. JOR may also process data for uses permitted by applicable Indian law.

• The assigned driver and authorised fleet-owner users for a relevant job
• Authorised JOR operations, support, finance and security personnel
• Contracted cloud, messaging, maps, identity, payment, analytics and support providers
• Professional advisers, auditors, insurers and authorities where legally required
• A successor entity in a lawful business transfer, subject to appropriate safeguards

JOR should use the least intrusive compliant verification method available and prefer masked or UIDAI-approved offline evidence. Aadhaar must not be treated as proof of citizenship or driving entitlement. Access to identity documents must be tightly restricted and logged.

Important: The present MVP allows document URLs and Aadhaar entry for testing. Real identity documents must not be onboarded until secure object storage, encryption, masking and provider controls are complete.

Location may be used for nearby matching, active-job visibility, incident response and dispute evidence. Role-based access and trip state should limit who can see precise location. Off-duty continuous tracking is not an intended purpose.

JOR will keep data only for the stated purpose and applicable legal, tax, safety, fraud, dispute and audit needs. Production retention periods must be documented by data category. When no purpose remains, data should be erased or irreversibly anonymised unless retention is legally required.

• Encryption in transit and appropriate encryption at rest
• Role-based access and privileged-action logging
• Secure secrets, backups and recovery testing
• Vendor due diligence and restricted data access
• Incident detection, response and legally required notifications

• Receive clear information about processing
• Request access to a summary of personal data and sharing
• Ask for correction, completion or updating
• Request erasure where applicable
• Withdraw consent
• Use the grievance process and nominate another person as permitted by law

JOR is intended for adults and commercial organisations. JOR does not knowingly onboard a person under 18 as a commercial driver or fleet-owner account controller.

Some providers may process data outside the user state or outside India where law permits. JOR will assess provider location, contracts and applicable government restrictions before production use.

Before paid public operations, JOR must publish an accessible grievance channel, responsible officer details and response process. Users may then escalate unresolved privacy matters to the competent authority under applicable law.

Important: The designated grievance officer and monitored contact details are not yet published. This must be completed before the controlled paid pilot.

JOR will publish the effective date and provide appropriate notice before material changes take effect. Prior versions should be retained for auditability.