How information is collected

Information is provided when a driver creates or uses an account, enters driver or vehicle details, prepares or submits a daily report, or contacts support. The public website does not ask visitors to complete a vehicle report.

Website and app infrastructure may also create limited operational and security logs needed to keep the service reliable and investigate problems.

Information the product may handle

The current product does not collect GPS tracking, payment-card, tax or income, Uber or Lyft API, AI-analysis, or fleet-analytics data.

Account and profile information, including email-based sign-in, name, preferred language, and a permit number when entered.
Primary vehicle information, including the plate and optional VIN, accessory number, or equipment indicators.
Daily report information, including the date, odometer, checklist results, dashboard indicators, defect notes, report reference, and submitted timestamp.
A verified, locked report-delivery email and limited PDF-delivery status records when secure report email is enabled.
Referral-program information, including a personal code, referrer and referred-account identifiers, claim and qualification status, qualifying report reference, and non-cash points entries.
Device-local drafts, reminders, and privacy-minimized diagnostics used to support the daily workflow.

Why information is used

Information supports account access, vehicle setup, the guided daily check, submitted-report history, driver-requested PDF delivery to the verified account email, reminders, referral attribution and abuse prevention, support, security, and product reliability.

A referrer receives aggregate pending and qualified counts plus points. VerifGo does not show the invited driver’s email, identity, vehicle, or reports to the referrer.

VerifGo does not sell driver verification records or use them for behavioural advertising.

Service providers and disclosure

VerifGo relies on service providers for authentication, database, hosting, app infrastructure, and—when secure report email is enabled—delivery of a driver-requested PDF to the verified account email. These providers may process information outside Quebec under their own security and contractual controls.

Records are not automatically sent to taxi companies, Uber, Lyft, police, or another public authority. Information may be disclosed when required by law or when necessary to protect the service and its users.

How information is safeguarded

VerifGo uses account authentication, driver-owned access rules, server-side report timestamps, integrity data, submitted-record immutability, a server-resolved verified email destination, delivery rate limits, and minimized diagnostics. Access is limited according to the product role and operational need.

No online service can guarantee perfect security. See the Security page for the current controls and reporting path.

Retention and submitted reports

During controlled testing, information is kept only as long as needed for product testing, support, security, and readiness. A final public retention schedule has not yet been approved.

A submitted report is designed to remain immutable. A correction request is handled through support without silently rewriting the historical submitted record.

Your choices and requests

You may request access to, correction of, or export of your information through the privacy contact. When the in-app deletion service is enabled for a build, an authenticated driver can initiate deletion of the entire account directly in App Settings without sending an email.

VerifGo may need to verify identity before completing a request and will confirm completion or explain when a submitted record must be retained to meet a legal obligation.

You may also contact the Commission d’accès à l’information du Québec about privacy rights or concerns.