Last updated September 27, 2026.
MileCount uses account, vehicle, trip and load-analysis information to provide route and freight-economics tools. Account authentication and application data are stored using Supabase. Subscription payments are processed by Stripe; MileCount does not store full payment-card numbers.
Account identifiers, saved vehicle specifications, operating-cost assumptions, routes, analyzed loads, trip economics, subscription status and basic application events.
To authenticate users, save vehicles and trips, calculate economics, operate paid features, secure the service, troubleshoot errors and improve MileCount.
We may use service providers needed to operate MileCount, including hosting/database, payment and future authorized freight-data providers. We do not state that freight providers or partners can access a user's private MileCount account data unless an integration specifically requires and discloses it.
Data may be retained while an account is active and as reasonably necessary for security, billing, legal and operational purposes. Users may contact MileCount to request account-data assistance. Additional deletion/export controls are planned before broad public launch.
Trip, fuel, RPM, margin and load-fit outputs are planning estimates and may depend on user-entered or third-party data.