Policy draft · not approved for launch
Privacy begins with clear boundaries.
What this test build collects today, and what must be decided before a final privacy notice.
1. What this test build collects
Account email and password (handled by Supabase Auth; passwords are never stored in our tables), the carrier application, trip records, expenses and documents you upload in the portal. All of it runs on a local test database with test data.
2. Who can see it
Each carrier sees only its own records, enforced in the database. Dispatchers see only the carriers assigned to them; billing staff and admins must use two-step sign-in. Documents are kept in private storage and opened with links that expire within minutes.
3. What we don’t collect
No analytics or advertising trackers, no payment card data, no load-board passwords, and no SSN or bank details in public forms.
4. Maps and outside services
The staff map loads map tiles from OpenFreeMap. No driver names, documents or financial records are sent to map or weather services.
5. Before launch
The legal business identity and contact, the full list of providers, retention and deletion rules, and how you can request your data must be settled and reviewed before a final privacy notice is published.