Drivers Hub handles drivers' personal and compliance information. Here's exactly how we keep it safe โ and what we deliberately choose not to keep.
Every connection to Drivers Hub is served over HTTPS/TLS and protected at the edge by Cloudflare, with HSTS enforced so browsers never fall back to an insecure connection.
Passwords are hashed with scrypt (a slow, memory-hard algorithm) and salted per user. We can never see or recover your password โ only verify it.
Accounts can enable app-based two-factor authentication (Google Authenticator / TOTP). The owner admin console is protected by 2FA as standard.
Compliance documents you upload โ licence, CPC, DBS, right-to-work, proof of address โ are used to verify you and then permanently deleted as soon as they're reviewed. We keep the approval result, not the file.
Every account can only ever see and change its own data. Driver records, bank details and private messages are gated to the person they belong to, or the agency that legitimately works with them.
Login and sign-up are rate-limited, sessions are server-side and HttpOnly, and the platform sends a strict set of security headers (CSP, X-Frame-Options, no-sniff) on every response.
We follow data minimisation: we only keep what's needed to run the service.
We welcome responsible disclosure. Email us and we'll respond quickly.
Report a vulnerability