Your data runs your business.
We treat it that way.

FleetPath is operated by FleetPath Technologies, Inc., a wholly-owned subsidiary of Lavish Enterprises, Inc. (OTC: VXIT). This policy explains how FleetPath handles data across the web application, the iOS application, and the backend services that run them. It applies to carriers, fleets, drivers, dispatchers, owners, and the brokers and shippers who interact with a carrier through FleetPath.

FleetPath is a multi-tenant platform. Each carrier organization is a separate tenant. Data is isolated per tenant at the database level with row-level security, and one tenant cannot read another tenant's data.

Account & identity.

Name, work email, role within the organization, and the tenant you belong to. Authentication is handled by our identity provider; we do not store your password.

Operational data.

Loads, trips, rate confirmations, bills of lading, proof of delivery, lumper and scale receipts, invoices, expenses, permits, inspections, and messages you create or upload. Documents you upload are processed by an automated extraction model to read structured fields (for example, the rate and lane on a rate confirmation).

Precise location during navigation (device GPS + HERE Positioning).

When you use in-app turn-by-turn navigation, FleetPath and the HERE Navigate SDK collect precise location so we can show your truck on the map, match you to the route, and provide guidance. That may include GPS coordinates and characteristics of nearby radio networks that the HERE Positioning service uses to improve accuracy. Collection for navigation runs while guidance is active (and, if you grant background location, may continue while a trip is active with the app backgrounded). You can refuse or revoke location permission in system settings; without it, map tiles and route previews may still work, but live vehicle positioning will not. HERE's own privacy policy applies to data they process: legal.here.com/privacy. FleetPath only enables HERE Positioning after you accept the in-app notice that describes this collection.

Telematics & ELD data, only with your connection.

FleetPath does not record hours of service and is not a registered ELD. We display telematics data only when your organization explicitly connects a third-party provider (such as Motive or Samsara) using your own provider credentials. See section 4 for detail.

Technical data.

Standard request metadata (IP address, timestamps, user agent) for security and audit logging, and error diagnostics with credentials stripped before storage.

We use data to operate the platform: to run your loads and settlements, extract fields from documents you upload, surface operational alerts, route trips, process billing, and keep the service secure. We may offer an optional, opt-in benchmarking feature that uses only aggregated, de-identified data; participation is your choice (see our Terms of Service).

We do not sell personal information. We do not share your data with third parties for their own marketing. We do not use your operational data to train third-party general-purpose models.

FleetPath is a visibility layer, not a compliance system of record. We do not capture, generate, certify, or store hours-of-service duty status as an authoritative record. The carrier remains responsible for ELD compliance under 49 CFR Part 395.

When your organization connects a telematics or ELD provider, the connection uses an authorization flow scoped to the data you approve. FleetPath reads only the data fields required for the features you use, displays them, and stops reading them when you disconnect. Provider credentials are encrypted at rest and every access to them is recorded in an audit log. Disconnecting a provider revokes the stored credential and stops further data collection; historical records already displayed are retained per section 6 unless you request deletion.

The platform is fully usable without any telematics provider connected. Features that benefit from live telematics degrade to a manual or estimated mode rather than being withheld.

Accounting and other connections.

You can also connect an accounting provider such as QuickBooks Online (Intuit) or Xero. When you do, FleetPath sends the invoice, customer, and expense records you choose to sync so your books stay current, under an authorization you grant and can revoke at any time by disconnecting. These connected providers are your own chosen vendors rather than FleetPath subprocessors.

We rely on a small set of vetted subprocessors to run the service. Each receives only the data necessary for its function, is contractually bound to protect it, and processes it in the United States. The full, current list, with what each provider receives, is on our Subprocessors page. In summary:

• SupabaseDatabase, authentication, and file storage
• Google (Gemini API)Automated document reading and AI features
• xAIBackup AI provider, used only if the primary is unavailable
• Voyage AIText embeddings for in-product search
• HERE TechnologiesRouting, mapping, geocoding, traffic, and — when you enable in-app navigation positioning — continuous location used for turn-by-turn guidance (see section 2 and HERE's privacy policy)
• StripeSubscription billing and payments
• ResendTransactional and portal email
• TelnyxSMS delivery. Receives destination numbers and message content solely to deliver texts
• Apple (APNs)iOS push notifications
• Fly.io, Cloudflare, Vercel, Temporal CloudHosting and workflow orchestration
• SentryError monitoring, with credentials stripped

Payment card data is handled entirely by Stripe. FleetPath never stores card numbers. Providers you connect yourself, such as Motive, Samsara, QuickBooks, or Xero, are covered in section 4 and on the Subprocessors page.

We retain operational records for as long as your organization has an active account, and after that for the period required by the applicable regulation (for example, DOT and IFTA record-keeping windows) or our documented retention schedule, whichever is longer. Transient processing artifacts (for example load-analyzer board photos) are deleted on a short cycle (hours to days). When you request account deletion, we open a cancelable grace window (about thirty days): your account stays intact and recoverable until that window ends, then a retention-aware purge hard-deletes what we are not required to keep. We do not sign you out or destroy your data at the moment you click delete. Records under a legal retention obligation (for example DOT and IFTA classes) are kept in restricted form; we do not purge them on an automatic statutory clock, because the obligation is your organization's and the governing period varies by jurisdiction. You can ask us to delete a retained class at any time.

Data is encrypted in transit (TLS 1.2+) and provider credentials are encrypted at rest. Tenant isolation is enforced at the database with row-level security. Access is role-based, multi-factor authentication is available, credential access is audit-logged, we maintain incident-response runbooks, and we run recurring internal security audits.

Depending on your jurisdiction (including under GDPR and the CCPA/CPRA), you may request access to the personal data we hold about you, a portable export of it, correction of inaccuracies, or deletion. You may also object to or restrict certain processing. We do not sell personal information, so there is nothing to opt out of in that respect.

To exercise any of these rights, contact admin@fleetpath.app. We verify the requester before acting and respond within the timeframe the applicable law requires.

FleetPath is operated from the United States and data is processed there. The platform is a business tool intended for commercial motor carrier operations and is not directed to children; we do not knowingly collect data from anyone under 16.

If we make a material change, we will update the effective date above and, where required, notify account administrators. Continued use after an update constitutes acceptance of the revised policy.

FleetPath may send operational and safety text messages to phone numbers that a carrier organization enters into its own FleetPath account. Recipients are the carrier's own staff and the emergency-contact and dispatcher numbers the carrier designates. We do not send marketing or promotional texts.

Message types include emergency SOS alerts to a driver's designated emergency contact and the carrier's dispatcher, and operational notifications to the carrier's own staff (for example load-status and exception alerts) as those features are enabled. Message frequency varies. Message and data rates may apply.

Your mobile information will not be sold or shared with third parties for promotional or marketing purposes.

All the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.

We will not share your opt-in to an SMS campaign with any third party for purposes unrelated to providing you with the services of that campaign. We may share your Personal Data, including your SMS opt-in or consent status, with third parties that help us provide our messaging services, including but not limited to platform providers, phone companies, and any other vendors who assist us in the delivery of text messages.

Reply STOP to any FleetPath text to opt out of non-emergency operational messages. Reply HELP or email admin@fleetpath.app for assistance. Program details, including how to opt out and how to get help, are also on our SMS program page and in the Terms of Service.

Emergency SOS alerts may still be sent when a driver requests emergency help, even if a number has opted out of operational messages. Those alerts are safety messages, not marketing.