Skip to main content

Sub-Processors and Third-Party Recipients

Last updated: October 2026

FleetHD Inc. uses the sub-processors and third-party recipients listed below to provide and support the FleetHD platform. This page is referenced by our Privacy Policy and our Data Processing Addendum. FleetHD maintains this page and will update it when sub-processors change.

Sub-Processors

The following service providers process personal data on behalf of FleetHD, under written obligations consistent with the terms of our Data Processing Addendum. These sub-processors support both FleetHD's controller processing and its service-provider processing on behalf of fleet operator customers.

Sub-ProcessorFunctionData InvolvedHosting Location
Microsoft AzureCloud infrastructure, identity management, endpoint and email security, SIEM, and optical character recognition (VIN reading)Account data, all hosted application data, authentication tokens, logsUnited States
MongoDB AtlasProduction databaseAll customer and application recordsUnited States
SisenseEmbedded analytics dashboards within the authenticated applicationName and email via session token; operational data in the analytics clusterUnited States
Twilio (including SendGrid)Email (via SendGrid) and SMS notification deliveryContact information (phone numbers, email addresses), notification contentUnited States
CloudflareDNS resolution and DDoS protectionNetwork metadata, IP addressesUnited States (geo-aware DNS routing)
Google Maps PlatformMaps and geocoding servicesLocation and address dataUnited States (geo-aware DNS routing)
All sub-processors listed above host FleetHD data in the United States. For Cloudflare, Twilio, and Google Maps, US delivery is achieved via geo-aware DNS request routing rather than a contractual data-residency guarantee.

Voice Features

The following sub-processors are engaged only where a fleet operator customer's subscription includes Voice Features, being FleetHD's voice assistant, voice dictation, and related AI features. They do not process data for customers who have not enabled Voice Features. This list corresponds to Schedule 1 to our Data Processing Addendum.

Sub-ProcessorFunctionData InvolvedHosting Location
LiveKitReal-time audio transport, agent connection, noise and echo cancellationAudio data, voice session metadataUnited States
DeepgramReal-time speech-to-textAudio dataUnited States (by routing)
GoogleLarge language model providing AI assistant reasoningSpeech-to-text transcriptions, query contextUnited States
ElevenLabsText-to-speechAI assistant response textUnited States
Microsoft Azure OpenAIEmbeddings for document searchQuery text, document fragmentsUnited States
Microsoft Azure AI SearchVector and semantic retrieval over truck documentationQuery textUnited States
Where a location is marked "by routing," FleetHD directs the processing to that location through its configuration and use of the service; the Sub-processor's agreement with FleetHD does not itself commit to that location.
Audio is processed in real time and is not retained after processing. The AI Interaction Transcript, comprising both the user's input and the assistant's response, is retained for up to 12 months. Retention of voice data is described in Schedule 1 to our Data Processing Addendum.

Third-Party Recipients (Controller Processing)

The following third parties receive personal data in connection with FleetHD's own business operations, where FleetHD acts as data controller.

RecipientFunctionData Involved
Google Analytics (GA4) / Firebase AnalyticsWebsite analytics (GA4) and mobile application analytics (Firebase)Usage data, device data, approximate geolocation, IP address

Customer-Directed Sharing

Where a fleet operator customer directs FleetHD to share platform data with a third party, FleetHD does so in its capacity as the customer's service provider (processor), acting on the customer's instructions. This sharing is governed by the applicable customer agreement and the Data Processing Addendum. Recipients in this category may include:

Recipient CategoryExamplesData Involved
Telematics and integration partnersGeotab, Samsara, LytxVehicle diagnostic and operational data (bidirectional, system-to-system)
Third-party AI and voice services designated by the customerGoodcall, Happy RobotPlatform data provided via FleetHD APIs at customer's direction
Customer work-order and maintenance systemsVaries by customerWork requests, repair records, and related operational data

If you have questions about this page or FleetHD's data processing practices, please contact us at privacy@fleethd.com.

This page is maintained by FleetHD Inc., 10089 Willow Creek Rd #200, San Diego, CA 92131.