Verified Driver Identity
Driver access depends on an approved account, eligible vehicle, current inspection and active Center Hub credential. The backend performs the final eligibility check.
Guardian connects identity, trip context, location privacy and support workflows so passengers, drivers and operations can respond with clearer information.
Important
LaBar never claims emergency services were contacted unless a real emergency integration confirms it.
Driver access depends on an approved account, eligible vehicle, current inspection and active Center Hub credential. The backend performs the final eligibility check.
During an eligible ride, passengers can request a temporary, expiring share link. The public view is limited to the trip information permitted by the backend.
Authorized staff review applicant and vehicle evidence independently. A mobile upload, OCR result or capture never approves a driver by itself.
Driver location is shared with the relevant passenger only while operationally required. The server remains authoritative for ride and location state.
An SOS request creates a safety event linked to the ride and available device location, then queues the configured operations notification workflow.
After a completed ride, passengers can submit a 1–5 score in the Passenger app. Those records update the driver score and can be read by authorized staff. Public pages do not invent review totals.
Authorized operations staff can review safety events and follow the recorded support workflow. Access and actions are subject to backend permissions and audit controls.
A ride that respects your day
Plan a route on the web with SMS OTP, book LaBar Mini or Oway when live, then continue in the Passenger app.