Subprocessors

How to read this list

These are the companies that may handle personal data on our behalf. Some apply only when a deployment turns the feature on (the "When" column on the page). We publish a new version of this page before adding one.

Cloud hosting and managed PostgreSQL

Purpose: Runs the application and stores its database.

Data: All account and operational data.

Location: The region chosen for the deployment (Canada or United States).

Used: Always.

S3-compatible object storage

Purpose: Stores uploaded files: proof-of-delivery photos, signatures, driver and vehicle documents, exports.

Data: Files you or your drivers upload.

Location: Same region as the database.

Used: Always.

Stripe

Purpose: Card payments for invoices, subscriptions, and driver payout onboarding (Connect).

Data: Company and payer name, email, billing details, payment amounts. Card numbers go to Stripe directly and never reach us..

Location: United States and Stripe regions.

Used: When online payments are enabled.

Email delivery provider (SMTP relay, Postmark, Resend or Amazon SES, chosen per deployment)

Purpose: Sends invitations, order updates, invoices and password resets.

Data: Recipient email address, name, message content.

Location: Provider region.

Used: Always for email.

Twilio

Purpose: Sends SMS order updates and one-time codes.

Data: Recipient phone number and message text.

Location: United States.

Used: When SMS is enabled for a company.

Expo push notification service

Purpose: Delivers push notifications to the driver app.

Data: Device push token, notification title and text.

Location: United States.

Used: When drivers use the mobile app.

CARTO basemap tiles

Purpose: Draws the map in the live map, route planner and tracking page.

Data: Map tile requests: the visitor IP address and the area being viewed.

Location: Global CDN.

Used: When a map is shown.

Google Maps Platform (Places)

Purpose: Address autocomplete in order and address forms.

Data: Text typed in an address field, and the visitor IP address.

Location: United States.

Used: Only if the deployment sets a Google Maps key.

Google (Maps SDK for Android, Firebase Cloud Messaging)

Purpose: Draws maps in the Android driver app and delivers its push notifications.

Data: Map requests (the area shown and the device IP address); device push token and notification text.

Location: United States.

Used: When drivers use the Android app.

Apple (MapKit, Apple Push Notification service)

Purpose: Draws maps in the iPhone driver app and delivers its push notifications.

Data: Map requests (the area shown and the device IP address); device push token and notification text.

Location: United States.

Used: When drivers use the iPhone app.

Anthropic (Claude API)

Purpose: Runs the AI assistant: drafts orders from pasted messages, suggests address-book fixes, pricing setups and route plans, writes the daily brief and customer message drafts. A person checks every suggestion before anything is saved or sent..

Data: The text a user pastes or types into an assistant, and the company records the feature needs to answer: customer names, address-book entries, order details, contact names and phone numbers. Never passwords, card or bank details, or driver documents. Anthropic does not train its models on this data..

Location: United States.

Used: Only for companies whose plan includes the AI assistant, when a user asks it for something.

Sentry

Purpose: Error monitoring.

Data: Error details, request path, a pseudonymous user id. Personal data in messages is scrubbed before sending..

Location: United States or EU region.

Used: Only if the deployment sets a Sentry DSN.