HaulFinder Privacy Policy

Last updated: November 5, 2026

HaulFinder is a Chrome extension for truckload dispatchers, operated by Novil Prime LLC ("we", "us"), 30 N Gould St Ste R, Sheridan, WY 82801, USA. It works on the DAT One (one.dat.com) and Truckstop (main.truckstop.com) load boards inside the user's own signed-in session. This policy explains what the extension reads, what stays on your computer, what reaches our server, what happens when you connect a Gmail account or sign in with Google, who else receives anything, and how to reach us.

Questions or requests: support@haulfinderapp.com.

Summary

• Your loads, notes and settings stay in your browser.
• Our server receives your work email (to sign you in and match you to your company's seat), a sign-in session, the map points of the road routes it draws for you and short error reports and counts of how the extension is working; with a licence check it may also receive a small health note (the extension's version, which view is open, and counts of the load board's answers — never their content). If you sign in with Google, it also receives your name from your Google profile, which it shows back to you in Settings and uses for nothing else.
• If your company uses HaulFinder's company features, our server also keeps what the company puts there — its team list (work emails, roles, last sign-in times), its broker list and its phone-app defaults — and a history of who changed what (section 3a).
• If your company moves you to HaulFinder from the browser extension it used before, our server holds a copy of what you set up there until you take it or it expires (section 3b).
• If you connect Gmail, HaulFinder can only send email — never read it. Google's permission for that is stored on our server encrypted; the messages themselves go from your browser straight to Gmail, and only when you press to send them: HaulFinder never sends an email by itself.
• Google user data — what HaulFinder receives from Google, and how it uses, stores, shares and deletes it, permission by permission: section 4c.
• If you connect RTS Pro, your browser asks RTS Pro for the credit of the brokers you look at, with your own RTS Pro sign-in, which the extension keeps in its own storage in your browser until you disconnect (or RTS Pro stops accepting it) and renews for you, without your password, when you look up a broker. None of it reaches our server.
• HaulFinder reads the loads on DAT One and Truckstop in your browser. On each board it also sends that board a few requests of its own for you, with your own session, such as the next page of results: section 2 lists them.
• Your DAT One and Truckstop sign-in tokens stay in your browser's memory. They are never saved and never sent to us.
• We do not sell data, show ads, or run analytics or tracking code.

1. What stays in your browser

HaulFinder keeps the following in your browser's extension storage (chrome.storage and IndexedDB). It is not uploaded to us, and Chrome deletes it when you remove the extension.

• Notes you add to loads, the loads you have already seen and when you first saw them (so a re-posted load does not look new), and your saved searches.
• Your settings — columns, filters, highlights, truck costs, fuel price and MPG — and your email templates, each with the signature you give it (your name, contact details and a logo image, if you add them).
• Your HaulFinder sign-in: your work email, your company and seat identifiers, a session token and, if you signed in with Google, your name from your Google profile. Signing out (the Cabinet's Sign out, or Logout in Settings) removes it from the browser and ends the session on our server.
• The latest signed licence from our server, so a short network outage does not lock you out.
• Your company's broker list and phone-app defaults, as read from our server (section 3a), so the broker tags show on loads and a phone number opens the right app. A copy belongs to one signed-in account and is never shown to another account on the same browser; it is replaced whenever the server's version changes.
• What you imported from a previous extension (section 3b): the templates and signatures join your own; the broker reviews you wrote there and its board settings are kept in the browser exactly as they came, because once our server's copy is deleted they exist nowhere else.
• If you connect Gmail: the list of connected addresses (address, display name, when connected — no tokens), a record of each email you send from HaulFinder (the sending address, the recipient, the subject, the load, the time and whether it went through), and — only until Chrome closes — which loads you emailed in this browser session, so their buttons still show it after a reload.
• If you connect RTS Pro: the access token and, if RTS Pro issues one, the refresh token of your own RTS Pro sign-in, in the extension's own storage, until you disconnect, remove access to rtspro.com or RTS Pro stops accepting the refresh token (section 4a).
• A short log of each load board's recent HTTP status codes, used to slow down or stop when the site is rate-limiting, and a short queue (at most 50 entries) of error reports waiting to be sent to us (section 3).
• Cached road routes for loads you have opened, so an opened route draws again without a request.

2. The load boards and your sessions

HaulFinder reads the loads shown on the load board — lanes, dates, rates, equipment and the broker's contact details — in your browser, to calculate figures such as rate per mile and estimated profit. This content is not sent to our server (the only exception is the map points of a route HaulFinder draws for you, see section 3).

On DAT One, to show your own results, HaulFinder uses the authorization token your browser already sends to DAT One for your session, for the same kinds of requests the page makes for you: place suggestions while you type, the next page of results when you scroll to the end of the list, and a refresh when you ask for one or turn on automatic refresh (off by default, never more often than every 30 seconds, only while the tab is visible). It works at the pace of a person using the page, and it stops at once if the site reports a limit or asks you to sign in again. The token is kept in memory only: it is never written to disk, never logged, and never sent to us or anyone else. HaulFinder never asks for, sees or stores your DAT One password.

On Truckstop (the load search page at main.truckstop.com), HaulFinder reads the answers to the requests the page makes for you: your searches and the page's own repeats of them, their counts, your search tabs, a load's details, Truckstop's rate estimate for a load, the loads you hid and the loads on your compare list. Of the compare list and the hidden loads it keeps only the load identifiers, and only in memory, for the life of the page. With Advanced View off, which is how HaulFinder starts on Truckstop, it sends Truckstop no request of its own. When you switch Advanced View on, your board takes the place of the page's table, and HaulFinder sends Truckstop these requests, with the authorization token the page itself uses:

• one search after each new search on the page: the same search at the same radius, or, for a search with no origin, the first page of the same search;
• the next page of results when you scroll to the end of the list;
• the first page again when you ask for a refresh or turn on automatic refresh (off by default, never more often than every 30 seconds, only while the board is on screen and the tab is visible);
• a load's details when you open its card;
• when you press hide or pin (or undo them) on a load that the page's own table does not hold, the same request the page's button would send. For a load in that table, and for the compare star of any load, HaulFinder presses the page's own button.

If you turn on Click city to search or Default equipment in Settings, HaulFinder fills in Truckstop's own search form for you and, for a city, presses its search button. It works at the pace of a person using the page, and it stops at once if Truckstop reports a limit, refuses a request or asks you to sign in again. The token is kept in memory only, in the script on the page: it is never written to disk, never logged, and never sent to us or to anyone but Truckstop. The search the page sends carries your company's account numbers at Truckstop; HaulFinder reads them there and uses them only in the requests above. HaulFinder never asks for, sees or stores your Truckstop password.

3. What reaches our server, and why

Our server is hosted by Railway (railway.com) at api.haulfinderapp.com, in Railway's EU West region (Amsterdam, the Netherlands) — outside the United States. It receives:

• Your work email address — to send you a one-time sign-in code and to match you to the seat your company holds. We keep your email, your company and seat identifiers, your role (admin or member), the time of your last sign-in, your company's plan and number of seats and, if your company pays by card, the identifiers Stripe gives its customer and subscription and the subscription's status.
• Where your company heard of us, if it buys on our website — the short code of the link that brought you to our website, if the link carried one (for example ?ref= in a link we posted), and your answer, if you give one, to the optional question "How did you hear about HaulFinder?" on the payment page. We keep them with your company's account to learn which of our announcements work; the code also travels with the payment to Stripe, where you type the answer (section 5). Our website stores nothing in your browser for this: it carries the code from the page's own address into the payment link.
• Your name, if you sign in with Google — the name on your Google profile, kept with your seat so HaulFinder can show it back to you. See section 4b.
• Sign-in codes — six digits, valid for 10 minutes, and at most 5 attempts. We store only a cryptographic hash of the code, never the code itself. The code is delivered to your inbox by our email delivery provider (section 5).
• Your sign-in session — after you sign in, your browser holds a session token and we store only its hash, together with your email and when the session was created and last used. A session ends when you sign out, after 90 days without use, or when your company's administrator revokes it.
• Licence checks — while the extension runs, it presents its session to our server about every five minutes and receives a signed licence (valid for 15 minutes) that unlocks your plan's features. With a check the extension may also tell us its version number, which view is open (Advanced View or the standard one) and how many answers the load board's site gave of each kind over the last few minutes (for example how many were accepted and how many refused) — numbers and fixed words only, never a load, a lane, an address, a name or a token. For each seat our server keeps just the time of its latest check and the extension version that made it — one record per seat, replaced by the next — so that we can see the service is healthy and which installations are out of date.
• Route requests — to draw a load's road route (in its card, or in a row's small map and a moment ahead when you point at that row), the extension sends our server the coordinates of the route's points — the load's pickup and delivery and, for the empty miles before and after it, where your search starts and ends — with your session. No load, rate, broker or other personal data is sent. Our server asks a road-routing service for the route — openrouteservice first, then Stadia Maps, then Geoapify (section 5) — and keeps the result in a cache, shared by all users and keyed by the coordinates, for up to 14 days. A route from Stadia Maps is not kept on our server.
• Diesel price — the card's fuel cost starts from the U.S. average retail diesel price that the U.S. Energy Information Administration (EIA) publishes each week, until you enter your own. The extension may ask our server for the latest week's figure; that request carries no load data, and our server reads the figure from EIA's public data — nothing about you or your loads is ever sent to EIA.
• Error reports — when something goes wrong that you do not need to act on (for example the load board refusing a request, or an error inside the extension), the extension notes an error code from a fixed list, the HTTP status code if there is one, whether you were in Advanced View or the standard view, the extension version, when it happened and how many times. The same notes also carry a few counts when nothing is wrong: that a page loaded, how long a search had the load board's live updates, how many new loads arrived and how late, and how far apart searches were run. The notes travel with the licence check above — no separate request — at most every 10 minutes. They never contain load content, your DAT One or Truckstop token, your HaulFinder session, email or web addresses: both the extension and our server accept only short codes from a fixed list. We store them with your company and seat identifiers, use them only to find and fix faults and to decide how the extension should work, and delete them after 14 days.
• Gmail, if you connect it, and Google sign-in, if you use it — see sections 4, 4b and 4c.

Like any web service, our hosting provider keeps standard technical logs of requests (for example the IP address and time). We do not use them to track you.

3a. Your company's account: team, broker list, phone-app defaults

HaulFinder is bought by a company, and some of what our server keeps belongs to the company rather than to one person:

• Team. A seat is a work email address that your company's administrator (or we, at the company's request) has added; we store the address before the person first signs in, and nothing is sent to it. Every seat has a role, admin or member. A company administrator sees, on the Cabinet's Team page, each seat's work email, its role, whether it is active and when its person last signed in, and can add a seat, remove one and change a role. That page shows nothing else about you — not your loads, notes, templates, mail or name.
• Broker list. The company's own list of brokers it wants tagged on loads: for each, an MC number, a name, other names, a status label and a short note. Administrators edit it (so can we, at the company's request); every seat of the company reads it, and each browser keeps a copy while signed in (section 1). It is the company's business data, not data about you.
• Phone-app defaults. Which calling app opens when a phone number is pressed: a default for the company and rules by the domain of the mailbox's address. We set it at the company's request. It holds app names and email domains — no phone numbers — and a dispatcher's own choice always wins over it.
• History. The server keeps a history of changes to the team and the broker list for the company's administrators: when, which administrator (by work email), what changed and the values before and after — for a seat, the address and role; for a broker, the entry's text. Changes we make at the company's request appear as "operator".

3b. Moving from your company's previous extension (optional)

If your company used another browser extension for DAT One before HaulFinder and asks us to move its dispatchers across, that extension sends a copy of what each dispatcher set up in it to our server, filed under the work email of the person's Chrome profile — before the person has signed in to HaulFinder. The sending is done by the previous extension; this section covers what our server receives and keeps. The transfer exists only for companies that asked us for it.

• What the copy contains. The addresses of the mailboxes connected there (never their passwords or tokens); the email templates, each with its name, subject, text and signature — the signature's name, position, company, phone numbers, email, website, location, MC and DOT numbers, and a logo image; the default mailbox and template; a few preferences (default equipment, map and city-click switches); the broker reviews the person wrote there (MC and DOT numbers, rating, text, whether anonymous, date); and a block of other board settings that we keep exactly as they arrive, without reading or interpreting them. Whatever is outside a fixed list of fields, or over a field's size limit, is dropped before anything is stored. We keep at most 3 installs per person and 2 MB per copy.
• Who receives it. A seat signing in to HaulFinder with the same work email takes the copy and imports it into its own browser (and, failing that, the one seat whose address the copy lists as its mailbox). Nobody else is given it: not your administrator, not another seat. Our operator's tools show how many copies exist, for which work email and how many templates and mailboxes — never their content — and nothing from a copy is written to our logs.
• How long. When the import has gone through, every copy filed under your work email is deleted; only a one-way hash of the address (no content) is kept for 180 days, so that the previous extension is told to stop sending. A copy that nobody takes is deleted 60 days after the last update the previous extension sent. You can ask us to delete yours at any time (section 9).

4. Sending email through your Gmail

Connecting a Gmail account is optional. When you press Connect Gmail in the HaulFinder Cabinet, Google asks you to grant HaulFinder one permission: to send email on your behalf (the scope gmail.send). HaulFinder cannot read, search, label or delete your mail, and it asks for nothing else in your Google account except your email address, so it knows which mailbox you connected (and, only when you use Sign in with Google, your name — section 4b).

• What we store. Google gives our server a refresh token for that permission. We store it encrypted (AES-256-GCM) on our server, together with the address, the permission Google granted and when you connected it. Our server uses it for one thing only: to issue a short-lived access token to your own signed-in extension when it sends an email, which keeps it in memory and never saves it.
• When an email is sent. Only when you press to send it: Send in the message window, after you have checked the message, or the one-press send on a load, which sends that load's email from the mailbox and template you picked for that search. HaulFinder never sends an email by itself.
• Where your messages go. The message — its text, your signature and its recipients — goes directly from your browser to Gmail; it does not pass through our server, and we do not keep a copy. Your browser keeps the record described in section 1.
• Disconnecting. Remove a mailbox with × in the HaulFinder Cabinet: our server deletes the stored token and revokes HaulFinder's access with Google in the same step. You can also remove access in your Google Account (Security → Third-party connections); when Google tells us the token no longer works, we delete it.

4a. Broker credit from your RTS Pro account (optional)

Connecting RTS Pro is optional and needs your own RTS Pro account. When you press Connect RTS in the HaulFinder Cabinet, Chrome asks you to allow HaulFinder to access rtspro.com (and to add a small script there); then you sign in to RTS Pro yourself, in your own tab.

• HaulFinder picks up your RTS Pro sign-in from that tab: the access token and, if RTS Pro issues one, the refresh token of the same sign-in, with the sign-in's client id and the address of RTS Pro's token service. It keeps them in the extension's own storage in this browser until you press Disconnect, you remove HaulFinder's access to rtspro.com, or RTS Pro reports that the refresh token is no longer valid — so you stay connected when Chrome closes or your computer restarts. The access token is also removed when it expires or RTS Pro rejects it; the refresh token has no time limit of ours, and a temporary failure (no network, a blocked page) does not remove it. They are never logged and never sent to us. HaulFinder never sees your RTS Pro password.
• To show a broker's credit, your browser sends RTS Pro that broker's MC or DOT number, with your session. The answer is shown to you and kept in memory; it is not sent to our server.
• Renewal. An access token expires after a limited time that RTS Pro sets. When it has run out at the moment you look up a broker's credit, or the Cabinet checks the connection, HaulFinder sends the refresh token and the client id to RTS Pro's token service (a host under rtspro.com, the one RTS Pro's own page used) to get a new access token, and the new refresh token if RTS Pro rotates it, which replaces the old one. That is the only time it does so: there is no timer and no background renewal, and it needs neither your RTS Pro password nor an open RTS Pro tab. If RTS Pro issues no refresh token, nothing is renewed and RTS Pro asks you to sign in again when the access token ends.
• Disconnect in the Cabinet removes the scripts, deletes the stored access and refresh tokens and gives Chrome's access back; you can also remove the access in Chrome's extension settings, which deletes them too.

4b. Signing in with Google (optional)

You can sign in to the HaulFinder Cabinet with Sign in with Google instead of an email code. One Google window can then do two things for the same address: it signs you in to HaulFinder and, if you allow it, it connects that Google address as a mailbox, exactly as described in section 4. Google asks you for four permissions: to see your email address and your basic profile information (your name) — the scopes openid, email and profile — and to send email on your behalf (gmail.send). The permission to send is the one you may decline (see below): signing in does not need it. Connecting a mailbox from the Cabinet's mailbox list (section 4) does not ask for the profile permission.

• What we receive from Google. Your email address, confirmed by Google; your name, as it appears on your Google profile; and, if you allow it, the permission described in section 4. We read nothing else from your profile: Google may send other details with the name (such as a picture), and we ignore them.
• Why. The email address matches you to the seat your company holds and, if you allowed sending, tells us which mailbox you connected. The name is shown back to you, and only to you, on the Profile line of HaulFinder's Settings, in place of your email address. We do not use it for anything else, we do not share it, and it is not shown to other users or in your company's seat list.
• Where it lives. Your name is kept on our server, together with your seat (the same record as your email address, your company and seat identifiers), and our server hands it to your own extension when you sign in; the extension keeps it with your sign-in record (section 1). It is not written to our logs or error reports and it does not travel in the signed licence.
• If you decline part of it. If Google's screen lets you untick the profile permission, sign-in still works and HaulFinder shows your email address instead of a name.
• If you decline sending email. If you leave "Send email on your behalf" unticked on Google's screen, you are signed in all the same — your address is matched to your seat as usual — and HaulFinder connects no mailbox: our server stores no token for you, and the access Google issued in that window is revoked with Google straight away (unless the same Google account already has a mailbox connected in HaulFinder, where revoking it would disconnect that mailbox as well). The Cabinet then shows that no Gmail is connected; press Connect Gmail (section 4) whenever you want to send email from HaulFinder. Nothing else in HaulFinder depends on it. Allowing the permission is what lets one window do both; HaulFinder uses it as described in section 4.
• Deleting it. Your name is removed when your seat is removed, or when you ask us to at support@haulfinderapp.com (section 9); signing out removes it from your browser. Signing in again without a name does not erase a stored one; a new sign-in with Google replaces it. To end Google's side, remove HaulFinder in your Google Account (Security → Third-party connections).

4c. Google user data: what HaulFinder accesses, how it uses, stores, shares and deletes it

"Google user data" here means everything HaulFinder receives from Google when you use Connect Gmail (section 4) or Sign in with Google (section 4b). Both are optional: you can sign in with a code sent to your work email instead, and everything in HaulFinder except sending email works without Gmail. Connect Gmail asks Google for three permissions — openid, email and gmail.send; Sign in with Google asks for the same three and profile. HaulFinder asks for no other Google permission, and none of the four lets it read your mail. The tables below go through the four permissions one by one.

Limited Use. HaulFinder's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements. The use of information received from Google APIs will also adhere to the Chrome Web Store User Data Policy (https://developer.chrome.com/docs/webstore/program-policies/limited-use), including the Limited Use requirements. We do not use Google user data for advertising, we do not sell it, we do not use it to train AI or machine-learning models, and no person at HaulFinder reads your email.

5. Service providers

We do not sell or rent personal information, and we do not share it for advertising. Route geometry is computed from OpenStreetMap data (© OpenStreetMap contributors, https://www.openstreetmap.org/copyright).

6. Links you click

Some buttons open other websites in a new tab — Google Maps directions, the FMCSA SAFER carrier lookup, a factoring company's site (only if you turn that column on), or your phone app for a call. Those sites receive what your browser sends when you visit them; their own privacy policies apply.

7. Do Not Track

HaulFinder does not track you across websites, so it behaves the same whether or not your browser sends a Do Not Track signal.

8. Security

Sign-in codes and session tokens are stored only as hashes; Gmail refresh tokens are stored encrypted; all traffic to our server uses HTTPS; your DAT One and Truckstop tokens stay in your browser's memory. No system is perfectly secure; if we learn of a breach affecting your information, we will notify you and your company as the law requires.

9. Retention and deletion

• In your browser: until you delete it, sign out (for the sign-in record and licence), or remove the extension; the marks of loads you emailed only until Chrome closes; your RTS Pro sign-in (its access and refresh tokens) only until you press Disconnect, you remove access to rtspro.com, or RTS Pro reports that the refresh token is no longer valid (the access token is also removed when it expires or RTS Pro rejects it).
• On our server: your seat record — work email, role, last sign-in time and, if you signed in with Google, your name — for as long as your company keeps your seat (removing a seat deletes the record, its sessions and its connected Gmail permission); sessions until you sign out, they expire, are revoked, or your seat is removed; route cache up to 14 days; error reports up to 14 days; the record of your seat's latest licence check (its time and the extension version) until your seat is removed, and in any case no more than 14 days after that check; Gmail tokens until you disconnect the mailbox, Google revokes them, or your company's seats stop working at the end of its subscription or because a payment is still not made after 7 days (Terms of Service, section 2) — the Gmail connections of those seats are then removed from our server (section 4c). Company data — the broker list, the phone-app defaults, the team history and where the company heard of us (section 3) — for as long as the company's account exists; a history line that names a seat stays after the seat is removed. A copy from a previous extension — as set out in section 3b.
• Backups. Our host keeps backups of the server's database so we can restore the service: scheduled ones, kept for up to 27 days. A record we delete from the live database can remain in a backup until that backup expires or is deleted; backups are used for nothing but restoring the service.
• Deletion on request: write to support@haulfinderapp.com or ask your company's administrator. We will delete the records tied to your email — your seat, name and sessions, any copy from a previous extension, and any stored Gmail token, which we also revoke with Google — and confirm by email. The lines of your company's team history that name your address are part of the company's own record and stay unless the company asks us to remove them.

10. Your choices and rights

You can sign out, disconnect a mailbox or RTS Pro, delete your notes, or remove the extension at any time. You can ask us what we hold about you, ask us to correct or delete it, or ask us to stop taking error reports from your seat, at support@haulfinderapp.com.

11. Business customers

HaulFinder is sold to companies. We process your dispatchers' seat data on your behalf to provide the service, and your company's administrators can manage the seats, roles and broker list described in section 3a. A data processing addendum is available on request.

12. Children

HaulFinder is a business tool for freight dispatchers. It is not directed to children under 13, and we do not knowingly collect their information.

13. Changes to this policy

We will post any change here with a new "Last updated" date. For a material change, we will also email your company's administrator before it takes effect.

14. Contact

Novil Prime LLC · 30 N Gould St Ste R, Sheridan, WY 82801, USA · support@haulfinderapp.com