Skip to content
haul.rocks

Draft for legal review. This page is not yet in effect and is hidden from search engines.

Privacy Policy

Last updated [date]

This policy explains what information haul.rocks collects, how it is used and shared, and the choices you have.

Who we are

haul.rocks is dispatch software for dump truck and aggregate haulers, operated by [legal entity name], [address] ("we", "us"). Questions about privacy: sales@haul.rocks.

Haulers who subscribe ("customers") decide what information to put into haul.rocks about their own staff, customers and jobs. For that information we act as their service provider (processor) and handle it only to run the service for them. For our own account, billing and website information we are the controller.

What we collect

  • Account details: names, work email addresses, mobile numbers and roles of the people a customer adds (admins, dispatchers, drivers).
  • Dispatch information a customer enters: jobs, trips, its customers' names and contacts, yards, quarries and jobsite addresses, materials, trucks, rates, invoices and subcontractor pay statements.
  • Driver work records: clock-in and clock-out times for each load, load ticket numbers and tons, photos of scale tickets, and the name and signature of the person who received a load.
  • Location: while a driver is clocked in on a load and has the driver app open, the phone shares its position so the dispatcher can see where the truck is and when it arrived at or left the pit and the jobsite. We keep only the latest position for each load, not a history of where the driver went, and nothing is collected while the driver is clocked out.
  • Requests from the public: when someone fills in a hauler's request form, their name, email, phone, job location and description.
  • Billing: your plan and subscription status. Card details are collected and stored by our payment processor, Stripe; we never see or store full card numbers.
  • Technical information: sign-in sessions, IP addresses in server logs, and the push-notification address of devices where a user turned notifications on.

How we use it

  • To run the service: build and share the day's schedule, send drivers their loads, record time and tickets, invoice, and pay subcontractors.
  • To send the messages the service depends on: schedules, invites, password resets, job offers, request confirmations and invoices, by email, text message or push notification.
  • To bill for subscriptions, prevent abuse (for example, rate limits on public forms) and keep the service secure.
  • To understand how the product is used in aggregate (for example, how many dispatch days are finalized each week) so we can improve it.

We do not sell personal information, and we do not use customer data for advertising.

Text messages (SMS)

Haulers use haul.rocks to text their drivers work information: invitations to set up an account and the loads they are scheduled to run. A hauler adds a mobile number only for people who have agreed to receive these work texts. Message frequency varies with the work schedule, usually no more than a few messages a day. Message and data rates may apply.

Reply STOP to any message to stop receiving texts, or HELP for help. After STOP, schedules continue by email or in the app.

Mobile numbers and text-messaging consent are not shared with third parties or affiliates for their marketing or promotional purposes. We share them only with our messaging provider (Twilio) to deliver the messages.

Who we share it with

Inside the service, information is shared only as the hauler sets it up: a prime contractor's jobs are visible to the subcontractors it offers them to (without its other subcontractors or its customer rates), and a hauler can give its own customer a private link showing that customer's loads, tickets and invoices.

We use these service providers, under contracts that limit their use of the data to providing their service to us:

  • MongoDB Atlas (database hosting)
  • Amazon Web Services (application hosting and private storage for ticket photos)
  • Stripe (subscription payments)
  • Mailgun (email delivery)
  • Twilio (text message delivery)
  • Browser push services operated by Apple, Google and Mozilla (push notifications, when a user turns them on)
  • [Timebridge, when a hauler turns on the time-tracking add-on: drivers' clock-in and clock-out times]

We may also disclose information if required by law, or to protect the rights and safety of our users or the public.

How long we keep it

We keep a customer's information while its account is active. After an account is closed we delete or anonymize it within [90] days, except records we must keep for tax, accounting or legal reasons, such as invoices. Ticket photos are deleted when the ticket they belong to is deleted. Private links (request status and customer portal) stop working when the hauler turns them off or makes a new one.

Security

Connections are encrypted (HTTPS). Passwords are stored only as salted hashes. Private links and invites store only a hash of their token. Ticket photos sit in a private storage bucket and are shown through links that expire within minutes. Each hauler's data is kept separate, and every request is checked against the signed-in user's company and role. No system is perfectly secure; if we learn of a breach affecting your information we will notify you as the law requires.

Your choices and rights

Drivers and other staff should contact the hauler they work for first, since the hauler controls their information in haul.rocks; we will help the hauler respond. You can also contact us directly. Depending on where you live (for example, California), you may have the right to know, access, correct or delete personal information, and not to be discriminated against for exercising these rights. We will verify a request before acting on it.

Location sharing can be turned off in the phone's browser settings at any time; the rest of the driver app keeps working. Push notifications can be turned off the same way.

Children

haul.rocks is a business service and is not directed to children under 16. We do not knowingly collect their information.

Changes

If we change this policy in a way that matters, we will tell account admins by email or in the app before the change takes effect.