Document: data-sourcing-accuracy-dispute-policy · version 67934917818a0bc6 · effective [EFFECTIVE DATE]
DRAFT v0.1 — for attorney review. Not legal advice.
Effective date: [EFFECTIVE DATE] · Last updated: June 7, 2026
This Policy explains where CarriersScore data comes from, the nature of the CarriersScore Score, the limits of accuracy, and how a carrier or other party may dispute or request correction of information. It is incorporated into the Website Terms of Use and Subscriber Terms of Service. Defined terms have the meanings given in the Subscriber Terms.
The Service compiles information from multiple sources, which may include:
The CarriersScore Score (the 0–1000 value and A–F band), together with sub-scores and reason codes, is CarriersScore's subjective, evaluative assessment produced by applying a disclosed general methodology to the underlying data. It is a statement of opinion, not a statement of fact, and it is not a guarantee or prediction of any carrier's safety, solvency, performance, honesty, compliance, or future conduct. Reasonable analysts using the same data could reach different conclusions. We disclose the general factors and weightings used so that the basis of our opinion is transparent; we do not disclose proprietary implementation details.
The data and outputs are provided "as is" and "as available." Underlying records may contain errors, omissions, or out-of-date entries from their original sources, and conditions change over time. We do not warrant the accuracy, completeness, currency, or reliability of any data or output, and we are not the source of, and do not control, public-government or third-party data. Each output reflects information as of its date. You should independently verify material information with primary or official sources and the carrier before relying on it, and you should not treat any output as the sole basis for a business decision.
The Service is a tool to support, not replace, your own due diligence and judgment. We make no representation that using the Service — including obtaining a Hard Pull or Snapshot — will satisfy any standard of care, will defeat or limit any negligent-selection, vicarious-liability, or other claim, or will comply with any law applicable to you. You are solely responsible for your carrier-selection, retention, and monitoring decisions.
A Hard Pull creates an immutable, timestamped Snapshot recording the data and Score returned at that moment. A Snapshot is a faithful record of what the Service returned on that date; it is not a representation that the underlying data was accurate or that any decision was reasonable. Snapshots are retained as records (see Section 8 and Doc 09).
We want our information to be as accurate as possible. Two paths apply, depending on the data:
(a) FMCSA-sourced fields (authority, safety ratings, inspections, crashes, census). These originate with FMCSA. The authoritative way to correct them is FMCSA's DataQs process at the FMCSA website; corrections accepted by FMCSA will flow into the Service after FMCSA updates and our next refresh. We cannot unilaterally alter official FMCSA records.
(b) CarriersScore-generated content and CarriersScore-sourced or carrier-provided fields. If you believe the Score, a reason code, a carrier-provided field, or other CarriersScore-controlled content is inaccurate or out of date, submit a dispute to info@carriersscore.com (or the in-product dispute tool) including: your name and relationship to the carrier; the USDOT/MC number; the specific item disputed; the correct information; and any supporting documentation.
We will acknowledge a complete dispute within 5] business days and conduct a reasonable review, typically within [30] days. We may: correct or update the item; annotate it as disputed pending review; explain the basis and source if we determine no change is warranted; or, for FMCSA fields, direct you to DataQs. We will notify you of the outcome. Submitting a dispute does not guarantee a particular result, and our determination reflects our good-faith assessment. This process is a customer-service and data-quality mechanism; it is not a consumer-reporting "reinvestigation" under the FCRA, which does not apply (see [Doc 08).
We retain Snapshots and transaction records as immutable records for [seven (7) years] or as otherwise required for legal, audit, and evidentiary purposes, even after correction of forward-looking data and even after an account closes. A correction changes the current Service data going forward; it does not alter historical Snapshots, which record what was shown at the time.
Your use of, and reliance on, data and outputs is at your own risk and subject to the disclaimers and limitations of liability in the Website Terms and Subscriber Terms.
Data disputes: info@carriersscore.com. General: info@carriersscore.com.
The Score is produced by a versioned scoring model. Every Hard-Pull Snapshot permanently records the model version, data as-of date, and a content hash of what was shown, so any past output can be re-examined exactly as delivered. We log methodology changes; when we make a material change to the methodology, we will announce it (release notes and/or in-app notice) and new outputs will carry the new version identifier. Requests for review of an output are evaluated against the model version that produced it.
*DRAFT — to be reviewed and finalized by counsel. (c) Blacktop Digital Assets, LLC.*
Where the Service displays cross-reference signals (factual statements derived
from public records and platform profiles, with sources shown), the carrier the
signal concerns may attach a written response of up to 1,000 characters giving
context or explanation. Responses are displayed alongside the signal to all
subscribers, attributed and timestamped, with edit history retained. A response
is not a dispute: to assert that the underlying data is wrong, use the dispute
process in this policy (and DataQs for FMCSA-sourced records). If a dispute is
upheld, the signal is corrected or removed and the removal is recorded. Known
benign patterns (for example, shared registered-agent addresses or leased
equipment registrants) are annotated by the system itself. Signals state facts
and sources only; subscribers must exercise independent judgment as required by
the Subscriber Terms of Service.