01
What the controls protect
Security controls cover account, profile, vehicle, draft, and submitted-report information used by the current product.
02
Core product controls
- Row-level access rules separate driver-owned records.
- Submitted timestamps are generated by the server and submitted reports include integrity data.
- Submitted reports are designed to be immutable and duplicate submission is prevented.
- Public app and website code uses public client credentials only; secret administrative credentials stay server-side.
- Device diagnostics are minimized and avoid unnecessary driver information.
03
What drivers can do
- Protect the device and email account used to access VerifGo.
- Enter accurate information and review every report before submission.
- Report a suspected security or privacy issue by email without sending passwords, access codes, or secret keys.
04
Limits and incident response
No online service can promise perfect security. VerifGo reviews reported issues and is designed to assess, contain, document, and address privacy incidents when required.
These controls do not mean regulator approval, legal protection, guaranteed report acceptance, or permission to operate a vehicle.