Legal
Legal Archive
Last updated: November 4, 2026
Which version of each RushHour legal document is in force, and which versions it replaced
What this page is for
Our legal documents change over time, and the version that applied when you signed up is not always the version on the site today. This page records the version number and effective date of every RushHour legal document, so you can tell which text governed your account, an order or a data request at any point in time.
If you are working out which terms applied on a particular date, use the version history below and then ask us for that copy. We keep a dated copy of every version we have published.
Documents in force today
These are the current documents. Each links to the live page.
| Document | Version | Date | Read it |
|---|---|---|---|
| Privacy Policy | Version 3.5 | Effective November 4, 2026 | /privacy |
| Terms of Service | Version 3.5 | Effective November 4, 2026 (accounts opened earlier: December 4, 2026) | /tos |
| Data Processing Agreement | Version 1.3 | Effective November 1, 2026 | /dpa |
| Sub-processor list | Not versioned - maintained continuously | Current list published on the page | /subprocessors |
| Account deletion instructions | Not versioned - support documentation | Updated October 25, 2026 | /delete-user-account |
What each document covers
- Privacy Policy. What personal data the platform holds, why we hold it, who it is shared with, how long it is kept, and the rights you can exercise.
- Terms of Service. The contract for using the platform and the driver app: subscriptions, billing, card payments from your customers, acceptable use, liability and dispute resolution.
- Data Processing Agreement. The processor terms that apply when we handle personal data on a business customer's behalf, including security, sub-processors and the assistance we owe you.
- Sub-processor list. The providers that process data for us, what each one does and what data it receives.
- Account deletion instructions. How a driver deletes their account in the app, what a company administrator can do in the portal, and what is erased and what is kept.
Version history
Dates are the dates each version took effect. A version stays in force until the date the next one takes effect.
Privacy Policy
| Version | Effective | Status | Notes |
|---|---|---|---|
| Version 3.5 | November 4, 2026 | In force | Current version. Replaces Version 3.4 of November 1, 2026. Describes the security check Cloudflare runs on our forms: Cloudflare Turnstile checks that a person, not an automated program, is sending the contact and free-trial forms on our website and the sign-in and sign-up forms of our web portals, and Cloudflare's network carries the traffic to our website and web portals, filtering out attacks and automated abuse. Says what Cloudflare receives, that it tells us only whether the check passed, and that we keep only that result in our server logs. The check protects our forms and accounts and starts no other use of personal data, so it took effect on publication. |
| Version 3.4 | November 1, 2026 | Superseded | Superseded on November 4, 2026 by Version 3.5. Copy available on request. When published it replaced Version 3.3 of October 13, 2026. Describes the card payments a company can take from its own customers through RushHour, which we are introducing: through the company's own Cardknox or Stripe account or, where the company chooses it, through RushHour's Stripe account; card holds, saved cards, payment links emailed to a customer with a payment page, payments in the Customer Portal and card payments a driver takes at a stop. Names Stripe as a provider for those payments, says what Stripe and Cardknox receive and what we keep, and confirms that card numbers and security codes never reach our servers. It starts no new use of personal data: those payments happen only where a company turns them on, so it took effect on publication. |
| Version 3.3 | October 13, 2026 | Superseded | Superseded on November 1, 2026 by Version 3.4. Copy available on request. When published it replaced Version 3.2 of October 5, 2026. Most of what it adds describes our platform release of October 16, 2026 and has applied since that release reached the company a driver works for. Describes the driver app's chat and call features - voice messages, files and shared locations in chat, online status and last seen, secret chats, and voice and video calls between drivers, which show each phone's network address to the other phone and use public STUN servers run by Google and Cloudflare and, where needed, Cloudflare's relay - and corrects the earlier statement that the app has no voice recording in chat. Adds driver ratings, training progress, link previews in chat and live-traffic arrival times; what happens to the details of a person who buys a subscription online, where we offer that, which Stripe sells as the merchant of record through its affiliate Sold through Link, LLC; and the driver data retention settings each company controls from that release, including what happens when the company a driver works for deletes the driver's account - erased after the grace period where the company's account was open before the release, unless it switches that off, and archived where it opens its account later, unless it switches erasure on. Updated October 25, 2026: the wording "from our next platform release" was removed now that the release is live, and where the date matters the policy names it as our platform release of October 16, 2026. This is a correction, so the version number stays 3.3 and what the policy describes has not changed. |
| Version 3.2 | October 5, 2026 | Superseded | Superseded on October 13, 2026 by Version 3.3. Copy available on request. When published it replaced Version 3.1 of September 27, 2026. Updates the entry on how long driver location points are kept, which said they are always deleted after 90 days: that is how the platform works at the date of this version, and from our platform release of October 16, 2026 deleting them becomes a setting each company controls, off unless the company switches it on. Adds a section on what the customers of the company a driver works for can see - shipment tracking links, which can show anyone who has an order's link where the vehicle is, at any time of day, while that order has stops still to be completed on the driver's active route; arrival and departure emails; proof-of-delivery documents, which from that release show the driver's name, the vehicle and the position recorded at the delivery; and the Customer Portal, which shows a customer the name of the driver assigned to its order - and says that the employer can still see the last position recorded before location sharing stops, that a vehicle telematics device is separate from the phone, that the Company Portal assistant can receive drivers' latest positions, that the map on a shipment tracking page comes from OpenStreetMap, and what happens if a company switches off erasure for drivers who delete their own accounts. It starts no new use of personal data: the features it describes are off, or unused, unless the company chooses to use them, and the company must tell its drivers which of them it uses. |
| Version 3.1 | September 27, 2026 | Superseded | Superseded on October 5, 2026 by Version 3.2. Copy available on request. When published it replaced Version 3.0 of September 3, 2026. Corrects and completes the description of what the driver app already does (location sharing, the device identifier, expenses and driving-hours records, the in-app path to Delete Account) and adds a statement that RushHour does not track you. It also explains what Stop sharing does during a route, separates the map and address lookup provided by the phone's operating system from our own providers, says how long driving-hours, expense, issue-report and device-identifier records are kept and that a driver's messages stay with the company after the driver's account is deleted, and describes the deletion grace period as normally 30 days. It starts no new use of personal data. |
| Version 3.0 | September 3, 2026 | Superseded | Superseded on September 27, 2026. It replaced the version dated January 3, 2026. Copy available on request. |
| Earlier version | January 3, 2026 | Superseded | Superseded on September 3, 2026. Not published at its own web address - copy available on request. |
Terms of Service
| Version | Effective | Status | Notes |
|---|---|---|---|
| Version 3.5 | November 4, 2026 | In force | Current version. Replaces Version 3.4 of November 1, 2026. Adds Protecting the RushHour Platform to the General Terms: no copying or cloning the platform, no using it to build or improve a competing product, no bots, scrapers or other automated collection outside our API, no getting around access controls, bot protection or trial and plan limits, and no using the platform to train AI models; the non-public parts of the platform are our confidential information; and what we can do when these rules are broken. The limitation of liability no longer caps a breach of that section or an infringement of RushHour's intellectual property, and either party may bring intellectual-property claims in court instead of arbitration. It took effect on publication for accounts opened from that date and for use of our websites, and takes effect on December 4, 2026 for accounts opened before then, which stay on Version 3.4 until that date. |
| Version 3.4 | November 1, 2026 | Superseded | Superseded on November 4, 2026 by Version 3.5 for accounts opened from that date, and on December 4, 2026 for accounts opened before it. Copy available on request. When published it replaced Version 3.3 of October 15, 2026. Adds section 2a, Card Payments from Your Customers: the payment providers a company can choose (Cardknox with its own merchant account, or Stripe with its own Stripe account, with its own API keys, or with RushHour collecting for it); Stripe's terms for a Stripe account a company connects; how RushHour collects as the company's agent and pays out, less refunds, chargebacks and fees disclosed in advance, and who bears refunds and disputes; how card details are handled; who can take a payment, including API tokens, MCP connections and the in-app assistant with the Charge customer cards permission; card holds, refunds, payment requests, card payments at the stop and phone or mail orders; and the company's responsibilities. It applies to a company from when it turns customer card payments on and changes nothing for a company that does not, so it took effect on publication. |
| Version 3.3 | October 15, 2026 | Superseded | Superseded on November 1, 2026 by Version 3.4. Copy available on request. When published it replaced Version 3.2 of October 13, 2026. Clarifies what happens when a subscription bought online goes unpaid, or a cancelled one ends: the company's office staff can no longer create new quotes and orders until billing is sorted out, while everything else keeps working and its drivers and its own clients are never blocked. Version 3.2 described this as locking the account. For non-payment it still never happens until at least 10 days after Stripe first reports a failed payment, and a company administrator fixes it under Settings > Subscription. It only limits what can happen to an account, so it took effect on publication, and it changes nothing else. |
| Version 3.2 | October 13, 2026 | Superseded | Superseded on October 15, 2026 by Version 3.3. Copy available on request. When published it replaced Version 3.1 of September 27, 2026. Adds the terms for a subscription bought online on rushhourapp.com, where we offer one: it is sold through Stripe Managed Payments (Stripe, through its affiliate Sold through Link, LLC, is the merchant of record and collects any sales tax), the free trial, automatic billing, receipts and invoices, the one-time onboarding fee invoiced separately by us, changing or cancelling under Settings > Subscription > Manage billing alongside cancellation by email, and failed payments. It changes nothing for a customer that does not buy online. |
| Version 3.1 | September 27, 2026 | Superseded | Superseded on October 13, 2026 by Version 3.2. Copy available on request. When published it replaced Version 3.0 of September 3, 2026. Corrects the driver-app location section to match the Privacy Policy (automatic sharing during a route, the in-app Location Sharing switch, what Stop sharing does, and the phone setting that stops all location collection), calls it location sharing rather than location tracking, and corrects the in-app path to Delete Account. It adds no new obligation and no new use of personal data. |
| Version 3.0 | September 3, 2026 | Superseded | Superseded on September 27, 2026. It replaced the version dated January 3, 2026. Copy available on request. |
| Earlier version | January 3, 2026 | Superseded | Superseded on September 3, 2026. Not published at its own web address - copy available on request. |
Data Processing Agreement
| Version | Effective | Status | Notes |
|---|---|---|---|
| Version 1.3 | November 1, 2026 | In force | Current version. Replaces Version 1.2 of October 13, 2026. Adds the card payments a customer can take from its own customers through RushHour, which we are introducing, from when the customer turns them on: the payment providers it can choose, what each receives and what we keep, and who decides about the data in each option - including, where the customer chooses RushHour collects for you, that Stripe is our sub-processor for those payments and that we keep the records of the money we receive and pay out for our own accounting, tax and card-network obligations, as a controller. Extends the description of the processing, the customer's duty to inform its own customers, and the security entry on saved cards. Nothing changes for an account that does not take card payments through RushHour, so it took effect on publication. |
| Version 1.2 | October 13, 2026 | Superseded | Superseded on November 1, 2026 by Version 1.3. Copy available on request. When published it replaced Version 1.1 of September 27, 2026. Most of what it adds describes our platform release of October 16, 2026 and has applied to a customer's account since that release reached it. Driver GPS location points: deleting them becomes a setting in the customer's account; accounts open before that release keep deletion after 90 days switched on, so nothing changes for them, and accounts opened after it start with deletion switched off. Deleted drivers: erasing them becomes two settings in the customer's account; accounts open before that release keep both switched on, so a driver who deletes their own account in the app and a driver deleted by the customer's staff are still erased after the grace period, and accounts opened after it start with erasure of a driver deleted by staff switched off, so those drivers are archived instead. Adds the driver-app chat and call features (voice messages, files and shared locations in chat, online status and last seen, secret chats, voice and video calls), driver ratings, training progress, and the shipment tracking links and live-traffic arrival times a customer can switch on, to the description of the processing, and extends the customer's duty to tell its drivers to cover them. Updated October 25, 2026: the wording "from our next platform release" was removed now that the release is live, and where the date matters the agreement names it as our platform release of October 16, 2026. This is a correction, so the version number stays 1.2 and what the agreement describes has not changed. |
| Version 1.1 | September 27, 2026 | Superseded | Superseded on October 13, 2026 by Version 1.2. Corrections to match the driver app; no new processing. The in-app path to Delete Account, the driver deletion grace period described as normally 30 days, and location points collected while a driver has switched on Location Sharing. Copy available on request. |
| Version 1.0 | September 3, 2026 | Superseded | First published version. Superseded on September 27, 2026 by Version 1.1. Copy available on request. |
Sub-processor list
| Version | Effective | Status | Notes |
|---|---|---|---|
| Published as a standalone page | September 3, 2026 | In force | Before this date the provider list was a section inside the Privacy Policy. The page is updated as providers change, rather than reissued as numbered versions. Updated October 5, 2026: the OpenStreetMap entry now also covers the map on public shipment tracking pages, from our platform release of October 16, 2026, and the fallback map shown when a company's selected HERE, Mapbox or Radar map cannot be loaded. Last updated October 13, 2026, ahead of use: adds, from our platform release of October 16, 2026, Google's public STUN servers (they help two phones connect a voice or video call in the driver app) and Cloudflare's Realtime TURN service (it relays calls that cannot connect directly, in encrypted form), and Stripe, for subscriptions bought online, under May be used; the Google Maps entry adds, from that release, the live-traffic arrival times and the addresses on tracking links. Updated October 16, 2026, with that release: Google's public STUN servers, Cloudflare's Realtime TURN service and Stripe moved to Currently used. Updated October 26, 2026, ahead of use: adds, under May be used, the optional map layers that the dispatch map offers from our next platform release - RainViewer weather radar, U.S. National Weather Service alerts, fuel stations from the Overpass API, and Esri satellite and OpenTopoMap terrain backgrounds. Updated November 1, 2026, ahead of use: adds, under May be used, Stripe for the card payments a company can take from its own customers through RushHour (in the company's own Stripe account, or on RushHour's Stripe account where RushHour collects for the company); the Cardknox entry adds the card holds, saved cards, refunds, payment links and card payments at the stop a company can use, and the name Sola Payments; and the Stripe entry for subscriptions bought online now points to the new entry. Updated November 4, 2026: the Cloudflare entry adds that the traffic to our website and web portals passes through Cloudflare's network, which filters out attacks and automated abuse, and Cloudflare Turnstile, the check that a person is sending our sign-in, sign-up, contact and free-trial forms. |
Account deletion instructions
| Version | Effective | Status | Notes |
|---|---|---|---|
| Current text | October 13, 2026 | In force | Updated alongside Version 3.3 of the Privacy Policy: from our platform release of October 16, 2026, a driver deleted by the company's staff is erased after the grace period where the company's setting for those deletions is switched on - as it is for companies whose account was open before that release, unless they switch it off - and archived where it is off; voice messages, ratings, training progress and the time last seen in chat are added to what stays with the company. Updated October 25, 2026: the wording "from our next platform release" was removed now that the release is live, and where the date matters the page names it as our platform release of October 16, 2026; what it describes has not changed. This is support documentation rather than a contract, so it is dated rather than versioned. |
| Earlier text | October 5, 2026 | Superseded | Superseded on October 13, 2026. Updated alongside Version 3.2 of the Privacy Policy: adds what happens when the company a driver works for has switched off erasure for drivers who delete their own accounts (possible from our platform release of October 16, 2026) - the account is closed and archived instead of erased, and [email protected] will pass the erasure request to that company. This is support documentation rather than a contract, so it is dated rather than versioned. |
| Earlier text | September 27, 2026 | Superseded | Superseded on October 5, 2026. Updated alongside Version 3.1 of the Privacy Policy: the in-app path to Delete Account, the grace period described as normally 30 days, and messages and expenses added to what stays with the company. Copy available on request. |
| Earlier text | September 3, 2026 | Superseded | Superseded on September 27, 2026. Reviewed and updated alongside Version 3.0 of the Privacy Policy. Copy available on request. |
Getting a copy of a superseded version
Superseded versions are held on file, not published at a web address
The text of the January 3, 2026 Privacy Policy and Terms of Service, of Version 3.0 of both (September 3, 2026), and of Version 3.1 of the Privacy Policy (September 27, 2026), is not on this site at its own address. We keep dated copies and will send you one on request.
Email [email protected] and tell us which document you need and either the version number or the date it was in force. We will send the copy that applied, normally within 5 business days. There is no charge, and you do not need an account with us to ask.
If you are asking because of a dispute, a data request or an audit, say so and we will confirm the effective and superseded dates in writing, so the copy stands on its own.
What changed in Version 3.0
Version 3.0 of the Privacy Policy and the Terms of Service, both effective September 3, 2026, is a rewrite rather than a set of amendments. It names the legal entity you are contracting with and its registered office; it stops assuming a United States-only audience, and adds a carve-out so that mandatory local-law rights are not overridden wherever the service is used; it moves the list of providers that process data for us onto its own page and commits to announcing changes to that list; it replaces general statements about retention with the periods we actually apply; and it sets out how account deletion works, including the grace period before erasure and the records that have to be kept. The Data Processing Agreement is new and is published for the first time in this release.
Nothing in Version 3.0 gives us a broader right to use your data than the previous version did. If you want a clause-by-clause comparison against the January 3, 2026 text, ask [email protected].
How we announce changes
- Material changes are emailed. We email the administrators on each business customer account, and post the change here with its effective date.
- Terms of Service changes get 30 days. Material changes to the Terms are notified at least 30 days before they take effect, so you have time to read them or to leave.
- Every document carries its own version and date. The version number and effective date are printed at the top of the document itself, and repeated in the tables above.
- Sub-processor changes are announced separately. The sub-processor page is updated as providers change, and those changes are emailed to subscribers. To subscribe, email [email protected] and ask to be added to the sub-processor notification list.
- Small corrections do not get a new version number. Fixing a typo, a broken link or an unclear sentence does not change your rights or ours. We update the page and the "last updated" date, but the version number stays the same.
- This page is the record. Whenever a document is reissued, the previous version moves into the version history above and is marked superseded on the date the new one took effect.
Who publishes these documents
Rush Hour Logistics System Inc
A business corporation incorporated in the State of New York, USA
New York Department of State ID: 5098884
1272 54th Street, Brooklyn, NY 11219, USA
Legal notices and archive requests: [email protected]
Privacy requests and sub-processor notifications: [email protected]
General enquiries: [email protected]