Privacy for a practical driver workflow.

What the app may collect

• Account details needed to identify the driver in the app.
• Driver profile and vehicle information needed for the daily verification record.
• Submitted report facts, including inspection date, item status, defect notes, and report history.
• Reminder preferences and product diagnostics needed to keep the 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.

What stays limited

• The public website does not require a driver to complete daily reports.
• VerifGo does not sell driver verification data.
• 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, operational procedures, and owner review will continue to tighten as the product moves toward driver use.