Trust and safety
Controls that hold up when something goes wrong
DriveVia is designed on the assumption that a dispute will eventually happen, and that the record has to answer it without anyone's memory being involved.
Who is allowed on the network
- Access is invitation-only. There is no open self-service sign-up.
- Every organization submits an application that a DriveVia reviewer approves or rejects.
- Company drivers are individually approved, not just added by their company.
- Compliance records have expiry dates, and lapsed records remove eligibility for new work.
Evidence requirements
- A defined photo set is required at pickup and again at delivery.
- Odometer and fuel or charge level are recorded at both ends.
- Pre-existing damage must be declared at pickup, before the vehicle moves.
- Steps are blocked in software until the required evidence exists — this is not a reminder, it is a gate.
Data isolation
- Every record belongs to exactly one organization and is filtered by that ownership at the database level.
- Fleets cannot see another fleet's vehicles, requests, rates or history.
- Providers see only the requests offered to them and the missions they hold.
- Sensitive identifiers are never read directly by application code; they are retrieved through audited, access-logged routines.
Money and audit
- Funding, settlement and payout are separate, inspectable states.
- Every settlement posts to a double-entry ledger that must balance.
- Payout release is a deliberate operational action after the verification hold, not an automatic transfer at delivery.
- Status changes on missions, applications and payouts are written to an audit trail.
Incidents and damage
Incidents are reported inside the mission and compared against the pickup evidence set. Resolution follows the published Incident and Damage Policy. DriveVia is a technology platform and is not the carrier of the vehicle.