Privacy Policy
Last updated: October 18, 2026
This policy explains how Motor Supply, Inc. handles information through LoadFlow, including loadflow.io, the application and connected services. LoadFlow serves fleet businesses. The fleet customer retains its rights in its fleet data. We process that data to provide the service and the features its authorized users choose.
Information we receive
- Accounts and contacts: Organization name, user email, name, role, phone and profile information, invitations, support messages, password hash or Google sign-in identifier, and onboarding details.
- Connected ELD data: When a fleet connects Motive or Samsara, we receive organization and connection details; vehicle identifiers and status; driver identities and assignments; HOS clocks and duty activity; vehicle locations, timestamps, speed, mileage, related telemetry and available fault information. Fields depend on provider access and enabled features.
- Trips and documents: Loads, stops, addresses, customers and contacts, appointment times, routes, ETA forecasts, notes, amounts and uploaded rate confirmations, bills of lading, proof of delivery, photos and other trip files. A connected dispatch sheet or QuickBooks account supplies information for those features.
- Billing: Stripe collects payment details. We receive and store Stripe customer, subscription, Checkout and invoice identifiers, truck quantity, payment/subscription status and related dates. Some older records may contain card brand, last four digits and expiration date. Full card numbers are entered through Stripe’s payment flow.
- Technical activity: Session and socket identifiers, browser and device information sent with requests, IP address, page visits, feature events, errors, performance traces and operational logs. Some app errors may include masked session replay. These records can include account or request context used for troubleshooting.
How we use information
We use information to authenticate users; connect and synchronize ELDs; display fleet locations and trips; calculate forecasts, HOS views and diagnostic indicators; parse documents selected by customers; provide support; monitor security and reliability; send operational messages; bill subscribed organizations; and improve the service.
We do not sell personal information. We do not use fleet data for advertising or to train AI models. When a customer requests document extraction, OpenAI processes the submitted document through its API for that request.
Service providers and integrations
We send information to the providers needed for the service and features a customer uses:
| Provider | Purpose |
|---|---|
| Amazon Web Services | Hosts the service, stores private uploaded files in S3, sends email through SES and supports operational infrastructure and logs. |
| MongoDB Atlas | Stores account, fleet, trip, driver, location, integration and billing metadata. |
| Motive and Samsara | Supply data through a fleet’s connected ELD account and handle connection requests. |
| Provides Maps, Places, geocoding and time-zone features; optional Google sign-in; Google Sheets for a connected dispatch sheet; and Google Analytics for homepage usage. | |
| HERE Technologies | Receives route stops and coordinates for truck-routing forecasts. |
| OpenAI | Processes a rate-confirmation PDF and extraction instructions when a customer requests automatic document extraction. |
| Stripe | Handles Checkout, recurring payments and the billing portal, and returns billing status. |
| Sentry | Receives error and sampled performance information; some app errors include masked replay. |
| Telegram | Receives operational alerts that may include fleet name or ID, subscription and integration events, or onboarding contact details. |
| Intuit QuickBooks | If connected, exchanges customer and invoice information, including relevant trip and payout details. |
| Fair Analytics and Tidio | Provide homepage analytics and chat. |
The homepage and app also load some browser assets from Google-hosted storage and cdnjs, which receive ordinary browser request information. We may disclose information to comply with law, respond to a lawful request, or protect the service and its users.
Cookies and analytics
LoadFlow uses a session cookie and a socket cookie, each configured for up to 14 days, to support authenticated features. The app uses local storage for Live and wall-display preferences and session storage for a short-lived marketplace installation flow. The homepage uses Google Analytics, Fair Analytics and Tidio chat. These services receive browser usage or chat information and may use their own browser storage. The production app sends diagnostic information to Sentry.
Security and file access
We use encryption in transit, access controls and account-scoped application access. Uploaded files are stored as private S3 objects. Before giving a user a short-lived signed link to a file, LoadFlow checks that user’s access to the organization. Authorized users can share or export information they can access in LoadFlow.
Storage and retention
The main application records are stored in MongoDB Atlas, and uploaded files are stored in Amazon S3. Location breadcrumbs in a dedicated time-series collection have a 90-day database TTL from each point’s timestamp. Derived trip locations, last positions, forecasts and driver-truck history can remain longer. Session records and the two LoadFlow cookies are configured for 14 days; OAuth connection state for 10 minutes; password/reset token records for 24 hours; and route-cache entries for seven days. Other records are retained to operate the service until they are deleted under the process below or retained as required by law.
Export, correction and deletion
Authorized users can download a trips CSV and remove individual trip files or trips. An organization owner can request a broader export, correction or deletion at loadflow@motor-supply.com. We verify the owner’s request and delete the organization’s customer data within 30 days of a verified deletion request, except backups and records we must keep by law. If a driver or another individual asks about information supplied by a fleet, we may coordinate with that fleet. Stripe and other providers may retain their own transaction or service records under their policies.
Changes and contact
We will post updates to this policy with a new “Last updated” date. Questions or data requests: loadflow@motor-supply.com.