Privacy
What Carrier Lookup collects: no accounts, one first-party analytics cookie, pseudonymous usage events, and—only if you join the waitlist—your email and the USDOT number you asked about. No emails are sent, no third-party trackers, no ad cookies.
Short version: there are no accounts. We set one first-party analytics cookie (HttpOnly, 1 year) that holds a random visitor id, and we record the first page and source you came from and a few pseudonymous usage events. If you join a carrier waitlist, we store your email and that USDOT number until alerts launch or you ask us to delete them. We send no emails today. There are no third-party trackers and no advertising cookies.
Carrier data we show
Carrier records come from FMCSA's public datasets on data.transportation.gov. We cache each lookup for up to 24 hours. We deliberately do not display the phone numbers, email addresses, officer names or street addresses that appear in those datasets, and our queries don't request them.
The numbers and names you type into the search box are sent to FMCSA's open-data service (data.transportation.gov, operated by the U.S. Department of Transportation) to run the lookup. They are not linked to your visitor id.
The carrier waitlist
Monitoring ("notify me when this carrier's insurance or authority changes") is not built yet. If you join the waitlist on a result page and tick the consent box, we store:
- your email address,
- the USDOT number of that carrier,
- the version of the consent text you agreed to, the time, and your random visitor id.
We use this only to tell you, once, when carrier alerts launch, and to count interest per carrier. We do not send any email until then, we never sell or share the list, and we don't add you to any newsletter. To be removed, send a deletion request through the contact form on the about page (topic “Delete my waitlist signup”, with the email you used) and we will delete your entries. Waitlist entries are deleted if alerts don't launch within 12 months.
The contact form
If you use the contact form on the about page and tick the consent box, we store your topic, your message, the reply email if you give one, the consent text version, the time and your random visitor id. We use it only to read and answer your message. Nothing is sent to you automatically, and messages are deleted after 12 months. Don't include sensitive personal data in the message.
The analytics cookie
When you open a page, the site sets one first-party cookie named _v:
- What it holds: a random visitor id and the date of your last visit.
- How it is set: HttpOnly, Secure, SameSite=Lax, expires after 1 year.
- What we store with the id, once, on your first visit: the first page you opened and where you came from (referring site, any
utm_tags or ad click id), your country as reported by our host, a rough device type and a one-way hash of your browser's user agent, used only to spot automated traffic. We never store your IP address.
Search engine crawlers and other self-identified bots do not get the cookie; we only count them per day.
Usage events
The page sends small events: when a page has loaded, when a lookup shows a result (whether you searched by USDOT, docket or name, whether a carrier was found, and the verdict category, never the number or name you searched), and when you click the factoring explainer link on a new-authority result. A waitlist signup and a contact message are recorded as events too (without your email or message). Individual events are kept for 120 days, then only daily totals remain. We use them only to see whether the tool is useful.
No third-party tracking
No third-party analytics, advertising or tracking scripts are loaded, and no advertising cookies are set.
What our host sees
The site runs on Cloudflare Workers (cache and database included). Like any website, Cloudflare receives the technical data needed to deliver pages (such as IP address, user agent and URL) and keeps short-lived request logs for security and reliability. See Cloudflare's privacy policy.
Your choices
You can delete the _v cookie or block cookies for this site at any time; the lookup keeps working without it.
Changes
We will update this page before the way the site handles data changes. Last updated November 15, 2026.