Security at FLEETBAQ

Your loads, drivers, invoices and documents run your business. Here is how we protect them.

Encrypted everywhere

• In transit: every connection uses HTTPS (TLS); HSTS forces browsers to never connect without it.
• At rest: data is stored in Supabase (Postgres on AWS), encrypted at rest with AES-256.
• Passwords: never stored; sign-in handled by Supabase Auth with salted one-way hashes.

Your company only sees your company

Each carrier's data is kept separate; drivers see only their own loads, documents and pay.

Connected accounts

• Gmail: mail is read live and not stored; only an encrypted token is kept; disconnect any time.
• ELD, GPS, fuel and factoring: you connect with your own account at each provider; FLEETBAQ reads only what you authorize; disconnect any time.
• Background checks: run through Checkr, an FCRA-compliant consumer reporting agency; reports stay in Checkr's system.

Infrastructure

• Website: Netlify.
• Database and sign-in: Supabase (AWS).
• Email: Google Workspace (SPF, DKIM, DMARC).

Report a security issue

Email contact@fleetbaq.com, subject “Security”. We reply within 2 business days. Don't access other customers' data or disrupt the service while testing. Machine-readable contact: /.well-known/security.txt