Privacy Policy

Blackridge Dispatch is used by hauling companies (our customers) to run dispatch, tickets, settlements and invoicing.

• For the operating data a customer puts into the app, such as its drivers, dispatches, tickets, photos, settlements, customers and invoices, the customer company is in control of that data and we process it on the company’s behalf, following its instructions. In privacy-law terms, the company is the controller and we are its processor.
• For our own account and billing relationship with a customer, such as the admin’s login and billing contact, and for enquiries sent through our website, we decide how the information is used. For that information, we are the controller.

Company admins (the person who signs up):

• name, email address and password (the password is handled by our authentication provider and we never see it in plain text);
• the company name and, if the admin adds them in Settings, the company’s address, phone number, MC and DOT numbers and billing email. The company chooses which of these print on its documents;
• a record that the admin agreed to our Terms of Service and this policy, with the date and the version agreed to;
• billing details: our payment processor, Stripe, receives the company name, the admin’s email and the number of active drivers. Card and bank details are entered directly with Stripe and never reach our servers.

Office users (dispatchers): the same login details as an admin (name, email, role). Adding dispatchers through the app is not available yet.

Drivers, as entered by their company:

• name, email address, phone number, employee ID, and whether they are an employee or a vendor’s driver;
• truck and trailer details: truck number, year, make, model, colour, licence plate, VIN and MC number; trailer type, capacity, plate and VIN; overweight permit; and any notes the office adds;
• a login account, created when the driver accepts an email invitation and sets a password.

We do not collect drivers’ Social Security or tax numbers, dates of birth, driver’s licence numbers, home addresses or bank details.

What drivers create in the driver app:

• tickets: the ticket number, the weight or quantity, and a photo of the scale ticket, taken with the phone’s camera or chosen from its photo library;
• the time a ticket is saved and submitted, and the times the driver accepts or declines a dispatch or updates its status (for example loaded, delayed or completed), with any reason the driver types in;
• pay records the company produces from this work: settlements showing gross pay, the driver’s share, deductions and net pay.

Location: the app does not collect the location of drivers’ phones. It does not use GPS tracking or the phone’s location services. The pickup and delivery coordinates on a dispatch are typed in by the office to describe the job site. Ticket photos have their embedded metadata, including any GPS location the camera recorded, removed before they are uploaded. PDF files uploaded by the office are stored as they are.

Customers, brokers and vendors, as entered by the company: names, contact names, email addresses, phone numbers, pit and job-site addresses, purchase-order and work-order numbers, and the invoices, manifests and ticket photos sent to them.

People who open a share link: when someone opens a share link a company has sent them, we record only that the link was opened: a count and the time of the most recent opening. We do not record their IP address, browser or identity, and they do not need an account.

Website enquiries: if you use the Request Access form, we collect your company name, your name, email address, phone number if you give it, and fleet size, and we email them to our sales inbox so we can reply.

Technical information: our hosting and database providers keep standard server and security logs, which may include IP addresses and browser type. These are kept for the provider’s standard period, typically 30 to 90 days. When the app hits an error, we send an error report to our error-tracking provider (see below).

• to provide the service: dispatching, tickets, settlements, invoices, reports and share links, for the company that entered the data;
• to send the emails the service depends on: driver invitations, password resets, account approval notices, and dispatch-decline notices to the company’s admins;
• to bill the company, through Stripe;
• to answer support requests and website enquiries; and
• to keep the service secure, and to diagnose and fix errors.

We may use anonymised, aggregated data that cannot identify a company, a driver or a customer, to improve the service and to publish industry benchmarks.

We do not sell personal information. We do not share it for advertising. We do not use customers’ operating data for any purpose of our own other than running and improving the service, and the anonymised, aggregated use described above.

We use these service providers (subprocessors) to run Blackridge Dispatch. Each receives only what it needs for its purpose:

• Supabase: database, user logins, and file storage for ticket photos, settlement PDFs and shared documents. Region: us-west-2 (Oregon, United States).
• Vercel: hosts the website and the app, and runs our server code. Region: United States.
• Stripe: subscription billing and payment processing. Receives the company name, the admin’s email, the active driver count, and the payment details entered at checkout. United States.
• Resend: sends every email from the service: driver invitations, password resets, account approval notices, dispatch-decline notices to admins, and website enquiries to our sales inbox. Receives the recipient address and the email content. United States.
• Driver invitations and password resets are generated by Supabase’s login service and delivered through Resend.
• Sentry: error tracking. An error report contains the technical details of the error, the page address without its query string, and random internal ID numbers for the user and company. We have configured it not to receive names, email addresses, IP addresses, cookies, form contents or database records, and not to record screen sessions. Region: United States.

Your company’s own documents go where your company sends them. For example, share links and invoices go to the customers and brokers your company chooses.

We may also disclose information if the law requires it, to protect the rights or safety of people or the service, or as part of a merger or sale of our business, in which case this policy continues to apply to it.

• Company data is kept while the company’s account exists. It is not deleted automatically, including after a subscription ends: a cancelled or unpaid account becomes read-only and its data stays readable and exportable by the company. If we ever need to remove an account’s data, we give the account admin at least 30 days’ notice by email first. Everything below that is kept "until the account’s data is removed" follows this same rule.
• When a company archives a driver, the driver’s login is blocked straight away, and their details, tickets and settlements are kept as part of the company’s records. A company can permanently delete a driver only if that driver has no dispatches, tickets or settlements.
• When a driver discards a draft ticket, the ticket and its photo are deleted. When a photo is replaced, the old photo is deleted. Photos of tickets that the office deletes are retained until the account’s data is removed.
• Share links stop working after 7 days, or sooner if the company revokes them. The shared files are retained until the account’s data is removed.
• The link in a driver invitation email expires after 24 hours.
• Signups we decline are marked declined and retained until the account’s data is removed.
• Website enquiries are kept until the enquiry is resolved, then deleted within 90 days.
• Error reports are kept by Sentry for the provider’s standard period, typically 30 to 90 days.
• Billing records are kept by Stripe and by us as long as needed for tax and accounting law.
• Database backups are kept by Supabase for the provider’s standard period, typically 30 to 90 days, so deleted data can remain in a backup until it ages out.

Each company’s data is kept separate from every other company’s by database access rules (row-level security) enforced by the database itself, and by server checks on every request. A user can only reach their own company’s data, and drivers can only reach what the app shows them.

Data is encrypted in transit (HTTPS) and encrypted at rest by our database and storage provider. Photos and documents are kept in private storage and opened through links that expire after a short time.

No system is perfectly secure. If we learn of a breach affecting personal information, we will notify the affected company without undue delay and as the law requires.

Because each company controls its own data in the app, requests to see, correct or delete personal information held for a company should go to that company’s admin first. The admin can edit or archive most records directly. We will help the company respond.

For information we hold as controller (the admin account, billing contact, or a website enquiry), contact us at support@blackridgedispatch.com.

Depending on where you live, you may have legal rights over your personal information, including under the Texas Data Privacy and Security Act [[CONFIRM: legal: whether and how the TDPSA applies to us, and the thresholds]]. We will respond to requests as the applicable law requires.

Your employer, or the company you haul for, added you to Blackridge Dispatch. That company controls your information in the app: it decides what is entered about you, can see your tickets, photos and settlements, and can change or archive your record.

If you have a question about your information, or want it corrected or removed, contact that company first. If you cannot reach them, write to us at support@blackridgedispatch.com and we will pass your request to them.

The driver app does not track your location.

Blackridge Dispatch is a business tool and is not intended for anyone under 18. Every user, including drivers, must be at least 18. We do not knowingly collect information from children.

We use one cookie, to keep you signed in. It lasts up to 7 days. The app also keeps your sign-in session in your browser’s local storage, and the driver app briefly saves a ticket you are typing so it is not lost if the page reloads. That saved ticket is cleared when the tab closes.

We do not use advertising cookies or third-party analytics, and we do not track you across other websites.

If we change this policy in a way that matters, we will email account admins before the change takes effect and update the date at the top of this page.

Privacy questions and requests: support@blackridgedispatch.com. We are contacted by email only.