Security and data handling

What the connector holds

• Your Freight Right credential for this connection, encrypted, so the assistant can be served without you signing in again. It is bound to this one connection and dies with it.
• Nothing else about you. No password (it never sees one), no session, no conversation, no shipment data at rest — every answer is fetched when your assistant asks for it.
• Prices it just fetched, for a short time (never longer than the offers are bookable), so that paging through offers does not ask carriers again. Encrypted, and re-checked against your account before they are ever shown again — if you were disconnected, paused, or left the organization the price was made for, they are refused and dropped.
• Bookings you prepared, until they are decided, because forgetting one is the only way a booking could be lost or doubled.

What the connector never does

• It never receives your Shipment Manager session, even when you confirm a booking. The confirmation page hands Freight Right's sign-in service your session and the connector a short-lived proof that says nothing else.
• It never logs what you asked, what came back, your e-mail address, your tokens or the query strings of requests. Its logs carry a request id, which account, which tool, the outcome and how long it took.
• It never sends anything to a third party. Your assistant vendor sees your conversation, as always; Freight Right does not.

Who enforces what

The connector is a face on Freight Right's public APIs, not a second permission system. Every single call is authorized again by the API that owns the data — your account's state, its products, the capability you approved, and your organizations. If the connector were wrong about any of it, the API would still refuse.

Reporting a problem

Write to support@freightright.com. If it is a security issue, say so in the subject and we will treat it accordingly.