Driver, vehicle, and report data support the daily verification flow.
Privacy
Privacy for a practical driver workflow.
VerifGo is designed to collect only the information needed to help a driver complete, store, and present a daily vehicle verification record.
Driver dataVehicle contextNo resale promise
The product is not built around selling driver verification records.
Deletion, export, and correction processes need approved support paths before wider pilot.
What the app may collect
- Account identity and driver profile details such as name, email-based sign-in, preferred language, and permit number when entered.
- Primary vehicle details such as plate, optional VIN, optional accessory number, and taxi/equipment flags.
- Daily verification records such as inspection date and time, odometer, checklist results, dashboard indicator details, defect notes, report reference, and submitted timestamps.
- Local draft, reminder, and privacy-minimized diagnostic data needed to keep the founder-test workflow reliable.
How it is used
Data is used to power the app workflow: preparing the daily check, saving submitted reports, showing report history, and supporting driver reminders.
The product is not built around advertising or resale of driver records.
Current data lifecycle
Submitted reports are intended to remain immutable. Deletion, export, and correction processes still require approved support procedures before any wider pilot.
What stays limited
- The public website does not require a driver to complete daily reports.
- VerifGo does not sell driver verification data.
- VerifGo does not collect tax or income records, Uber or Lyft API data, payment card data, fleet analytics, or AI analysis in the MVP.
- Pilot-stage access is kept narrow while the release gates are completed.
Pilot-stage posture
VerifGo is still moving through readiness work before a wider pilot. Privacy language, support procedures, and legal review must be approved before controlled driver testing.