What we don’t do

A vetting tool is most useful when its limits are explicit. Here are ours.

We don't synthesize a safety score

You will never see a "TDPort score" beside a carrier. We surface FMCSA's own ratings, scores, percentiles, and flags. When a row shows red or amber, it's because FMCSA rated, scored, or flagged that data point. We don't mix the inputs into a single number, because:

• Crash prediction from public data is not a solved problem, and every commercial scoring product that claims otherwise is inviting the same negligent-hiring lawsuit Montgomery just opened up.
• A single number invites the question "why did you accept a 60?" The answer to "why did you accept this carrier?" is whatever paper trail you built — not a number we made up.

We don't recommend hiring or rejecting

There is no Hire button and no Reject button. There is no banner that says "Recommended: DO NOT HIRE." The workbench shows you what FMCSA, USPS, and the rest of the data sources are saying. You decide what to do with that.

This is deliberate. The moment we say "reject this carrier," we have made a factual representation about that carrier's safety, and we have inserted ourselves into a transaction we have nothing to do with. The tool is the camera. The decision is yours.

We don't paywall any v1 feature

Everything individual brokers and shippers use today is free.

• Anonymous tier: full vetting on screen, plain-text report. No daily quota.
• Free account: everything anonymous, plus the sealed cert PDF, pickup checklist, and your vault.

A future enterprise tier (team accounts, TMS integration, SSO, white-label cert PDFs, SLA) is planned. It does not gate any existing feature; v1 is and remains fully free for individual brokers and shippers. Same mental model as ChatGPT: free is the full product for individuals; pay for org-scale features the free tier was never built to serve.

We don't store your private key

Your account's signing key is generated in your browser, lives on your machine, and never reaches our servers. We can't sign on your behalf. We can't recover it if you lose it. That's by design — see Your account key.

We don't store the plaintext of your vettings

When you seal a record, the encryption happens in your browser before the data is posted to the proof chain. The chain stores the encrypted bundle and the public proof envelope. The decryption key rides on the cert PDF's QR code, which is yours, not ours.

We can't read your past vettings. Neither can a future attacker who breaks into TDPort. The plaintext only exists where you decide to put it.

We don't sell data

There is no data resale, no analytics product, no aggregated "industry insights" we ship to brokers or insurers based on what you vetted. Your records are yours.

We don't aggregate paid third-party feeds

CARRIER411, MyCarrierPortal, and similar paid safety-score products are out of scope. We're a free public-data tool. Users who want those feeds are free to bring them; we don't resell or relabel them.

We don't verify driver-level safety

PSP (Pre-Employment Screening Program) data is the FMCSA's driver-level data product. It's not free, requires the carrier's consent, and costs about $10 per pull. It is out of scope for this tool's v1.

We don't claim more than the chain actually proves

The TDPort proof chain proves three things about a sealed record: the encrypted bundle existed at the sealed-at timestamp, the bundle was signed by the named producer's key, and the bundle has not been altered since. That's the claim, and it's the only claim the cert PDF carries.

The cert does not claim the carrier is safe. It does not claim the FMCSA data was accurate. It does not claim the broker or shipper did the right thing with the data. It claims a vetting happened, by whom, with what data, at what time. That's what's useful in court.