DEVELOPMENT PREVIEW
Privacy notice
Draft for review before public launch. Updated September 27, 2026.
What this workspace stores
Accounts sign in through Supabase using Google or an email address and password. Google sign-in shares basic account identity, including name, email and profile information, with Supabase. Operational records may include driver names, contact emails, truck identifiers, manually entered locations, availability, load details and trip updates. Audit records identify who changed an operational record.
How information is used
Information supports account access, internal trip planning, driver coordination and security. Financial data is restricted to the owner. Drivers can access their own assigned operational records. The preview contains clearly labeled fictional examples.
Service providers and separation
Supabase processes authentication and database records; the hosting provider serves the application. This workspace uses dedicated LoadVerge database tables and access policies in a shared Supabase project. Company, sample and login pages are publicly reachable. Real operational data requires a verified Supabase account and an activated LoadVerge role.
Cookies and tracking
Essential cookies maintain sign-in and navigation preferences. This version does not include advertising trackers, analytics cookies, background location tracking, voice recording or automated broker calls.
Sensitive information and retention
Do not enter Social Security numbers, CDL images, medical records, banking details or other sensitive documents in free-text fields. Before live operations, the company must establish retention schedules, deletion procedures, provider agreements and an approved privacy contact.
Privacy requests
During this pre-launch stage, invited users should contact the owner who provided access. A verified public privacy contact and applicable request procedures must be published before customer or driver onboarding.