Skip to main content

Trust and onboarding

Verification is a workflow, not a marketing badge

JOR collects driver identity and licence evidence for review. Production verification against authorised sources will only be activated through compliant providers and consent flows.

Provider integration pending

JOR must not claim that a driver is Aadhaar-verified or government-database-verified until the relevant consented provider check has completed successfully.

Evidence requested

  • Name, mobile number and profile information
  • Driving licence number, category, validity and document image
  • Identity evidence through an approved method
  • Selfie or liveness evidence where legally permitted and necessary

Aadhaar handling

JOR should prefer UIDAI-approved offline or masked methods and collect the minimum information needed. Aadhaar is not proof of citizenship, driving entitlement, employment suitability or criminal history.

Important: Raw Aadhaar numbers and document images require strict access controls, masking, retention limits and a documented lawful purpose. The current MVP input flow needs production hardening before real onboarding.

Review outcomes

  • Pending while evidence or provider checks are incomplete
  • Approved for the categories actually reviewed
  • Rejected or returned for correction with a clear reason
  • Suspended when documents expire or credible safety concerns arise

Fleet-owner responsibility

Fleet owners must still verify vehicle-specific eligibility, endorsements, fitness, insurance and any legal or contractual requirement before permitting a driver to operate a vehicle.

Correction and appeal

Drivers should be able to correct inaccurate details and ask for human review of an adverse verification decision through JOR support.

Official references

These links are provided for transparency. JOR policies must also be reviewed by qualified Indian counsel before paid public operations.