Private early access
Privacy Policy
This notice describes the public website at carrierhelm.com and the private early-access application at app.carrierhelm.com. CarrierHelm is the product name. Privacy questions and requests can be sent to carrierhelm.admin@gmail.com.
Updated October 26, 2026
1. Demo requests and information you provide
The form collects legal company name; operating name (optional); USDOT number (optional); MC number (optional); owner or contact name; business email; phone number; requested active driver seats; current active drivers; current active trucks; current dispatch or TMS system (optional); desired integrations (optional); and the free-text problem description (optional). Please do not include sensitive personal information in free text. We receive and store submissions in the website’s hosted database and send them through a protected connection to the application’s prospect-review queue. Authorized administrators use them to assess fit and respond to the request. Submitting does not create an operational account or purchase a subscription.
2. Accounts and Google Sign-In
Google Sign-In requests openid, email and profile to receive your name, email address, profile picture and account identifier for authentication, invitation matching and company access. Google Sign-In itself does not grant access to Gmail, Drive, Calendar or contacts. Separately configured carrier integrations may require their own permissions and process data for the requested feature. Account identity alone does not grant a company role or driver seat.
3. Carrier records and uploaded documents
Depending on the enabled workflow, a carrier may provide driver and staff contact details, qualification and employment records, customers and facility addresses, load and stop details, equipment identifiers, rates and financial records, BOL/POD, scale tickets and other evidence. Authorized office users and assigned drivers can access records according to their company role and workflow. Carrier-provided records are administered for that carrier; contact the carrier first about its operational records, or contact us for assistance.
4. Driver location and operational actions
The driver interface may request browser location permission during setup. That setup position is discarded. While an active load is open, the interface can watch position to support operational actions. Location and accuracy may be included with trip actions and mileage or routing requests. This is not a promise of continuous background tracking. Location use depends on browser permission and the active workflow; changing browser permission can affect location-dependent trip actions.
5. Hosting and other providers
Base44 hosts the website, application, authentication and database services and can serve website images. Supabase provides private evidence storage and processing support. Cloudflare provides network delivery for the public site. Google provides Sign-In, externally loaded web fonts and, for configured application features, mapping or carrier-connected Drive/mail services. Fonts receive technical request data such as an IP address. Billing or other optional providers depend on the carrier’s configuration and should be confirmed before use. An observed vendor is not a promise that every tenant uses every integration.
Review service providers and optional integrations6. Purposes and disclosure
We use information to respond to requests, provide authorized workflows, enforce company and role access, maintain operational and security records, troubleshoot problems and meet applicable obligations. Information can be disclosed to the carrier administering the record, providers operating the requested service, or where required by law. We do not sell personal information or share it for cross-context behavioral advertising. A demo request is not enrollment in an automated marketing-text program.
8. Retention and privacy requests
Retention depends on the purpose and record type, the carrier relationship, security and audit needs, disputes and applicable obligations. This notice does not promise automatic deletion after a fixed period. Contact carrierhelm.admin@gmail.com to request access, correction or deletion, or raise a privacy concern. We may verify identity and coordinate with the carrier responsible for shared records. Deactivating a driver or releasing a seat is not personal-account deletion; retained carrier operational and financial records require separate review. You can revoke Google access in your Google Account permissions.
9. Security
CarrierHelm uses company-scoped records, role-aware access and protected application operations. No system can guarantee absolute security. Contact us about suspected unauthorized access. Specific contractual retention, security and support commitments must be established for the agreed customer service.
10. Google API Services User Data Policy
CarrierHelm’s use and transfer to any other application of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Google API Services User Data Policy11. Children, changes and contact
CarrierHelm is intended for business use and is not directed to children under 16. Contact us if a child’s information was submitted. Updates are posted with a revised date. For privacy, account-data or security questions, use carrierhelm.admin@gmail.com.
12. Customer processing documents
For carrier-controlled personal data, the proposed DPA describes processing duties to be agreed before customer activation. The public provider disclosure distinguishes core infrastructure from optional or customer-controlled integrations. These documents do not establish a subscription, completed due diligence or a legal agreement merely by being viewed.
Review the Data Processing Addendum