Where DispatchAi data may be processed.
DispatchAi uses service providers to run infrastructure, protect login, store documents, parse paperwork, power maps, and support customer-approved integrations. Customer-enabled integrations process data only when the customer connects or configures that workflow.
| Provider | Purpose | Data categories | Status |
|---|---|---|---|
| Amazon Web Services | Hosting, storage, AWS S3 document storage, AWS Textract OCR, AWS SES-style transactional email, AWS Location/geofence services, and device infrastructure where configured. | Account, tenant, documents, OCR metadata, operational records, logs, and service metadata. | Core infrastructure |
| Cloudflare | Cloudflare Turnstile login security, bot prevention, Cloudflare Email Routing, and signed email-intake worker delivery where configured. | Security challenge metadata, browser/device signals, inbound email routing metadata, and normalized intake payloads. | Security and intake provider |
| Google Maps surfaces and Gmail integrations when a customer connects them. | Map requests, addresses, Gmail thread/message metadata, attachments, and outbound email content when enabled. | Customer-enabled | |
| Smartsheet | Customer-approved load import and synchronization workflows. | Sheet rows, load references, sync metadata, and customer-approved integration fields. | Customer-enabled |
| Mobile platform push services | Push notification delivery for driver or office mobile workflows when a customer enables native or mobile push. | Push tokens, device metadata, delivery attempts, and operational notification content. | Planned or customer-enabled |
| Hardware and dashcam providers | Future ELD, telematics, live viewing, camera obstruction, dashcam safety, and device health workflows. | Vehicle, device, safety event, camera channel, clip, and telemetry metadata. | Hardware pilot only |
DispatchAi does not sell personal information or use customer operational data for cross-context behavioral advertising.