Secure passenger links
Each public passenger link contains a booking-specific random token. It exposes only its associated booking and requires no passenger account.
Security
PaxWhere protects the Operations workspace while keeping the passenger journey simple and account-free. These safeguards describe the current product without making unsupported compliance claims.
Each public passenger link contains a booking-specific random token. It exposes only its associated booking and requires no passenger account.
Operations pages and write actions require authenticated, authorized company access. Authorization is enforced on the server for every request.
Bookings and events are read and changed only within the authenticated operator’s company boundary.
Passenger and operational events are appended to the booking timeline. Editing does not overwrite the historical event stream.
Removing a booking disables its passenger link and removes it from operational views while retaining the booking and event history in storage.
PaxWhere displays passenger-declared progress. It does not collect GPS coordinates or continuously track a passenger’s location.