Sub-Processor List
LogAI.ai uses the following third-party subprocessors to provide the service. This list is maintained and updated when subprocessor relationships change materially.
| Subprocessor | Country | Purpose | Data Processed |
|---|---|---|---|
| Hetzner Cloud | Germany (EU) | Compute infrastructure — application servers, worker processes, and managed database hosting. | All customer operational data, load records, freight documents, and load event history. |
| Cloudflare | Global (CDN nodes worldwide) | CDN, DDoS protection, and TLS termination for the LogAI.ai application. | Request metadata and cached static assets. Customer payload data passes through but is not stored by Cloudflare beyond the request. |
| PostgreSQL (Hetzner Managed DB) | Germany (EU) | Primary relational database — load records, carrier data, document metadata, event history, and user accounts. | All customer operational and account data. |
| SendGrid (Twilio) | USA | Transactional email — load status notifications, document collection requests, missing POD chase emails, and billing notifications. | Recipient email address, sender name, and email body content for transactional messages. |
| Telnyx | USA | Voice communications — outbound check calls placed by the Phony module on behalf of LogAI.ai customers. | Phone numbers dialed, call audio, and call transcripts associated with specific load records. |
| Twilio | USA | Voice communications fallback — used when Telnyx is unavailable. Same purpose as Telnyx. | Phone numbers dialed, call audio, and call transcripts associated with specific load records. |
Compute infrastructure — application servers, worker processes, and managed database hosting.
Data: All customer operational data, load records, freight documents, and load event history.
CDN, DDoS protection, and TLS termination for the LogAI.ai application.
Data: Request metadata and cached static assets. Customer payload data passes through but is not stored by Cloudflare beyond the request.
Primary relational database — load records, carrier data, document metadata, event history, and user accounts.
Data: All customer operational and account data.
Transactional email — load status notifications, document collection requests, missing POD chase emails, and billing notifications.
Data: Recipient email address, sender name, and email body content for transactional messages.
Voice communications — outbound check calls placed by the Phony module on behalf of LogAI.ai customers.
Data: Phone numbers dialed, call audio, and call transcripts associated with specific load records.
Voice communications fallback — used when Telnyx is unavailable. Same purpose as Telnyx.
Data: Phone numbers dialed, call audio, and call transcripts associated with specific load records.