Using RideFlag’s tool requires no handling of the smartphone by the driver at any time as verification can occur while stationed in the driveway/parking lot or completed by the passenger(s) if already in the lane. The driver/user will always be automatically verified. In the case of a reverification audit requirement at the end of the trip, the passenger(s) in the vehicle can complete this process.
This occurrence would be a matter of policy decision. In this situation, users can report a missing credit at the end of the trip in-app. It will then be reviewed, and if an error occurred, it would be corrected.
Having a dummy or any images with attempts to manipulate the camera would not work; the camera would detect that the facial signature is not real and thus not allow verification. Our camera detection has multiple verification image strategies to differentiate between real faces and depictions of real faces.
The camera verification tool works with masks. If a user is wearing a mask, they can still be HOV verified.
Will occupant/user images remain private?
No information or images are stored in the cloud. When a facial verification image is taken, there are no photographs sent to the cloud. All images and information remain on the host’s smartphone cache temporarily but are automatically deleted at the end of the trip.
The transportation agency/tolling operators own all data, and users are registered and managed by RideFlag.