Security Overview
A plain-English overview of the controls used to protect MV Fleet Compliance customer information.
Security architecture
MV Fleet Compliance uses a layered design rather than relying on a single password or browser check. Operator accounts authenticate through Supabase; company access is linked to authenticated membership; live customer records are protected by database Row Level Security; private evidence is stored outside public file URLs; and privileged server secrets are kept outside public web files.
Driver separation
The driver app receives a reduced driver-safe view rather than the complete company database. Driver submissions are merged server-side into the latest customer record so a driver device cannot simply replace the whole operator database.
Operational safeguards
- HTTPS/TLS.
- Individual user authentication and role checks.
- Private document storage with authorised/signed access.
- Revision checks to detect conflicting stale saves.
- Audit/history records.
- Protected cron/API secrets outside public web folders.
- Company-specific push subscriptions.
- Backups according to infrastructure/account configuration.
Shared responsibility
Customers must still protect devices and credentials, remove leavers, use appropriate access roles, verify notification recipients and maintain operational oversight. No internet-connected service can guarantee zero risk or uninterrupted availability.
Report a concern
Suspected security or privacy issues can be reported to . Data-protection complaints can also use our complaint form.