Privacy Policy

This policy is published in English. Where a translation is offered it is provided for convenience only; if there is any difference, the English version applies. If you would like anything here explained in Hebrew, write to us and we will help.

Who we are

RushHour is operated by Rush Hour Logistics System Inc, a business corporation incorporated in the State of New York, United States on 8 March 2017 and registered with the New York State Department of State under DOS ID 5098884, with its registered office at 1272 54th Street, Brooklyn, NY 11219, United States.

Where this policy says "we", "us" or "RushHour", it means that company. Contact details for privacy questions and for exercising your rights are at the end of this policy.

Where we offer the service

We offer RushHour to business customers in the United States and Israel. The product is in English, it is priced in US dollars, and we sell it to fleets in those two markets. We do not currently target the European Economic Area or the United Kingdom. Under Recital 23 of the GDPR, the fact that a website or an app can be reached from the Union does not by itself mean services are being offered there.

Because we have no establishment in the EEA or the UK and do not target those markets, we have not appointed representatives under Article 27 of the GDPR or the UK GDPR. Before we begin offering the service to customers established in the EEA or the UK we will appoint a representative in each, and name them here. We have kept the EU and UK rights sections below in full, because they describe how we handle a request wherever those laws do apply to you.

There is a second route by which these laws can apply, and we want to be straight about it. The GDPR also covers the monitoring of people located in the Union, and the Driver App records a driver's location while they have an active assigned route or have switched on Location Sharing in the app, and once at certain moments, such as a duty-status change. So if one of our customers has drivers who operate in the EEA or the UK, that location monitoring falls under the GDPR whoever we market to. We will appoint the representatives described above before onboarding a customer whose drivers work in those territories, and the same reasoning applies to the UK GDPR.

Privacy contact

Write to privacy@rushhourapp.com about anything in this policy, to exercise a right, or to raise a concern. It reaches the people responsible for data protection here. It is also the address to use for matters under the Israeli Protection of Privacy Law.

We have not appointed a data protection officer. Our core activities are not large-scale monitoring, and not large-scale processing of special categories of data, on our own account: we run software for our business customers and act on their instructions as their processor. The conditions for a mandatory appointment in Article 37 of the GDPR are therefore not met. If that changes, we will appoint one and say so here.

Our role: who decides what happens to your data

RushHour plays two different roles, and which one applies decides who you should contact.

Data our business customers put into the platform

The trucking, logistics or delivery company that subscribes to RushHour decides what data goes into its account, why, who inside the company can see it and how long it is kept. That company is the controller (in Israel, the owner of the database); we run the software for it and act on its instructions as its processor (in Israel, a holder). This covers its own customers and contacts, orders, stops and addresses, uploaded documents, and its drivers' records, assignments, messages and location history.

If you want that data corrected, exported or deleted, ask that company first. If you ask us, we will pass your request on within 5 business days, tell you we have done so, and help the company answer it - but we cannot act against its instructions except where the law requires us to. We do not use its data for our own purposes and we do not use it to train AI models.

Data we decide about ourselves

For a smaller set of data we are the controller in our own right: the account and contact details of the people authorised to use the platform, subscription and billing records, support correspondence, security and audit logs, product usage data, and information from visitors to our website. This policy is our own notice to you for that data, and requests about it come straight to us.

Business customers subject to the GDPR, UK GDPR, the Israeli Protection of Privacy Law or a US state privacy law can read our Data Processing Agreement, which contains the processor terms, the international transfer terms and a link to our current provider list. Email privacy@rushhourapp.com for a signed copy.

Who this policy covers

• Platform users - dispatchers, administrators and staff at the companies that subscribe to RushHour.
• Drivers - people who use the RushHour driver app for the company that engaged them.
• Our customers' customers and contacts - people whose details are in the platform because a RushHour customer put them there, and people who sign in to a customer portal.
• Website visitors - anyone using rushhourapp.com, including its chat assistant.

For platform users (dispatchers and administrators)

Information we collect

• Account information: name, work email address, phone number, company name, role and permissions, and your sign-in credentials.
• Billing information: billing contact and address, invoices, payment records and the payment token, card brand, last digits and expiry date returned by our payment processor. We never receive your full card number or security code.
• Operational data you enter: customers and contacts, orders, quotes and stops, addresses, vehicles and drivers, documents and photos, and everything else you put into your company's account.
• Communications: in-app messages, email sent and received through the platform, support tickets and correspondence with us.
• Voice recordings: audio you record when you use voice input in the assistant. It is converted to text and is not kept by us afterwards.
• Technical data: IP address, browser and device type, operating system, app or portal version, pages and features used, and cookies needed to keep you signed in.

How we use it

• Provide, host and support the platform for your company
• Authenticate you, enforce permissions and keep accounts secure
• Invoice your company and take payment
• Answer support requests and send service notices
• Detect, investigate and prevent misuse, fraud and security incidents
• Meet our legal, tax and accounting obligations
• Understand how the product is used, in aggregate, so we can improve it

For driver app users

Most of the information below is entered by the company you drive for, or by you during onboarding at that company's request. That company decides which fields it requires.

Information we hold about you

• Identity and contact details: name, email address, phone number, profile photo, home address, date of birth and gender.
• Government and compliance records: driver's licence number, class, issuing state and expiry date; images of your driving licence, vehicle registration card and insurance card; and, where your employer requires it for payroll, tax or insurance purposes, your Social Security number or equivalent national identification number.
• Location: your device's position, including while the app is in the background or closed, while you have an active assigned route or have switched on Location Sharing in the app; the single position recorded with each duty-status change you make and each issue you report; and your position when you switch to yard move or search for nearby places, which is sent to our server for that check or search. See the location section below.
• Work records: assignments, stop-by-stop progress, arrival and completion times, hours, and delivery performance figures.
• Driving hours: each duty-status change you record in Hours of Service (such as driving, on duty, off duty or sleeper berth), with its time, the position where you made it and the nearest city and state, and an odometer reading.
• Expenses: expenses you submit in the app - amount, date, category, vendor, the truck it relates to, how it was paid (for example cash, a fuel card or a check - never a card number), for fuel purchases the fuel type, quantity and the state where you bought it, the odometer reading, any notes, and a photo of the receipt.
• Vehicle and safety records: the vehicle assigned to you, inspection reports, and photos or video recorded in them.
• Photos, media and documents: proof-of-delivery photos, signatures you draw, barcode scans, and incident documentation, including the photos and videos you attach to an issue report, and the photos you take as proof when you collect a payment at a stop, such as a photo of the check or of the person paying.
• Messages and attachments: in-app messages with dispatch and, on some orders, with the customer, including photos you attach and any audio or other files attached to a message. Where your company uses the Telegram integration, messages sent to you over Telegram.
• Device and technical data: device type, operating system, app version, IP address, the push notification token for your phone, and a device identifier that we store with that token so that notifications reach the right phone and stop when you sign out. On iPhone this is the identifier Apple gives our app on your device (the "identifier for vendor"); on Android it is the Android ID; if neither is available, the app creates a random one. It is not an advertising identifier, and it is not used to recognise you in any other company's app. When the app checks for an update, our app-update provider also receives a random identifier for that installation (see the providers below).

Device permissions the app asks for

• Location: to show your route and navigation, confirm stops and let dispatch follow live progress; to record where you were at each duty-status change; to check that you are in one of your company's yards when you switch to yard move; to attach your position and nearest street address to an issue you report; to find nearby fuel, food, parking and other places (your position is sent to our server, which asks the map provider); and, if the company you drive for uses shipment tracking links, to show anyone who has an order's link roughly where the vehicle is - at any time of day, from when that order is put on your active route until its stops are completed - or exactly where, whenever the next stop on your route is one of that order's stops, if the company chooses that. See below.
• Camera: to photograph delivery documents, scan barcodes, capture proof of delivery and record vehicle inspection media; to take photos and videos for an issue report; and to photograph a payment you collect at a stop, such as the check or the person paying.
• Photo library: to attach an existing photo of a document or receipt, and to save a delivery photo if you choose to.
• Microphone: to record sound when you capture a video with the camera to attach to an issue report. The app has no voice recording in chat.
• Notifications: to alert you about new assignments, route changes and messages.

We ask for each permission when you first use the feature that needs it. The app still works if you decline - you lose that feature, not the app.

You can withdraw any of these permissions at any time in your phone's settings (iPhone: Settings > Apps > RushHour, or Settings > RushHour on older versions of iOS; Android: Settings > Apps > RushHour > Permissions).

Optional in-cab features

The app includes an internet radio player and offline puzzle games for use during breaks. Station listings come from radio-browser.info, an independent community service that receives your device's IP address and whatever you type into station search; it receives nothing about you, your employer or your deliveries, and we receive no record of what you listen to. When you play a station, the audio streams from that broadcaster's own server, which receives your device's IP address, as any website you visit would. Neither radio-browser.info nor the broadcasters are our processors, and the app sends them nothing about you, your employer or your deliveries. The games run entirely on your phone and send nothing anywhere. The app uses background audio only while the radio is playing.

Location in the driver app

• Automatic recording starts when a route is assigned to you and has outstanding stops, and stops when the route is finished, unassigned, or when you sign out. Stop sharing also stops it, but only until it starts again on its own - see How to turn location off below.
• Recording you switch on yourself under Location Sharing runs whether or not you have a route, until you tap Stop sharing on that screen or sign out. If you leave it switched on, it starts again the next time you open the app or sign in on that phone. Signing out always stops recording.
• Apart from that, background recording does not run when you have no active route.
• The app also records your position once, at the moment you do something that needs it, whether or not you have a route: when you change your duty status in Hours of Service (driving-hours rules require the location of each change, and the nearest city and state are stored with it), and when you report an issue (the nearest street address is stored with it). These single positions are kept as part of that duty-status log or issue report, for as long as that record is kept - except that when your driver account is deleted and then erased, the position and address on the issues you reported are erased (see Deleting your account). The position on each duty-status change is kept, because the driving-hours log needs it.
• When you switch to yard move, or search for nearby places, the app sends your current position to our server for that check or search.
• We collect latitude and longitude, altitude, direction of travel, speed, the accuracy of each reading and the time. We collect nothing about what else your phone is doing.
• While background collection is running, iPhone shows a location indicator and Android shows a permanent notification, so you can always tell.
• Before your phone asks for background location permission, the app explains in plain language why it is needed. You can decline, and you can change your mind later.
• Menu > Settings > Location Sharing shows whether your position is being shared right now, when the last position was sent, how many positions have been sent, and your location permission - whether your phone allows RushHour to share your location in the background. It does not show where you were.

How to turn location off

In the app, Menu > Settings > Location Sharing > Stop sharing stops all location sharing, including the automatic sharing during an assigned route. If you still have an assigned route with stops to complete, sharing starts again automatically, without you switching it back on: within a few seconds if you had also switched sharing on yourself; otherwise the next time you open the app after it has been closed, when you sign in again, when you receive a route after having none, or when the app refreshes your driver details (for example when you pull down to refresh the Dashboard). Automatic sharing follows the route, and your employer decides what your job requires. To stop all location collection, including during a route, change the permission on your phone:

• iPhone: Settings > Privacy & Security > Location Services > RushHour. Choose "While Using the App" to stop background collection, or "Never" to stop it entirely.
• Android: Settings > Apps > RushHour > Permissions > Location. Choose "Allow only while using the app" or "Don't allow".

The app keeps working for viewing and completing stops, but live location sharing with dispatch, navigation and automatic arrival detection stop. If location is switched off entirely, changing your duty status in Hours of Service asks you to turn it back on, because the driving-hours log needs the location of each change. We do not send your employer a separate alert when you change a device setting; they will simply see that your position is no longer updating, in the same way as if your phone lost signal. Your employer, not RushHour, decides what your job requires.

There is no in-app view of your own location history today: Location Sharing shows whether sharing is on, the time of the last position sent, how many have been sent and your location permission, but not where you were. To get a copy of the location data we hold about you, write to our privacy contact below and we will provide it or route the request to the company that controls it.

If your data reached us through one of our business customers

Most people whose data is in RushHour never signed up for it. You may be a contact at a company that ships or receives goods, or a person a transport company is delivering to, or a customer signing in to a portal your logistics provider gave you.

• Where it came from: the company that uses RushHour entered it, or it arrived in an order, an email or a document they forwarded into the platform.
• What it is: usually your name, your company, your email address and phone number, the pickup or delivery address, and the orders, quotes, documents and invoices connected to you. If you pay through a customer portal, also your billing address and a payment token - we never receive your full card number. If you open a support ticket or use the portal's assistant, what you write.
• Who decides what happens to it: the company arranging your shipment, not us. We hold it for them, on their instructions.
• What we do with it: run the platform for them - dispatch and routing, shipment tracking links where the company uses them, notifications, invoicing and payment, and the AI features described below.
• Your rights: contact that company first. If you do not know who they are, write to us with the order or invoice number and we will identify them and pass your request on.

Website visitors

When you browse rushhourapp.com we process the technical data described above. When you use the chat assistant on the site, what you type is sent to our AI provider in the United States so it can answer you - please do not put confidential information into it. We keep no copy of website chat conversations on our servers. The conversation is stored in your own browser, so it is still there if you come back; clearing your browser's site data removes it.

AI features

Parts of the platform use large language models: an assistant in the Company Portal, an assistant in the Customer Portal, AI help with pricing, documents and email drafting, search over uploaded documents, voice-to-text in the message box, and the assistant on our website. The driver app itself has no AI feature.

• What is sent: the question asked, plus the records needed to answer it. That can include customer and contact names and contact details, pickup and delivery addresses, order, quote and invoice details, driver names and route assignments, the latest recorded positions of drivers and vehicles, and the text of documents uploaded to the platform. Voice notes are sent as audio and converted to text.
• Who receives it: OpenRouter, which passes the request to the model provider configured for the account - today OpenAI or Anthropic. Document search indexing and voice transcription go directly to OpenAI. If a company has supplied its own provider key, requests go to that provider instead. All of them process the data in the United States, under the transfer safeguards described below.
• Training: we do not use your data, or anything typed into an assistant, to train AI models, and the terms under which we use these providers do not allow them to train on it either. Where your company supplies its own provider key, its own agreement with that provider governs instead.
• Human control: the assistant proposes and a person confirms. It does not make decisions about you on its own.
• Turning it off: an administrator at your company can disable AI features for the account.

AI output can be wrong. Prices, routes, summaries and drafts it produces are suggestions - check them before relying on them.

Automated decisions and performance figures

The platform automatically suggests the order of stops on a route, recommends prices, proposes which driver to assign, and calculates delivery performance figures such as on-time rate. These are suggestions: a person at the company using RushHour reviews and confirms them. We do not make decisions about you that produce legal or similarly significant effects without a person involved.

Your employer decides how it uses performance figures, including in employment matters - ask them how. If you believe a decision affecting you was taken purely automatically, you have the right to a human review, to state your side and to challenge the outcome: contact your employer and copy our privacy contact below.

Legal bases for processing (EU and UK GDPR)

Where we are the controller, we rely on the following bases for each purpose:

• Providing and supporting the platform to the company you work for: performance of our contract with that company, and our legitimate interests in running the service (Article 6(1)(b) and 6(1)(f)).
• Creating and administering user accounts, authentication and permissions: performance of that contract and our legitimate interests in controlling access (Article 6(1)(b) and 6(1)(f)).
• Billing, invoicing, collections and financial record-keeping: performance of contract and legal obligation (Article 6(1)(b) and 6(1)(c)).
• Security, fraud prevention, audit logging and incident investigation: our legitimate interests in keeping the service and its users safe (Article 6(1)(f)).
• Service notices, and support correspondence: performance of contract and legitimate interests (Article 6(1)(b) and 6(1)(f)).
• Aggregated, de-identified product analysis: our legitimate interests in improving the product (Article 6(1)(f)).
• Complying with tax, accounting, transport and employment law: legal obligation (Article 6(1)(c)).
• Marketing email to business contacts: consent, or our legitimate interests where the law of the recipient's country permits it (Article 6(1)(a) or 6(1)(f)). You can opt out at any time and we will stop.

Driver location and work data

We do not rely on your consent to collect your location. Consent given to an employer is rarely freely given, so relying on it would not be honest. The transport company you work for decides why and how your location is collected and is the controller for that data. Its basis is normally its legitimate interests in running a transport operation safely, proving deliveries, giving customers accurate arrival times and, where it uses shipment tracking links, showing its customers where their delivery is (Article 6(1)(f)), or a legal obligation such as driving-hours and vehicle-inspection rules (Article 6(1)(c)). We process it only on that company's documented instructions, as its processor.

Your employer must tell you what it collects, why, and for how long, and where it relies on legitimate interests it must have carried out and recorded a balancing test. Ask them for it. If you ask us something we cannot answer because the decision is not ours, we will tell you and pass your request to them.

Location Sharing that you switch on yourself outside an assigned route runs only because you chose it, and you can switch it off at any time in Menu > Settings > Location Sharing.

Companies that process data for us

We do not sell personal data and we do not share it for advertising. We use the providers below to run the service. Each is bound by a written contract that limits it to processing personal data on our instructions and for the purposes in this policy, and requires it to give that data the same or equal protection as this policy, including appropriate security.

The providers we use, in outline

That table is a summary. Our sub-processor page is the authoritative version and the one we keep current: it names every provider individually, says what each receives and where it processes it, and separates the providers used on every account from those used only where a business customer switches an integration on. Which of the optional ones apply to you depends on the company whose RushHour account your data is in - ask that company what it has enabled.

Services your phone's operating system provides. Two things the driver app shows or looks up come from services built into your phone's operating system rather than from a provider of ours. On an iPhone where the company has chosen the phone's standard map, the map on screen is Apple Maps, which receives your phone's IP address and the area of the map being shown. And to find the nearest street address or city for an issue report or a duty-status change, the app uses the address lookup built into your phone's operating system (Apple's on iPhone; on Android, usually Google's), which receives that position. Your phone's operating system provides these under Apple's or Google's own terms. Apple and Google are not our processors for them, and they are not covered by the contracts described above.

We also call a small number of reference services that receive no personal data at all - national fuel-price averages, postal-code and country lookups by place name - and we use Google Cloud and Slack for our own internal cost reporting and alerting, which carry no customer, driver or end-user data.

Other disclosures

• To the business customer whose account your data sits in, and to the people it authorises - including, where it uses these features, its customers who sign in to its Customer Portal, anyone who has a shipment tracking link it issued (a link can be forwarded), and the people it sends delivery notifications or documents to (see What the customers of the company you drive for can see).
• To professional advisers such as auditors and lawyers, under confidentiality.
• In a business transfer - if we are merged with or acquired by another company, or sell assets, your data may transfer with the service. We will say so here beforehand where the law requires it.
• To law enforcement or a regulator where the law requires it, or where it is needed to protect someone's safety. Where we are permitted to, we will tell the affected customer first.

Keeping this list current

We publish any new or replacement provider on our sub-processor page before it starts processing personal data, and that page records the date of the most recent change. Keeping that page current is how we give notice of a change - a new provider, or an existing one taking on a materially different category of data. Business customers can ask to be emailed about changes as well, and may object to a change under our Data Processing Agreement. To be told about changes by email, write to privacy@rushhourapp.com and we will add you to the notification list.

We do not use analytics, advertising or crash-reporting tools in our apps or on our websites. There is no advertising or attribution software in the driver app, no advertising identifier is collected, and the Android build blocks the advertising ID outright. Error monitoring runs on our own servers, not on your device.

Where your data is processed, and international transfers

We run the platform in the United States. Our application servers, the operational database, the search index and the image store are in Amazon Web Services in US East (Ohio); uploaded company documents are stored in AWS in US West (Oregon). Our Customer Portal, Admin Portal and website are hosted by Vercel on its global edge network. We do not operate a hosting region in the EEA, the UK or Israel.

Most of the providers listed above are also in the United States. HERE is in the Netherlands, Sinay in France, CHAMP in Luxembourg, and the OpenStreetMap tile and radio-directory services are community-hosted in the European Union.

If you are in the EEA, the UK or Switzerland

Your data leaves your country. For those transfers we rely on:

• the European Commission's Standard Contractual Clauses (Decision 2021/914) for transfers from the EEA;
• the UK International Data Transfer Addendum to those Clauses, or the UK International Data Transfer Agreement, for transfers from the United Kingdom;
• the Swiss addendum where Swiss law applies;
• and, where the provider receiving the data is certified under the EU-US Data Privacy Framework and its UK Extension, that certification. Ask our privacy contact which basis we rely on for a particular provider and we will tell you.

We have assessed the risk of these transfers and apply encryption in transit, role-based access controls and logging, as described under How we protect data below. You can ask for a copy of the safeguards we rely on by writing to our privacy contact.

If you are in Israel

Your data leaves Israel and is processed in the United States. Before personal data is transferred out of Israel we satisfy ourselves that a ground under Regulation 2 of the Protection of Privacy (Transfer of Data to Databases Abroad) Regulations 5761-2001 applies to that transfer. Every provider on our sub-processor page is engaged under a written agreement that limits it to processing the data on our instructions, requires appropriate security, and restricts onward transfer to the same terms. Write to privacy@rushhourapp.com and we will tell you which ground we rely on for a particular transfer and give you a copy of the relevant undertaking.

How long we keep data

We keep personal data only for as long as we need it for the purpose it was collected for, plus any period we are required to keep it by law or need it to defend a legal claim. The criteria we apply are: how long the account is active, what the record is needed for operationally, what tax, transport and employment law requires, and whether a dispute or investigation is open. The periods below are the ones the platform actually enforces; a business customer can also ask us to delete its own records sooner, and we act on that instruction. Where a period depends on a setting the company controls in its own account, the entry below says so.

• Account and profile data: while your company is a customer. After the account closes we keep it for 30 days, then erase it.
• Driver GPS location points: until our next platform release, a job runs every night and deletes points older than 90 days, for every company. From that release, deleting them is a setting that the company you drive for controls (ask it whether it has switched deletion on), and it is off unless the company switches it on. If it does, the nightly job deletes points older than the period the company sets - 90 days unless it sets another, never less than 30 days, and none at all if it sets 0. Otherwise the points are kept while its account is active. Whatever the setting, your own location points are deleted outright when your driver account is erased (see Deleting your account).
• Hours-of-service duty-status records, including the position and the nearest city and state recorded with each change: kept for as long as the company's account keeps them. They are not removed by the deletion of GPS location points described above, and they are not erased when a driver account is deleted, because transport rules require the company to keep them.
• Expenses and receipt photos a driver submits: kept for as long as the company's account keeps them. Deleting a driver account does not remove them.
• Issue reports: kept for as long as the company's account keeps them. When a driver account is deleted and then erased, the description the driver wrote and the position and address recorded with it are erased; the rest of the report stays with the company.
• Push notification token and device identifier: marked inactive when you sign out, so notifications to that phone stop. The record itself is kept with your driver account and deleted when that account is erased (see Deleting your account).
• Orders, stops, delivery records and proof of delivery: controlled by the business customer; kept while its account is active, then deleted or returned under our Data Processing Agreement. Delivery documentation that evidences a shipment is kept for up to 7 years, because a freight claim can be brought long after the delivery.
• Invoices, payment records and tax records: 7 years, to meet US federal and New York State tax record-keeping requirements.
• Payroll-related records: 7 years.
• Messages, voice notes and email stored in the platform: kept while the company's account is active, and erased with that account. Deleting a driver account does not erase the messages the driver sent and received in the app, or the photos and files attached to them: they stay with the company.
• Uploaded documents, delivery photos and signatures: kept while the account is active. Where a document evidences a shipment, it is kept for up to 7 years for the same reason as delivery documentation above.
• Security, audit and activity logs: the activity log of actions taken in an account - changes to records, sign-ins, email sent, automated jobs - is kept for 365 days, and so is the audit trail of AI-assistant actions and document handling. Records of when a portal user was signed in and online are kept for 180 days. Metering records for AI usage, which show which user triggered which model and what it cost but not the prompt or the reply, are kept for 400 days; the anonymous daily totals derived from them carry no user or record identifiers and are kept indefinitely.
• Server error reports: 90 days.
• Backups: encrypted backups are rotated on our normal cycle, and deleted data ages out of them as that cycle turns over. We do not restore deleted accounts from backup.

How we protect data

• All traffic between your browser or device and our servers travels over TLS (HTTPS), and our API instructs browsers to use HTTPS only.
• Passwords are stored only as salted hashes. Nobody at RushHour can read your password.
• Card numbers and security codes are captured directly by our payment processor's own secure fields and never reach our servers.
• Access is role-based: each person - our staff and your colleagues alike - sees only what their role requires, and every record is scoped to the company that owns it.
• Access to production systems is limited to the small number of our staff who need it, individually credentialed and logged.
• We log administrative actions and access to sensitive records so changes can be traced, and we keep those logs for the periods set out above.
• Credentials a company supplies for its own AI provider are encrypted before they are stored.
• We maintain a documented incident-response process.

We describe only the controls we actually operate. We do not hold a SOC 2 report or an ISO 27001 certificate, and we do not claim one. If your procurement process needs a security questionnaire completed, write to security@rushhourapp.com and we will answer it honestly.

No system is completely secure. We work to protect your data but cannot guarantee it against every possible attack.

If there is a security incident

• Where we hold personal data for a business customer, we notify that customer without undue delay after confirming an incident, with the detail they need to meet their own reporting deadlines, and we help them investigate.
• Where we are the controller, we report to the relevant supervisory authority within 72 hours of becoming aware, where the law requires it, and we notify state regulators within the deadlines their laws set.
• In Israel, we report a severe security incident to the Privacy Protection Authority immediately as required by Regulation 11(d) of the Protection of Privacy (Data Security) Regulations 5777-2017, and follow any instruction it gives about notifying the people affected.
• Where an incident is likely to put you at high risk, we notify you directly and without undue delay, in plain language: what happened, what data was involved, what we are doing, and what you should do. We may delay notice only if law enforcement tells us in writing that it would impede an investigation.

To report a suspected vulnerability or incident, write to security@rushhourapp.com. We acknowledge security reports within one business day.

What your employer can and cannot see

Your employer is the company that gave you access to the driver app and owns the account your records sit in.

They can see:

• your location while you have an active assigned route or have switched on Location Sharing in the app, and the route history it produces;
• the single position stored in its account with each duty-status change you make and each issue you report;
• the position of a vehicle the company has fitted with a telematics device connected to RushHour, which that device reports separately from your phone, whatever your phone's settings;
• your stop-by-stop progress, arrival times, delivery outcomes, proof-of-delivery photos and signatures;
• your working hours, shift attendance and delivery performance figures;
• the expenses and receipt photos you submit;
• your vehicle inspection reports, including any photos or video attached to them;
• the identity and compliance records they hold about you, including your licence, registration and insurance document images;
• the messages you send and receive inside the app, and the photos and files attached to them, including route chats with dispatch. In-app messaging is a work tool and is not private from your employer - please do not use it for anything personal.

They cannot see:

• your current location when you have no active assigned route and have not switched on Location Sharing, or at any time when location is switched off on your phone - though they can still see positions already recorded, such as the last position your phone sent before sharing stopped and the single position recorded when you change duty status or report an issue, and the position of a vehicle fitted with a telematics device (see above);
• anything you do on your phone outside the RushHour app - your personal messages, calls, photos, contacts or browsing;
• what you listen to on the in-cab radio, or anything you do in the in-app games;
• your account password.

We cannot stop your employer from seeing data about the work you do for them while you use their RushHour account, and we cannot remove records that belong to them. If you have questions about what your employer does with these records, or about being monitored at work, raise them with your employer - and see the rights sections below for how to take it further.

What the customers of the company you drive for can see

Some features let the company you drive for keep its own customers informed about their deliveries. Each of them is off, or unused, unless that company chooses to use it, and the company decides who receives what. As with everything else it collects about you, the company must tell you which of them it uses (see Driver location and work data above) - ask it if it has not.

• Shipment tracking links. If the company switches tracking links on, it can give a customer - or anyone else it chooses - a link to a web page about one order, by copying the link or by email, and it can have links emailed automatically. Anyone who has the link can open the page without signing in, and a link can be forwarded. The page shows the order's stops on a map and how the delivery is progressing, including the times you arrived at and left each of the order's stops and, whenever the next stop on your route is one of them, an estimated arrival time calculated from your phone's latest position. While the order has stops still to be completed on your active route, the page can also show where the vehicle is, using the latest position your phone sent in the last 20 minutes. This does not depend on the time of day, on the date the stops are scheduled for, or on whether you are on duty: your phone keeps sending its position while your route has stops still to complete (see Location in the driver app above), so it can apply from the moment the order is put on your active route - which can be days before the delivery - until its stops are completed, including on breaks, before or after your shift and while you are at other customers' stops:
  • by default, only an approximate area, about 1 km across;
  • if the company chooses, no map position - only which of the order's stops was completed last, and when. The estimated arrival time still shows, and because it is worked out from your phone's position it reveals roughly how far you are from that stop;
  • if the company chooses live position, your exact position, direction of travel and the accuracy of the reading, with the page updating about every 15 seconds - whenever the next stop still to do on your route is one of that order's stops, even if you will not reach it until a later shift, and you are more than 2 km from any of its stops whose address is hidden from the page; at other times the page shows the approximate area instead.
  The page never shows your name, phone number, photo or vehicle, and never shows a history of your positions - only the latest one. A link stops working when it expires (after 30 days, unless the company sets a different period of up to a year), when the company revokes it, or when the company switches tracking links off. It does not stop working when the delivery is complete.
• Arrival and departure emails. If the company switches these on, its customer can be emailed when you arrive at or leave one of its stops, with the time and, unless the company leaves them out, your name and phone number.
• Proof-of-delivery documents (from our next platform release). A proof-of-delivery document the company produces in RushHour shows your name, the vehicle's name and plate number, your arrival, departure and waiting times at the stop, and the delivery photos and signature, and it can show the position your phone recorded closest to the moment you completed the stop (within 10 minutes of it), with its time and accuracy. The company can send the document to its customer, and can have it sent automatically when you complete a delivery.
• The Customer Portal. Customers who sign in to the company's Customer Portal can follow their own orders there: the planned route, the stops, how the delivery is progressing, and whether a driver has been assigned and that driver's name. The Customer Portal does not show where the vehicle is. Where the company emails tracking links automatically, its customers can also choose there to receive them.

Cookies and similar technologies

Our websites and portals use only what is needed to make them work: keeping you signed in, remembering your language and light or dark preference, and protecting against abuse. We use no advertising or analytics cookies and no trackers, which is why you are not asked to accept a cookie banner.

Our Company Portal loads fonts and icons from Google Fonts, Font Awesome and the unpkg content network, which means those providers receive your browser's IP address when a page loads. They set no cookie for us and receive no application data.

If we ever add analytics or marketing technology, we will update this section and ask for your consent first where the law requires it.

Your rights if you are in the EEA or the UK

You can ask us to: give you a copy of your data; correct it; delete it; limit how we use it; send it to you or another provider in a portable format; and stop using it where we rely on our legitimate interests.

• You can object at any time, and for any reason, to your data being used for direct marketing. We will stop.
• Where we asked for your consent you can withdraw it at any time. That does not make what we did beforehand unlawful.
• You have the right to complain to a data protection authority: in the EU, the authority where you live, where you work or where the problem happened; in the UK, the Information Commissioner's Office. We would rather you came to us first, but you do not have to.

How to use these rights: email our privacy contact with your name, the email address on your account and what you want. There is no charge. We answer within one month; if your request is complex we may take up to two further months and will tell you within the first month if that happens. If your data is in the platform because a transport company put it there, that company decides - we will forward your request to them within 5 business days and tell you we have done so.

Your rights if you are in Israel

Whether you have to give us your data (Section 11)

• Drivers: the company you drive for is required by transport, tax and employment law to hold some of this data about you, and we hold it for them. Your name, contact details, licence details and your location while you have an active assigned route are needed to use the driver app for work. You are not legally obliged to give them to us, but without them your employer cannot dispatch you through RushHour.
• Platform users: giving us your name, work email and company details is voluntary, but we cannot open or run your account without them.
• Our customers' customers: the data we hold about you came from the company arranging your delivery, not from you. Ask that company to correct or remove it, or ask us and we will pass the request on.

The purposes for which we hold data, and the recipients it is delivered to, are set out in the sections above.

Access and correction (Sections 13 and 14)

You may ask to see the data we hold about you, and to have it corrected or deleted where it is incorrect, incomplete, unclear or out of date. Write to our privacy contact with your name and the email address on your account. We will reply within 30 days. If we refuse, we will tell you why in writing, and you may apply to a Magistrates' Court under Section 15. You may also complain to the Israeli Privacy Protection Authority (הרשות להגנת הפרטיות) at the Ministry of Justice.

Database security and notification

Where a company puts data into RushHour, that company is the owner of the database and we are its holder. Registering or notifying that database, and classifying it under the Protection of Privacy (Data Security) Regulations 5777-2017, are the owner's responsibilities; we give our business customers the information they need to do it, and our Data Processing Agreement sets out what we do as holder. For the account, billing and support records we hold in our own right, we apply the access controls, logging and incident handling described under How we protect data above. Write to our privacy contact if you need security information for your own compliance file.

Direct mailing

We only send marketing email to business contacts who have agreed in advance to receive it. Every marketing message is marked as an advertisement, names us and gives our postal address and a contact address, and carries a one-click unsubscribe link. You may ask at any time to be struck from our direct-mailing database and we will remove you and stop sending; on request we will tell you where we obtained your contact details. Operational email - route assignments, delivery notifications, invoices and payment requests, password and invitation links, security notices and notices about changes to this policy - is not marketing and cannot be switched off while your account is active.

Your rights if you are in the United States

If you live in California, Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana or another state with a comprehensive privacy law, you may ask us to confirm whether we process your personal information and give you a copy; correct it; delete it; provide it in a portable format; and, in California, limit the use of sensitive personal information.

We do not sell or share your personal information

We have not sold personal information, and have not shared it for cross-context behavioural advertising, in the preceding 12 months, and we do not do so today. We use no advertising software, no advertising cookies and no advertising identifiers. Because we neither sell nor share, a Global Privacy Control signal has nothing to opt you out of - we recognise it and there is no sale or share to stop. If that ever changes we will honour Global Privacy Control as a valid opt-out and publish a "Do Not Sell or Share My Personal Information" link before any such use begins.

Sensitive personal information

We collect Social Security numbers, driver's licence numbers and precise geolocation, and we use and disclose them only to run the transportation operation the business customer uses RushHour for - never to infer characteristics about you. Because we do not use them beyond the purposes permitted by California law, the right to limit their use does not apply; you can still ask us to delete them.

Non-discrimination, agents and appeals

• We will not deny you service, charge you a different price or give you a lesser service for exercising these rights.
• An authorised agent may act for you with your written, signed permission; we may still ask you to confirm your identity with us directly.
• We respond within 45 days and may extend once by a further 45 days, telling you why.
• If we refuse a request in whole or in part, you may appeal by replying with "Appeal" in the subject line. We will decide within 45 days and, if we still refuse, tell you how to complain to your state Attorney General.

Many of these state laws do not cover information about you in a purely employment or business-to-business context, and California's law does. Where an exemption applies to your request we will tell you which one and, where we practically can, honour the request anyway.

Our sites do not respond to browser Do Not Track signals, because we do not track users across other companies' apps or websites (see We do not track you above). We do not disclose personal information to third parties for their own direct marketing.

Biometrics and driving records

We do not collect, capture, store or use biometric identifiers or biometric information. Signatures you draw at a delivery, and photographs taken for proof of delivery, vehicle inspection or payment collection, are stored as images only - we do not run face recognition on them, derive a face, hand, voice, fingerprint or iris template from them, or use them to identify anyone. Voice notes are transcribed to text and are not used to build a voiceprint. We also do not obtain personal information from state motor vehicle records and do not run driving-record or background checks - licence details come from you or from the company you drive for.

Your rights wherever you are

Whatever country you live in, you can ask us for a copy of the personal data we hold about you, ask us to correct it if it is wrong, ask us to delete it, ask us to stop using it for a particular purpose, or ask us how it reached us. Where the data belongs to one of our business customers we will route your request to them and help them answer it. We do not charge for this, and we will not treat you differently for asking.

Children's privacy

RushHour is a business service for commercial transport operations. It is not directed at children, it is not intended for anyone under 18, and we do not knowingly collect personal information from anyone under 18. If you believe a child has provided us with personal information, contact us and we will delete it from our systems.

Deleting your account

If you use the RushHour driver app, you can start account deletion from inside the app: tap the menu button (☰) at the top left, tap Settings, tap Privacy, tap Delete Account, then confirm with Delete. Typing "delete account" into the app's search also takes you to the Privacy screen. You do not need to email us. The app first checks that you have no route still assigned to you and no outstanding payments on your account.

Your access ends immediately. The deletion then has a grace period (normally 30 days), during which the company you drive for can restore your account and cancel the erasure. After that we erase your personal records, and the erasure completes within 30 days of the grace period ending. From our next platform release, the company you drive for can switch off erasure for drivers who delete their own accounts. If it has, your account is closed and archived in that company's account instead of being erased: your personal records, including your location history, are not erased and stay with that company, under its own retention settings. In that case, write to privacy@rushhourapp.com and we will pass your erasure request to that company and help it respond. Some records survive, either because the law requires them or because they belong to the company you drove for: that company's delivery, route, proof-of-delivery and vehicle inspection records, in which your name can appear; the hours-of-service and inspection compliance records transport rules require it to keep, which remain attached to a record that no longer names you; the messages you sent and received in the app, and the photos and files attached to them; the expenses and receipt photos you submitted; payroll, invoicing and tax records, kept for 7 years; and records under a legal hold or needed for an open dispute, audit, insurance claim or regulatory request, until that is resolved.

Full instructions, what is erased, what is kept and why, and an email route for people who can no longer sign in are on our Delete Your Account page.

Portal users: your account is managed by your organisation's administrator, who can remove it. To close an entire company account, an authorised administrator should write to us from a company address - we confirm the request before acting on it, because closing the account affects every user and driver on it.

Contact us

If you have questions about this Privacy Policy or our data practices, or want to exercise a right, contact us:

We acknowledge privacy requests within 5 business days, answer rights requests within one month (45 days for US state privacy requests), and reply to general enquiries within 2 business days.

Changes to this policy

We update this policy as the product and the law change. When we do, we update the version number and the dates at the top of this page, and the version it replaces is listed in our legal archive, where you can see which document applied on a given date.

For changes that materially affect your rights - a new purpose, a new category of data, or a new provider receiving personal data - we tell account administrators by email and in the product at least 30 days before the new version takes effect, and we tell you before any new use of personal data begins. Minor corrections take effect when posted.