Logistics and distribution
Supply chain visibility platforms: who owns your tracking data?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
Ownership of tracking data on a supply chain visibility platform is set by contract, not by who generated the ping. Shippers commonly own their shipment data, carriers control their location feeds, and platforms commonly reserve rights to aggregated data and outputs they compute, such as ETAs. Read the data, license and termination clauses for each layer.
Key takeaways
- Tracking data comes in layers: shipment details, location pings, status events, ETAs and network benchmarks.
- Each party's rights come from a different contract, and the platform's subscription terms are only one of them.
- Platforms commonly reserve rights in aggregated data and in outputs they compute, such as predicted ETAs.
- Export rights and data return at termination matter as much as ownership language.
Who owns tracking data on a visibility platform?#
Tracking data on a visibility platform is owned and controlled according to a stack of contracts, and no single party usually holds all of it. The shipper's subscription agreement, the carrier's onboarding terms, a broker's agreements on both sides and the platform's terms of service each allocate part of the picture.
A more useful framing asks three questions for each layer of data: who supplied it, who may use it and for what, and who can get it back. Ownership language matters, but use rights and export rights decide what a company can actually do with its tracking history, whether for its own analytics, a dispute, a platform switch or a licensing review.
The layers of tracking data#
Tracking data on a visibility platform comes in layers, and each layer tends to sit in a different contractual position. Separating them is the first step in any rights review.
Brokers sit in the middle of most of these layers. A broker typically supplies shipment details on behalf of its shipper customers and receives location feeds on behalf of its carriers, so its rights in each layer depend on two sets of agreements rather than one.
- Shipment details: orders, stops, reference numbers and appointment windows, usually sent from the shipper's or broker's TMS.
- Location pings: positions from ELDs, telematics units, driver mobile apps or carrier systems.
- Status events: arrivals, departures, delays and exceptions, recorded by drivers or carriers or inferred by the platform.
- Predicted ETAs and risk scores: outputs computed by the platform's own models.
- Network data and benchmarks: aggregated performance across many customers, carriers and lanes.
- Your own annotations: exception notes, customer messages and resolutions your team adds to shipment records.
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
Typical contract positions by party#
Typical contract positions differ by party, and the table summarizes what agreements commonly say. These are patterns, not rules; your own agreements control, and positions vary widely between platforms and over time.
The last layer in the list above is often overlooked. Notes your team adds to a shipment record are usually your content, but if they are stored only inside the platform, export rights decide whether you ever see them again.
| Party | Commonly owns or controls | Commonly grants | Commonly restricted |
|---|---|---|---|
| Shipper | Its shipment details and its own annotations | A license for the platform to process data to provide the service | Access to other customers' data and to benchmarks beyond the product |
| Carrier | Its location feeds and fleet data | Permission to share location for specific shipments while active | Tracking outside the shipment window; onward use of driver location |
| Broker | Its load records and its customer and carrier relationships | Shipment visibility for its customers through the platform | Disclosure of carrier identities to shippers, under some broker agreements |
| Platform | Its software, models, computed outputs and aggregated data | Customer access to dashboards and exports during the term | Customer use of platform outputs beyond internal purposes |
Clauses to read in a visibility platform agreement#
The clauses that decide your rights are spread across the subscription agreement, the data processing terms and the terms of service. A general counsel reviewing tracking data rights should read them together, because a generous ownership clause can be narrowed by a restrictive use clause elsewhere.
Watch for definitions that move data between categories. If status events are defined as platform outputs rather than customer data, or if de-identified data is carved out of the customer data definition, information you supplied can end up on the platform's side of the line without any clause saying so directly.
| Clause | What to look for |
|---|---|
| Customer data definition | Whether it includes location pings, status events and your annotations, or only data you upload |
| License to the platform | Whether the platform may use your data only to provide the service, or also to improve models and build benchmarks |
| Aggregated or de-identified data | Whether the platform owns data derived from your shipments and may keep using it after termination |
| Outputs and derived data | Who owns ETAs, risk scores and reports, and whether you may use them outside the platform |
| Export and data return | Format, scope and timing of exports during the term and at termination |
| Restrictions on use | Limits on sharing platform data with third parties, including AI developers |
| Assignment and change of control | What happens to your data if the platform is acquired, merged or restructured |
Driver location is a privacy question too#
Driver location from a phone app or ELD can be personal data, because it tracks an identifiable person, often an owner-operator, through the working day. That adds a privacy layer on top of the commercial contracts.
State privacy laws and employee or contractor notices may apply, depending on where drivers are and how the data was collected. Carrier onboarding terms usually limit tracking to the shipment window, and carriers watch that limit closely. Any use of location history beyond operations should be assessed with counsel, and pings are usually coarsened or removed before records leave the company.
What a company can usually license from its tracking history#
A company can usually license the tracking history it supplied or created: its own shipment records, the status events tied to them, and its team's exception notes and resolutions, after de-identification. What it usually cannot license are the platform's computed outputs, network benchmarks and other parties' feeds, unless the agreements say otherwise.
In practice, the most useful records for AI teams are not the pings but the decisions around them: a missed appointment, the call to the receiver, the re-plan and the outcome. Those records often live in the company's own TMS and email as much as in the platform, which strengthens the company's position.
Illustrative: a fictional mid-size freight brokerage tracks most loads on a visibility platform and keeps load records and notes in its own TMS. Its general counsel finds that customer data covers uploaded shipment details and user annotations, while ETAs and aggregated data belong to the platform. The brokerage exports its shipment events and notes during the term, joins them to its TMS exception records, removes carrier and driver identities, and limits a proposed license to that combined set, leaving platform ETAs out.
How SourceX approaches tracking data#
SourceX approaches tracking data by starting with the contract stack in the Rights step of the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The fit check collects metadata only, such as which platform is used, what the company can export and where its own exception notes live.
Each package that proceeds is documented in a SourceX Evidence Packet covering provenance, licensing rights, permitted use, the privacy record and release authorization. Platform-owned outputs and other parties' data stay out unless the agreements allow them, and the company approves every step and keeps ownership of its own records.
Frequently asked questions
Can a visibility platform use our data to train its own models?
It depends on the license you granted. Many subscription agreements let the platform use customer data to provide and improve the service, which can include model training. Read the license and aggregated data clauses, and negotiate limits at renewal if they matter to you.
Do we lose our tracking data if we switch platforms?
You may lose access if you do not export before termination. Check the data return clause for format and timing, schedule regular exports during the term, and keep copies in your own storage.
Are predicted ETAs our data?
Usually not. ETAs and risk scores are typically defined as platform outputs, licensed to you for internal use during the term. Your actual arrival and departure events, by contrast, are usually part of your shipment data.
Does a carrier have to agree before we share tracking history?
Possibly. Carrier onboarding terms and broker-carrier agreements may limit how location data is used and for how long. De-identifying carriers and drivers helps, but counsel should check the carrier-side terms before any license.
When should we negotiate data terms with a visibility platform?
Renewal is the natural moment. Common asks include a customer data definition that covers annotations and status events, limits on model training with your data, exports in a usable format on request and at termination, and notice before any assignment of the agreement.
What happens to our data if the platform is acquired or split up?
The assignment and change of control clause usually lets the platform transfer the agreement, and customer data follows the contract. Confirm export rights and data return obligations, and consider pulling a full export whenever a corporate change is announced.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.