1. How to read this list

To run FleetPath we rely on a small set of vetted providers. Each one receives only the data it needs for its function, is bound by contract to protect it, and processes it in the United States. We do not sell personal information, and we do not use your operational data to train any third-party general-purpose AI model.

This page separates two different things: the subprocessors FleetPath engages to operate the platform, and the integrations you connect yourself, where data flows under your own authorization. The distinction matters for who is responsible for the relationship.

2. Platform subprocessors

These providers process data on FleetPath's behalf so the product can function.

Supabase

Database, authentication, and file storage, including the documents you upload before they are read. United States.

Google (Gemini API)

Automated document reading and platform AI features for non-sensitive document classes. Receives page images and text for those classes. Sensitive driver-compliance classes (for example CDL, medical card, drug/alcohol test results, W-9, SSN verification) are gated so their images are not sent to third-party vision. United States.

xAI

Backup AI provider, used only if the primary provider is unavailable. Same document classes and sensitive-document gate as the primary. United States.

Voyage AI

Text embeddings that power in-product search. Receives operational text. United States.

HERE Technologies

Routing, mapping, and geocoding. Receives route locations and pickup and delivery addresses. United States.

Stripe

Subscription billing and payments. Receives payment and account details. FleetPath never stores card numbers. United States.

Resend

Transactional and portal email delivery. Receives recipient email addresses, message content, and any attached documents. United States.

Telnyx

SMS delivery. Receives destination phone numbers and message content solely to deliver operational and safety texts. United States.

Apple (APNs)

Push notifications to the iOS app. Receives device tokens and notification content. United States.

Google (Places API)

Fuel-station lookups near a route. Receives route coordinates only, with no personal identifiers. United States.

3. Infrastructure subprocessors

These providers host and run the services the platform is built on.

Fly.io

Backend and worker compute hosting. United States (Dallas region).

Cloudflare

API hosting and edge security. United States.

Vercel

Web application hosting. United States.

Temporal Cloud

Durable workflow orchestration. Workflow data can include load, document, and driver records. United States.

Sentry

Error monitoring. Receives diagnostic data with credentials stripped before storage. Active only where enabled. United States.

4. Integrations you connect

The following are third parties you connect and authorize. Data flows to and from them under your own connection and provider credentials, so they are your chosen vendors rather than FleetPath subprocessors. You can disconnect any of them at any time, which revokes the stored credential and stops further data exchange.

Motive

Electronic logging and telematics. Connected with your own provider credentials.

Samsara

Electronic logging and telematics. Connected with your own provider credentials.

QuickBooks Online (Intuit)

Accounting sync for invoices and expenses. Connected by you through an authorization flow you approve.

Xero

Accounting sync for invoices and bills. Connected by you through an authorization flow you approve.

FleetPath only integrates with electronic logging providers that appear on the FMCSA official list. When you disconnect a provider, historical records already displayed are retained under the schedule in our Privacy Policy unless you request deletion.

5. What is not on a live data path

FleetPath keeps a reserved, un-provisioned configuration slot for a future prose-assist feature (an Anthropic model). It is not on any live data path today, and no customer data is sent to it. If that ever changes, this list changes first.

Government reference services that FleetPath queries for public data, such as FMCSA, the National Weather Service, and NHTSA, receive lookup values (for example a DOT number or a VIN) rather than a copy of your operational data, and are not subprocessors.

6. Changes to this list

We update this page when we add, remove, or change a subprocessor. Where your agreement provides for advance notice of a new subprocessor, we follow that process so you have the opportunity to review it.

Questions about our providersadmin@fleetpath.app