Sub-processor List
The companies that help us run RushHour, and what each of them can receive.
Version 1.0 | Effective 3 September 2026
How to read this page
A sub-processor is a company we use to run RushHour that may handle personal data on our behalf. We publish the full set here - including services that are built into the product but are not switched on for every customer, and one service we have not connected yet. Naming a provider on this page is not a statement that it is in use. Read the status heading above each table: it tells you whether the provider is processing data today, is available for a customer to enable, or has been disclosed in advance.
This page is published in English. Where a translation is offered it is provided for convenience only; if there is any difference, the English version applies.
What this list covers
This list is referred to by our Privacy Policy and forms part of our Data Processing Agreement. It covers the providers we use to deliver the RushHour platform, the driver app, our web portals and our website.
Each provider is engaged under its data processing terms, which limit it to processing personal data for the purposes described in the tables below and require it to keep that data secure. We do not sell personal data and we do not share it for advertising.
The three statuses on this page
- Currently used. Processing personal data today, for every customer, as part of the running service.
- Available integrations. Built into the product and switched on per customer or by configuration. A customer's data reaches one of these only if that integration is turned on for their account. Ask the company whose RushHour account holds your data which integrations it uses.
- May be used. Disclosed in advance so that we can adopt it without a further announcement. Nothing is sent to a provider in this group today.
Currently used
These providers process personal data today. They are part of how the service runs, so they apply to every RushHour account.
Infrastructure and hosting
| Provider | What it does for RushHour | Personal data it can receive | Where it processes |
|---|---|---|---|
| Amazon Web Services, Inc. | Runs the platform: application servers, the operational database, file and document storage, the search index, the cache layer and our container registry. | Effectively all personal data in the platform - account and contact details, driver records including licence details and uploaded identity documents, pickup and delivery addresses, GPS location points, delivery photos and signatures, messages, invoices and payment metadata, and audit logs. | United States. Uploaded images are stored in US East (Ohio) and company documents in US West (Oregon). |
| Vercel Inc. | Hosts and delivers the rushhourapp.com website and our web portals. The chat assistant on our website runs as a function on Vercel before the message is passed to the AI provider. | Web request data - IP address, browser and device type, and the pages requested - and anything a visitor types into the website chat assistant. | Vercel's global edge network. |
| Cloudflare, Inc. | Domain name service and domain registration for our web addresses. | Domain lookup information, including the address of the resolver making the request. No account, order or driver data. | Cloudflare's global network. |
| Google LLC - Google Fonts | Delivers the web fonts used by the Company Portal. | The IP address, browser type and page address of anyone loading a portal page. No account, order or driver data. | Google's global network. |
| unpkg (npm content delivery network) | Delivers one map plugin script to the browser in the Customer Portal and the Admin Portal. | The IP address and browser type of anyone loading those pages. No account, order or driver data. | Global content delivery network. |
| GitHub, Inc. (Microsoft) | Source control, build and release automation, and the sync that pulls our help documentation into the product. | None by design - our own source code and build logs only. | United States. |
| Docker, Inc. (Docker Hub) | Supplies the base container images used to build the service, and the optional antivirus scanning image. | None. | Docker's global infrastructure. |
Mapping and routing
| Provider | What it does for RushHour | Personal data it can receive | Where it processes |
|---|---|---|---|
| Google LLC - Google Maps Platform | Address autocomplete and validation, geocoding, place details, directions, distance and travel-time calculation, and the maps drawn in our portals and in the driver app. | Pickup and delivery addresses including residential ones, address text typed by dispatchers and customers, warehouse and stop coordinates, and the driver and vehicle positions drawn on a map. The driver app calls Google from the phone, so the device's own IP address reaches Google. | Google's global infrastructure. |
Communications
| Provider | What it does for RushHour | Personal data it can receive | Where it processes |
|---|---|---|---|
| Twilio Inc. (SendGrid) | Sends all of our outbound email - invitations, password and set-password links, invoices, quotes, delivery documents and order notifications. | Recipient names and email addresses, subject lines, full message bodies - which routinely contain customer names, order numbers, addresses and amounts - and attachments such as invoices and bills of lading. | United States, on SendGrid's global infrastructure. |
Payments
| Provider | What it does for RushHour | Personal data it can receive | Where it processes |
|---|---|---|---|
| Cardknox Development Inc. | Processes card payments made against invoices. | The card number, security code and expiry date are typed directly into Cardknox's own hosted fields and never reach our servers. Cardknox also receives the cardholder name, the amount and the invoice reference; we receive back a token and the last four digits. | United States. |
AI features
| Provider | What it does for RushHour | Personal data it can receive | Where it processes |
|---|---|---|---|
| OpenRouter, Inc. | Routes requests from the AI assistant in the Company and Customer Portals, from AI document processing, and from the assistant on our website, to the underlying language model. | Whatever the request contains: the question asked, the order, customer, driver and route records the assistant reads in order to answer it, and text extracted from uploaded documents. OpenRouter forwards the request to the model provider that handles it. | United States, and then the region of the model provider handling the request. |
App distribution and push notifications
| Provider | What it does for RushHour | Personal data it can receive | Where it processes |
|---|---|---|---|
| Expo (650 Industries, Inc.) | Builds the driver app, relays push notifications to Apple and Google, and delivers over-the-air app updates. | Device push tokens and device identifiers; notification titles and bodies, which quote route, stop and order details; and device and app-version information sent when the app checks for an update. | United States. |
| Apple Inc. | Distributes the iOS driver app through the App Store and TestFlight, and delivers push notifications to iPhones. | Apple push tokens and the content of the notifications relayed to them. App Store account data is held by Apple under its own terms, not by us. | Apple's global infrastructure. |
| Google LLC - Google Play and Firebase Cloud Messaging | Distributes the Android driver app and delivers push notifications to Android devices. Expo relays our notifications to Google's messaging service; the app itself contains no Google messaging software. | Android push registration tokens and the content of the notifications relayed to them. Play Store account data is held by Google under its own terms, not by us. | Google's global infrastructure. |
Available integrations
These providers are built into the product but are not used unless the integration is switched on - normally by an administrator on the company's own account, and in a few cases by a configuration setting we control per environment. If an integration is off, nothing is sent to that provider at all.
Being listed here does not mean it is in use
We would rather disclose a provider that turns out never to be used than leave one out that is. Whether any of these applies to you depends on the company whose RushHour account your data sits in. That company can tell you which integrations it has enabled, and we will confirm on request.
AI features
AI requests go through OpenRouter by default. A company can instead supply its own key for one of the providers below, in which case its requests go there.
| Provider | What it does for RushHour | Personal data it can receive | Where it processes |
|---|---|---|---|
| OpenAI, L.L.C. | Voice-to-text for dictated notes and the text embeddings behind document search, and assistant requests for companies that supply their own OpenAI key. | Audio recorded when a user dictates, text extracted from uploaded documents, and the content of assistant requests - customer, order, driver and route details. | United States. |
| Anthropic PBC | Answers AI assistant requests for companies that supply their own Anthropic key. | The content of assistant requests and text extracted from uploaded documents. | United States. |
| xAI Corp. (Grok) | Answers AI assistant requests for companies that supply their own xAI key. | The content of assistant requests and text extracted from uploaded documents. | United States. |
| Google LLC - Gemini | Answers AI assistant requests for companies that supply their own Google AI key. | The content of assistant requests and text extracted from uploaded documents. | Google's global infrastructure. |
Telematics and compliance
| Provider | What it does for RushHour | Personal data it can receive | Where it processes |
|---|---|---|---|
| Samsara Inc. | Electronic logging and fleet telematics for companies that connect a Samsara account: vehicle locations, hours-of-service clocks and driver records are synchronised. | Driver name, username, phone number, driver licence number and issuing state, and activation status; vehicle locations and duty status. Samsara's carrier settings - carrier name, office address and DOT number - are read back into RushHour. | United States. |
Payments and accounting
| Provider | What it does for RushHour | Personal data it can receive | Where it processes |
|---|---|---|---|
| Intuit Inc. - QuickBooks Online | Pushes invoices and payments into the company's own QuickBooks file, over a connection the company authorises. | Customer names, billing addresses and email addresses; invoice lines and totals; payment records; and driver names, which are used as QuickBooks class names. | United States. |
Communications and messaging
| Provider | What it does for RushHour | Personal data it can receive | Where it processes |
|---|---|---|---|
| Ably Real-time Ltd | Delivers in-app chat between dispatchers and drivers in real time. | Message content, chat and route identifiers, the sender's identity, and the IP address of the connecting browser or device. | Ably's global edge network. |
| Telegram (Telegram FZ-LLC / Telegram Messenger Inc.) | Sends route and stop messages to drivers over Telegram, where a company enables it. The Telegram connection is handled by a separate service that RushHour runs. | The driver's Telegram identifier, phone numbers used to reach the account, and message text containing route, stop and address details. | Telegram's global infrastructure. |
| Google LLC - Gmail SMTP | An alternative way of sending our email, used in place of SendGrid where it is configured. | The same as SendGrid: recipient addresses and full message bodies, with their attachments. | Google's global infrastructure. |
Mapping, routing and address data
A company chooses which map and routing provider its account uses. Only the one it selects receives anything.
| Provider | What it does for RushHour | Personal data it can receive | Where it processes |
|---|---|---|---|
| Trimble Inc. (Trimble Maps / PC*MILER) | Truck-aware geocoding, routing, map tiles and toll pricing, where a company selects Trimble. | Pickup and delivery addresses, route waypoint coordinates, and the vehicle profile used to price tolls. | United States. |
| Mapbox, Inc. | Map tiles, and geocoding, directions and route optimisation once that fuller integration is switched on. | Map view coordinates and the browser IP address for tiles; addresses and route waypoints where geocoding or routing is used. | United States. |
| HERE Global B.V. | Maps, address autosuggest, routing and stop-sequence optimisation, where a company selects HERE. | Addresses and address text typed by users, route waypoint coordinates, and the IP address of the browser loading a HERE map. | Netherlands, and HERE's global endpoints. |
| Radar Labs, Inc. | Maps, address autocomplete, directions and route optimisation, where a company selects Radar. | Addresses and address text typed by users, route waypoint coordinates, and the IP address of the browser loading a Radar map. | United States. |
| OpenStreetMap Foundation | A free map tile layer that a company can select as its map background. | The viewer's IP address and the map tiles requested, fetched by the browser directly from OpenStreetMap servers. | Volunteer-run infrastructure, mainly in Europe. |
| Valhalla routing engine | Calculates route paths. By default this runs on RushHour's own servers and no third party is involved. A company can instead point it at a routing host of its own choosing. | Route waypoint coordinates only. In the default configuration nothing leaves our own systems. | Our own infrastructure by default; otherwise wherever the configured host runs. |
| VROOM optimisation engine | Works out the best order for the stops on a route. By default this runs on RushHour's own servers. A company can instead point it at a host of its own choosing. | Stop coordinates and vehicle constraints only. In the default configuration nothing leaves our own systems. | Our own infrastructure by default; otherwise wherever the configured host runs. |
| TollGuru | Estimates toll costs for a priced route. | Route origin, destination and waypoint coordinates, and the vehicle class. No names or contact details. | United States. |
| GeoNames (Unxos GmbH) | Looks up postal codes from a city and state, to validate and suggest ZIP codes in address forms. | City, state and country names typed into an address form. | Switzerland. |
Freight tracking and reference data
| Provider | What it does for RushHour | Personal data it can receive | Where it processes |
|---|---|---|---|
| CHAMP Cargosystems S.A. | Air waybill track-and-trace for air freight shipments. | The airline prefix and air waybill number. No names or contact details, although the waybill identifies a specific shipment. | Luxembourg. |
| Sinay SAS | Ocean container tracking for sea freight shipments. | Container numbers. No personal data. | France. |
| CollectAPI | Supplies regional fuel prices used in cost estimates. | Region or state codes. No personal data. | Turkey. |
Monitoring and alerting
| Provider | What it does for RushHour | Personal data it can receive | Where it processes |
|---|---|---|---|
| Functional Software, Inc. (Sentry) | Records server errors so that we can find and fix faults. It is switched off entirely unless an error-reporting address is configured for that environment. | Error messages and stack traces, the web address and request details of the request that failed, and any account or record identifier that happens to appear in the error. Vendor keys are removed before an error report is sent. | United States or the European Union, depending on the account the reports are sent to. |
| Slack Technologies, LLC (Salesforce) | Delivers internal operational and cost alerts to a RushHour channel, so that our own team sees them. | Operational and spend figures and vendor and company names. No driver, customer or end-user personal data. | United States. |
May be used
Nothing below is connected and nothing is sent to it today. We disclose it here in advance so that the capability can be enabled without a surprise. If we select a provider for it, we will name that provider on this page before it starts processing personal data, and give notice as described below.
Communications and messaging
| Provider | What it does for RushHour | Personal data it can receive | Where it processes |
|---|---|---|---|
| SMS and WhatsApp delivery notifications - no provider selected | Customer stop notifications by SMS or WhatsApp. The channel can already be chosen in settings so that a company can record a preference, but no messaging provider is connected and nothing is sent. Only email notifications are delivered today. | None today. A provider added later would receive customer phone numbers and the text of delivery-status messages. | Not yet determined - no provider has been selected. |
What is not on this list, and why
We do not use analytics, advertising or attribution tools in the driver app or in our portals. There is no advertising software in the driver app, no advertising identifier is collected, and the Android build blocks the advertising ID outright. The app shows no app-tracking prompt because it does no cross-app tracking.
Two of the routing services above deserve a word: Valhalla and VROOM run on our own servers in their default configuration, so choosing them does not introduce a third party at all. They appear in the list because a company can point them at a host of its own instead.
We also disclose providers in the tables above that receive no personal data at all - source control, container images, fuel-price and postal-code lookups - so that the list is complete rather than only the parts that are awkward.
Where data is processed
We run the platform in the United States. The "Where it processes" column names a country only where that is what the provider does for us; otherwise it says that the provider operates a global network and decides the region itself. A handful of providers are outside the United States - HERE in the Netherlands, Sinay in France, CHAMP in Luxembourg, GeoNames in Switzerland, CollectAPI in Turkey, and the OpenStreetMap tile service on volunteer infrastructure mainly in Europe.
Where personal data moves between countries, the transfer safeguards described in our Privacy Policy apply.
Changes to this list, and how to object
We update this page whenever we add or replace a sub-processor, and we do it before that provider starts processing personal data.
- How we give notice: this page is the notice. We update it before a new or replacement sub-processor starts processing personal data, and before an existing one starts handling a materially different category of data. There is no waiting period: once the page is current, the provider can be switched on.
- If you want an email as well: write to privacy@rushhourapp.com and we will add you to the notification list. Subscribers get an email each time this page changes. We do not email every customer about every change, because keeping one published list accurate is more reliable than a mailing round.
- Objection: a customer may object in writing to privacy@rushhourapp.com within 30 days of the change appearing here, on reasonable data protection grounds. We will work with you to find a reasonable alternative. If we cannot, you may terminate the affected part of the service without penalty and receive a pro-rata refund of fees paid for the unused period. This mirrors the objection right in our Data Processing Agreement, which governs if the two ever differ.
- Enabling an integration is not a change to this list. When an administrator switches on an integration that is already published above, that is the company's own decision about its own data, and no notice period from us applies.
- Emergency replacements: if a provider has to be replaced urgently - it fails, or its contract ends without notice - we will make the change and update this page as soon as we can, and tell affected customers what happened.
Subscribe to changes
Email privacy@rushhourapp.com with the subject "Sub-processor notifications" and the address or addresses you want notified, and we will email you whenever this page changes. You do not have to be an account administrator to subscribe, and you can unsubscribe by replying to any of those emails.
Each version of this page carries a version number and an effective date at the top. We keep earlier versions and will send you one on request.
Related documents
- Privacy Policy - what we collect, why, how long we keep it and your rights.
- Data Processing Agreement - the terms on which we process personal data for our business customers, including the sub-processor notice and objection right.
- Terms of Service - the commercial terms for using RushHour.
Contact us
Questions about this list, objections to a new sub-processor, and requests to be notified of changes all go to the same address.
Rush Hour Logistics System Inc
1272 54th Street, Brooklyn, NY 11219, USA
New York Department of State ID 5098884
Sub-processor questions, objections and notifications: privacy@rushhourapp.com
Legal notices: legal@rushhourapp.com
Security reports: security@rushhourapp.com
General enquiries: info@rushhourapp.com
We acknowledge privacy requests within 5 business days.