Carrier directory · Data corrections
Data corrections
Every record on this site is a copy of an FMCSA public record, shown with the date FMCSA published it. If a value here does not match what FMCSA serves today, or you are the registrant and want the profile withheld, use the form on the carrier’s profile page.
Find the profile
What can be requested
- Legal name
- DBA name
- Registered city, state or ZIP
- Fleet figures (power units, drivers)
- Operating authority or insurance filing
- Registration status
- Another field
- Removal of the profile from this directory
NeuroHaul does not edit FMCSA’s records. A correction here changes what this directory shows; to change the underlying registration, file an updated MCS-150 or authority application with FMCSA. Where a request says the directory differs from FMCSA’s current record, the reviewer checks FMCSA’s SAFER snapshot and re-reads the source dataset.
How a request is handled
- The form checks that the USDOT exists in the directory and that the request is not a duplicate (at most three open requests per carrier, and a daily cap across the site).
- A person at NeuroHaul reviews it against FMCSA’s current record. Nothing is changed automatically.
- If the directory is wrong, the profile is corrected and re-published. If the source dataset is wrong, the profile keeps FMCSA’s value and the review note records the discrepancy — the directory cannot show a value FMCSA does not.
- A removal request from the registrant unpublishes the profile while it is under review; the URL then returns 404. Because pages are cached for up to 24 hours, a change can take that long to appear everywhere.
- If you left an email address, it is used only to reply about this request. No mailing list, no follow-up.
What is kept, and for how long
- The request itself (field, claimed value, message) and its review notes: 12 months after the request is closed, then deleted.
- Your email address, if given: 12 months after close, then deleted. It is used only to reply about this request.
- A keyed hash of the submitting IP address and the browser user-agent string, kept to stop automated abuse: 90 days, then deleted. The raw IP address is never stored.
- Anti-abuse checks: a Cloudflare Turnstile challenge and a hidden honeypot field. No account, no cookies beyond those the site already sets.
The site’s privacy policy covers everything else. Request data is never combined with the carrier record and never published.
Where the data comes from
Sources, dates and the rules behind every derived sentence are on the methodology page.