Logistics and Supply Chain Technology IP Toolkit: Shipment Data, Platforms, and Network Rights

By Casey Scott McKay · 2025-08-09

A shipment generates data about two parties who are not the logistics provider, which is the structural fact underneath every intellectual property question in freight technology. This toolkit assembles the working material for practitioners advising forwarders, brokers, carriers, and the platforms that connect them. It covers who owns shipment data and what a provider may do with it, why benchmarking products are the sector's most valuable and most legally exposed offering, how customs and regulatory interfaces create obligations that override commercial terms, and what network effects mean for contract drafting when the product's value comes from participants rather than from code. It sets out the competitor-sensitivity problem that arises when one platform serves rivals, and the exit terms that determine whether a customer can ever leave.

IP and Technology > Information Technology | Toolkit | Published 9 August 2025 - Updated 9 June 2026 | Casey Scott McKay - marksy.us

Summary. A shipment generates data about two parties who are not the logistics provider, which is the structural fact underneath every intellectual property question in freight technology. This toolkit covers who owns shipment data and what a provider may do with it, why benchmarking products are the sector's most valuable and most exposed offering, how customs and regulatory interfaces create obligations overriding commercial terms, what network effects mean for drafting when value comes from participants rather than code, the competitor-sensitivity problem when one platform serves rivals, and the exit terms determining whether a customer can leave.

Keywords: logistics IP · shipment data rights · freight platform terms · carrier agreements · benchmarking outputs · rate data · customs interfaces · EDI and API terms · network effects · visibility platforms · telematics · warehouse automation · brokerage data · aggregated analytics · competitor sensitivity

Start Here

Every intellectual property question in logistics technology descends from one observation: the data is about somebody else's business.

A shipment record contains the shipper's product, the consignee's receiving pattern, the origin and destination, the volume, the timing, the rate paid, and the carrier used. None of that is the logistics provider's information in any intuitive sense. All of it passes through the provider's systems, is stored there, and is the raw material of every analytics product the provider might build.

That produces a persistent tension. The provider believes it owns its own records. The shipper believes its shipping patterns are commercially confidential. The carrier believes its rates are. And all three are partly right, because the record is a composite that nobody created alone.

Layer on the sector's other distinguishing features and the practice takes shape.

Value comes from the network, not the software. A visibility platform is worth what its carrier integrations and shipper participation make it worth. The code is replicable; the network is not. That means the legally protectable assets are the integration work, the participation agreements, and the accumulated data — not the product.

Regulatory interfaces are mandatory and shared. Customs filings, security programmes, and transport documentation are prescribed, exchanged with government systems, and carry obligations that override what the commercial contract says.

One platform serves competitors. A forwarder, a broker, or a visibility provider routinely holds data from rivals in the same industry, which is a confidentiality and competition problem before it is an intellectual property one.

Switching costs are the business model. Integration effort, historical data, and configuration make leaving expensive, which makes exit terms the most consequential clause in any agreement and the least negotiated.

Four questions organise the work.

Who owns the shipment record, and what may each party do with it?

What may be built from aggregated data, and what representations are being made about it?

Which obligations come from regulation rather than contract?

What happens on exit — data, integrations, and continuity?

See Where the Box Went for the doctrinal treatment and Advising a Logistics or Supply Chain Technology Business for the sequence.

The shipment record, and the four claims to it

A single shipment generates a record with at least four interested parties, and the sector's contracts almost never address all four.

The shipper supplies the commodity description, the volumes, the destinations, and the commercial terms. Its shipping pattern reveals its customers, its seasonality, its sourcing, and its margins.

The consignee is disclosed by the record and is frequently not a party to any agreement with the provider at all.

The carrier supplies the rate, the capacity, and the service performance, and treats its rate structure as confidential.

The provider creates the record, adds tracking and status data, and maintains the system.

The legal position on each element differs. Facts about a shipment are facts, thinly protected under Feist Publications v. Rural Telephone Service. The compilation of many shipments involves selection and arrangement and is protectable as a compilation under 17 U.S.C. § 103. Rate data supplied in confidence is protectable as a trade secret under 18 U.S.C. § 1839 if treated as such. And the whole record is governed by whatever the contract says, which is usually a general confidentiality clause drafted for a different purpose.

The practical drafting response is to stop arguing about ownership and to allocate uses instead.

Operational use — running the shipment, billing, and support — is uncontroversial.

Customer-facing analytics, returning insight to the party whose data it is, is generally acceptable.

Aggregated benchmarking across customers is where the value is and where the disputes are.

Sale to third parties is a separate question requiring separate consent and separate pricing.

Retention after termination determines whether the provider's aggregate product survives a customer's departure.

See the Data Licensing and Rights Toolkit and the Data Licensing Checklist.

Benchmarking, and the sector's most exposed product

Every logistics platform of any scale eventually sells benchmarking: how your rates compare, how your transit times compare, how your carrier performance compares. Customers value it highly and it is the offering most likely to generate a claim.

Six problems recur.

Consent is inferred rather than obtained. The right to use customer data for aggregate analytics is read into a general licence clause, and customers who read the clause afterwards disagree.

Aggregation is asserted, not tested. In a market with few participants on a given lane, an "aggregate" figure may reveal an identifiable competitor's rate. The threshold rules — minimum contributor counts, suppression of small cells — must be defined and enforced.

Rate data is competitively sensitive. Sharing pricing information among competitors, even through an intermediary, raises competition concerns that have nothing to do with intellectual property. See the IP and Antitrust Toolkit.

Representations about the product are claims. Statements about coverage, sample size, and methodology are advertising claims subject to substantiation under 15 U.S.C. § 45 and challengeable by competitors under 15 U.S.C. § 1125.

Departing customers want out of the dataset. A contributor that leaves and demands removal from historical benchmarks presents the same unwind problem that trained models present: it may not be technically possible, and the contract should say so rather than promise otherwise.

Carriers object more than shippers. A carrier whose rates appear in a comparison product has a direct commercial injury and is more likely to litigate.

The drafting response is a benchmarking annex: explicit consent, defined aggregation thresholds, suppression rules, a stated methodology, a competition review, and honest terms about historical data on exit.

Platform, API, and integration terms

The connective tissue of the sector is integration: electronic data interchange with established trading partners, application programming interfaces with newer ones, and file transfers with everyone else.

Integration work is the moat. Connecting to hundreds of carriers, each with idiosyncratic systems, takes years. That work is protectable as trade secret know-how and as copyrighted mapping code, and it is what a competitor cannot replicate quickly.

Interface specifications are contested territory. Google LLC v. Oracle America, Inc. addressed reimplementation of an interface and left the surrounding questions live. Whether a competitor may implement a platform's published API to interoperate is both a copyright question and a commercial one.

Terms of use are enforced against scrapers. Automated collection of rate and tracking data from public interfaces raises contract, computer access, and trespass theories, with the access analysis running through Van Buren v. United States and the broader question of what authorisation means on a public site.

Rate limits and access tiers are the practical control, more effective than any clause.

Onward flow-down matters. A platform whose customer resells access has data moving to parties with no agreement.

Deprecation and versioning obligations determine whether an integration built today works next year, which is a continuity question for the customer and a support cost for the provider.

See the Technology Contracts Toolkit, the Online Terms and Consumer Contracts Toolkit, and the Software, Data, and Open Source Toolkit.

Regulatory interfaces, which override the contract

A substantial part of what a logistics provider does is prescribed by government, and the resulting obligations sit above whatever the commercial terms say.

Customs declarations are filed on prescribed forms through prescribed systems, using data supplied by the shipper, with accuracy obligations resting on the filer and record retention requirements running for years.

Broker licensing and confidentiality regimes govern what a customs broker may do with client information, independently of the contract.

Security programmes require disclosure of supply chain information to authorities and to programme partners.

Transport documentation — bills of lading, air waybills, dangerous goods declarations — is standardised, is a document of title in some forms, and is increasingly electronic under frameworks whose legal status varies by jurisdiction.

Sanctions and screening obligations require checking parties against lists, which is a data processing activity with its own retention and accuracy consequences.

Trade data becomes public. In several jurisdictions manifest data is published or obtainable, which means the shipper's confidentiality expectation is partly unfounded and the provider should not promise otherwise.

The practical instruction: identify which data elements are regulatory rather than commercial, and do not draft confidentiality obligations the law prevents you from honouring.

See Building an Export Compliance Program for a Technology Company and the Export Control Checklist for the adjacent screening obligations.

Serving competitors, and the wall that has to exist

A logistics platform of any scale holds data from businesses that compete with each other, and frequently from businesses that compete with the platform's own operations.

The asymmetry is the problem. A forwarder that also sells a visibility platform sees its competitors' shipments. A marketplace that also brokers freight sees the rates its participants accept.

Contractual confidentiality is necessary and insufficient. Customers want structural separation, and the credible answer is access controls, separated environments, and audited processes rather than a promise.

Competition law sits alongside. Information exchange among competitors through a common intermediary is a recognised risk area, and a platform that facilitates it may have exposure independent of any customer's complaint.

Employees move between roles. Someone who worked on the platform side and then joins the operating side carries knowledge, and the internal mobility policy is part of the compliance architecture.

Disclosure builds trust. Platforms that publish their separation architecture win business from customers who would otherwise refuse to participate.

Ownership structure matters commercially. Neutrality is a selling point, which is why some platforms are structured as consortia or independent entities.

What a logistics business actually owns

The integration estate. Carrier connections, mappings, and the operational knowledge of how each partner's system misbehaves. Trade secret material, rarely treated as such.

The historical dataset. Years of shipment records, valuable in aggregate, contested in ownership, and the basis of any analytics product.

The routing, pricing, and optimisation logic. Software with copyright protection and, where genuinely novel, some patent potential — subject to the eligibility difficulties that attend business-process claims under 35 U.S.C. § 101 and Alice Corp. v. CLS Bank International.

The customer and carrier relationships, protected by contract and by trade secret treatment of the lists.

The brand, which in a trust-dependent business matters more than in most technology sectors.

Warehouse and equipment technology for asset-operating businesses, where robotics and automation bring their own analysis. See the Robotics and Autonomous Systems IP Toolkit.

Nothing about the shipments themselves, which is the point this toolkit began with.

Exit, portability, and the clause nobody reads

Switching costs are the sector's business model, which makes exit terms the most consequential and least negotiated part of any agreement.

Data export format matters more than the right to export. A right to receive data in a proprietary format, without schema documentation, is not portability.

Historical data is the lock. A customer that has three years of shipment history in a platform loses its analytics baseline by leaving, whatever the export clause says.

Integrations do not transfer. The connections built to a customer's carriers belong to the platform, and rebuilding them at a competitor is the real switching cost.

Configuration is undocumented. Business rules, exception handling, and routing logic developed over years live in the system and nowhere else.

Transition assistance should be priced in advance, since a provider asked to help a departing customer at a moment of its choosing will charge accordingly.

Deletion obligations conflict with aggregate products and with regulatory retention, and the contract should reconcile them honestly rather than promising deletion the provider will not perform.

Insolvency of a platform strands customers whose operations depend on it, which is an escrow and continuity question. See the Software Continuity and Escrow Toolkit.

Privacy, which arrives through the driver and the door

Freight is business-to-business and nonetheless generates substantial personal data.

Driver telematics. Location, hours, speed, and behaviour, collected continuously about identifiable individuals, and used for performance management. This is workforce monitoring with all that entails. See Everything the Application Knows and the Recruitment and Workforce Data Toolkit.

Delivery data. Consumer names, addresses, signatures, photographs of doorsteps, and increasingly biometric confirmation. Personal data in every regime.

Warehouse monitoring. Cameras, wearables, and productivity tracking, with the same analysis as any employee monitoring programme.

Cross-border transfer is inherent, since a shipment crosses borders and its data follows.

Consumer-facing tracking pages are ordinary web properties with ordinary privacy obligations that logistics companies frequently overlook.

See the State Privacy Compliance Toolkit, the Biometric and Sensitive Data Toolkit, and the Incident Response and Breach Notification Toolkit.

Network effects, and what they mean for drafting

Logistics platforms are network businesses, and network businesses have legal characteristics that software businesses do not. Understanding them changes what a practitioner spends time on.

The asset is participation, not code. A visibility platform with two hundred carrier integrations and five hundred shipper customers is worth what those relationships make it worth. A competitor can write equivalent software in months and cannot assemble the network in years. Legal effort should therefore concentrate on the agreements that constitute the network — participation terms, integration ownership, exclusivity where it is obtainable — rather than on protecting the software, which is replaceable.

Value accrues asymmetrically. Early participants create value that later participants capture. Sophisticated early joiners ask for something in return — preferential pricing, equity, governance rights, or data rights — and the ones that do not ask receive nothing. Advising an early participant means recognising that it is contributing an asset, not merely buying a service.

Exclusivity is the contested term. A platform wants carriers connected only to it; carriers want to be everywhere. Exclusivity in this setting has competition implications, particularly where the platform has significant share, and a term that would be unremarkable in an ordinary supply agreement may not be here.

Interoperability pressure grows with scale. A platform that becomes infrastructure faces demands, and eventually regulation, requiring it to interconnect. Building a business on the assumption of a closed interface is building on ground that shifts.

Standardisation arrives eventually. Message formats, event definitions, and status codes in this sector are gradually standardising through industry bodies, which brings the declaration and commitment questions familiar from telecommunications. A platform participating in that work should have a policy about what it contributes. See the Standard Essential Patents and FRAND Toolkit.

Consortium and neutral structures exist precisely because participants will not contribute data to a competitor. Where a platform's ownership is the obstacle to participation, restructuring is a commercial answer with substantial legal architecture behind it — governance, data trusts, contribution terms, and access rules.

Multi-homing defeats lock-in. Customers connected to three platforms have leverage, and platforms know it, which is why integration effort and historical data are the retention mechanisms rather than contractual exclusivity.

The drafting consequence is a reordering of priorities. In a software business, the licence grant, the service levels, and the intellectual property indemnity carry the weight. In a network business, the participation terms, the data use matrix, the integration ownership schedule, and the exit annex carry it — and the licence grant is nearly boilerplate. A practitioner who spends a negotiation perfecting the warranty section while leaving the data matrix to a general clause has optimised the wrong document.

The freight brokerage variant

Brokerage deserves separate treatment because its economics differ and its data questions sharpen.

A broker's business is knowing which carrier will move which lane at what price, and its principal asset is a carrier list plus the pricing history behind it. That asset is trade secret material if treated as such under 18 U.S.C. § 1839, and it walks out the door with every departing salesperson.

Four points recur.

Carrier lists are protectable and contested. The list itself, the contacts, the rate history, and the performance notes are compiled information with real value. Whether a departing employee may use it turns on secrecy discipline, on the enforceability of any covenant, and on whether the information was genuinely confidential rather than obtainable from public sources.

Automation changes the analysis. Digital brokerages match loads algorithmically, which converts personal relationships into software and data. That is better for protection and worse for retention, because the software is copyable and the data is the moat.

Rate transparency is a competitive weapon and a risk. Publishing market rates attracts participation and exposes the publisher to complaints from parties whose pricing is revealed.

Double brokering and fraud are operational problems with intellectual property edges: impersonation of legitimate carriers, misuse of operating authority numbers, and fraudulent use of a broker's name. That last is a trademark matter, and the enforcement route runs through the ordinary false designation analysis under 15 U.S.C. § 1125 plus platform takedowns. See the Online Brand Protection Toolkit.

A short glossary

Shipment record. The composite data object generated by moving goods, containing information about at least four parties.

Visibility platform. A service aggregating tracking data across carriers and presenting it to shippers.

Integration estate. The accumulated connections to trading partners' systems. The sector's principal undocumented asset.

Electronic data interchange. The established message-based integration standard, still dominant with large partners.

Benchmarking product. Comparative analytics built from aggregated customer data. High value, high exposure.

Small-cell suppression. The practice of withholding aggregate figures derived from too few contributors to be genuinely anonymous.

Multi-homing. A customer's connection to several competing platforms, which defeats lock-in and shifts negotiating power.

Manifest data. Cargo information filed with customs, publicly obtainable in several jurisdictions, and therefore not confidential whatever the contract says.

Operating authority. The regulatory permission to operate as a carrier or broker, and a common target for impersonation fraud.

Double brokering. Re-tendering a load to another carrier without authority, frequently involving misuse of a legitimate operator's identity.

Telematics. Vehicle and driver data collected continuously, which is workforce monitoring in substance.

Transition assistance. Support given to a departing customer. Priced in advance or extracted at leverage.

Keeping those twelve straight resolves most confusion in the sector, because nearly every dispute is a disagreement about whose data a composite record is, and what the party holding it may build from it.

Advising the four kinds of client

The shipper. Buys logistics services and generates the data everyone wants. Its priorities are keeping its shipping patterns confidential, controlling whether its data feeds benchmarking products, and retaining the ability to change providers. Its characteristic error is signing a platform's standard terms without reading the data licence, and discovering three years later that its lane volumes inform a product sold to its competitors. Its leverage is highest at renewal and at onboarding, and nowhere else.

The carrier. Supplies capacity and rates, and treats pricing as its most sensitive information. Its priorities are rate confidentiality, control over appearance in comparison products, and integration terms that do not require rebuilding for every platform. Its characteristic error is connecting to platforms operationally, through an IT project, without anyone reading what the connection agreement permits the platform to do with the rates flowing through it.

The forwarder or broker. Sits in the middle, holds data from both sides, and increasingly sells technology as well as services. Its priorities are protecting the carrier list and rate history as trade secrets, managing the conflict inherent in serving competitors, and getting the benchmarking annex right. Its characteristic error is treating its customer and carrier lists as obviously confidential without ever having done the work — marking, access control, enumeration — that makes them legally protectable when someone leaves.

The platform. Owns software and, more importantly, a network. Its priorities are the integration estate, participation terms, the data use matrix, separation architecture if it serves competitors, and exit terms that are honest rather than aspirational. Its characteristic error is drafting like a software company: a beautiful licence grant, careful service levels, a well-negotiated indemnity, and a data clause of three lines that will determine whether the business has a product at all.

Each of the four signs paper written by the others. The practitioner's first job is to identify which chair the client occupies, and the second is to find the data clause, which in every one of these agreements is shorter and more consequential than anything around it.

The first meeting

Six questions asked of a new logistics technology client surface most of what matters.

Show me your data clause. Not the agreement — the clause. It will be three or four lines, it will use the word "aggregate" without defining it, and it will be the most important provision in the document.

Do you sell benchmarking, or plan to? If yes, the consent, thresholds, and competition review either exist or are the first workstream.

How many contributors sit behind your thinnest published figure? If the answer is unknown, the anonymisation claim is untested and the product is exposed.

Who built your integrations, and is any of it documented? The integration estate is the asset a buyer pays for and the thing no one has written down.

What does a customer receive if it leaves tomorrow? If the answer is a file in an undocumented format, the portability clause is decorative.

Which of your data fields are regulatory rather than commercial? Confidentiality promises over manifest data that is publicly obtainable are promises the provider cannot keep.

Six questions, half an hour, and a work plan. The answers also produce the data use matrix, which is the single document that makes every subsequent negotiation shorter.

A closing observation

Logistics technology is unusual among data businesses in that almost none of the data is about the company holding it. A software company's telemetry describes its own product. A retailer's transaction data describes its own customers. A freight platform's records describe two other businesses' commercial relationships, captured incidentally because the goods had to move.

That is why the sector's contracts, drafted on software templates, keep failing at the same point. A software licence assumes the provider owns what it processes. A logistics agreement cannot assume that, and the general licence clause borrowed from the software template papers over a question it was never designed to answer.

The remedy is a single document — the data use matrix — replacing an ownership argument nobody wins with a use allocation everyone can live with. It takes an afternoon to draft, applies across a whole book of business, and resolves in advance the dispute that otherwise arrives with the platform's most valuable customer, at the worst possible moment, over a product the customer only discovered by seeing itself in it.

Cross-border and modal variations

The analysis holds across the sector with adjustments worth noting, because a practitioner advising a multimodal business will meet all of them.

Ocean. The most data-transparent mode, because manifest information is published or obtainable in several jurisdictions. That materially weakens confidentiality claims over container-level movements and supports a whole industry of trade-intelligence products built on public filings. A shipper who believes its ocean movements are secret is usually mistaken, and the provider should say so rather than promise otherwise. Bills of lading are documents of title, and their electronic equivalents rest on frameworks whose legal effect varies by jurisdiction — which is a commercial risk as much as a legal one.

Air. Faster, more tightly regulated for security, and generating richer real-time data. Air waybills are not documents of title in the same way, which simplifies the transfer analysis. Security programme obligations require disclosures that cut across confidentiality terms.

Road. The most fragmented, with the largest number of small carriers, the heaviest telematics footprint, and the sharpest workforce monitoring questions. Brokerage economics dominate, and the carrier list is the asset.

Rail. Concentrated, with fewer counterparties, longer contracts, and interchange arrangements that resemble telecommunications interconnection more than trucking.

Parcel and last mile. Consumer-facing, which brings the full weight of consumer privacy law, delivery photograph practices, and tracking-page obligations that business-to-business freight avoids.

Warehousing and fulfilment. Adds facility automation, workforce monitoring, and inventory data belonging to the client rather than the operator — a variant of the same composite-record problem, with the added feature that the operator can see the client's sales in real time.

Cross-border generally. A shipment crosses jurisdictions and its data follows, which means transfer mechanisms, differing confidentiality baselines, and conflicting disclosure obligations are structural rather than exceptional. Assume the data will be subject to more than one regime and draft so that the strictest applicable obligation is the one the systems implement.

The unifying instruction is the same in every mode: identify which data elements are prescribed by regulation, which are publicly obtainable, and which are genuinely commercial — and confine the confidentiality and exclusivity promises to the third category.

That instruction also disposes of the most common drafting request in the sector, which is a shipper's demand for an absolute confidentiality undertaking over everything the provider touches. It cannot be given honestly. Manifest data is filed and often published; customs records are retained under statute; sanctions screening generates records that must be produced on request; and security programmes require disclosure to authorities and partners. A provider that signs the absolute undertaking has agreed to something it will breach in the ordinary course, and the shipper has bought an illusion. The better answer is a schedule: here is what is prescribed, here is what is public, here is what we will genuinely protect, and here is what we will tell you before we disclose.

Shippers who receive that schedule almost always accept it, because the alternative they were offered was never real.

The same schedule doubles as the provider's own compliance map, which is why it is worth building once and reusing across the book rather than negotiating from scratch with each counterparty.

Keep it current, because the regulatory column changes more often than the commercial one and a stale schedule is worse than none.

Review it whenever a new mode, a new jurisdiction, or a new government interface is added to the platform.

Each of those three events changes the regulatory column, and each is announced by an engineering team rather than by counsel.

A Suggested Reading Path

New to the sector: Where the Box Went, then Advising a Logistics or Supply Chain Technology Business, then the Logistics Technology IP Checklist.

Data terms: the Data Licensing Checklist and the Data Licensing and Rights Toolkit.

Platform terms: the Technology Contracts Toolkit, the Online Terms and Consumer Contracts Toolkit, and the Software Continuity and Escrow Toolkit.

Secrecy programme: Building a Trade Secret Program That Survives Litigation and the Trade Secret Protection and Departure Checklist.

Competition overlay: the IP and Antitrust Toolkit.

Claims: the Advertising and Marketing Law Toolkit for benchmarking representations.

Privacy: the State Privacy Law Applicability and Readiness Checklist and the Biometric Data Checklist.

Adjacent sectors: the Telecommunications and Network Infrastructure IP Toolkit for the network analysis, the Automotive, Mobility, and Connected Vehicle IP Toolkit for fleet telematics, and the Marketplace and Platform Liability Toolkit for intermediary questions.

Transactions: the IP Due Diligence Toolkit, where the data rights position and the customer concentration in the integration estate are the two findings that move price.

Primary Authorities

| Authority | Use | |---|---| | 17 U.S.C. § 102 | Platform software and documentation | | 17 U.S.C. § 103 | Shipment datasets as compilations | | 17 U.S.C. § 106 | Reproduction in scraping and reuse claims | | 17 U.S.C. § 201 | Contractor-developed integrations | | 17 U.S.C. § 204 | The signed writing behind them | | 17 U.S.C. § 412 | Timely registration of code and datasets | | Feist v. Rural Telephone | Shipment facts and the limits of compilation protection | | Google LLC v. Oracle America | Interface reimplementation and interoperability | | 35 U.S.C. § 101 | Eligibility for routing and optimisation claims | | Alice Corp. v. CLS Bank International | The abstract idea problem for logistics methods | | 35 U.S.C. § 103 | Obviousness over a well-developed operations literature | | 35 U.S.C. § 271 | Divided infringement across shipper, platform, and carrier | | 18 U.S.C. § 1836 | Misappropriation of integration know-how and customer lists | | 18 U.S.C. § 1839 | Reasonable measures over rate and routing data | | 18 U.S.C. § 1030 | Unauthorised access in scraping disputes | | Van Buren v. United States | What exceeding authorised access means | | 15 U.S.C. § 45 | Substantiation of benchmarking and coverage claims | | 15 U.S.C. § 1125 | Competitor challenges to performance claims | | 15 U.S.C. § 1 | Information exchange among competing participants | | 15 U.S.C. § 1114 | Counterfeit goods moving through the chain | | FRCP 26 | Protective orders over rate and customer data | | FRCP 34 | Production of transactional records | | FRCP 65 | Injunctive relief in scraping and departure cases |

Search the underlying materials directly for shipment data ownership platform terms, freight rate benchmarking antitrust, logistics API scraping unauthorized access, customs broker client confidentiality, and driver telematics monitoring privacy.

Forms and Templates

A data use matrix rather than a data ownership clause, mapping each category of shipment data to permitted uses: operational, customer-facing analytics, aggregated benchmarking, third-party sale, and post-termination retention. Ownership arguments are unwinnable; use allocation is drafted in an afternoon.

A benchmarking annex with explicit consent, minimum contributor thresholds, small-cell suppression rules, a stated methodology, a competition review record, and honest terms about historical data after a contributor leaves.

A carrier data rider addressing rate confidentiality, whether rates may appear in comparison products, and what happens on termination — because carriers are the party most likely to sue over a benchmarking product.

An API terms document with rate limits, permitted uses, prohibitions on automated collection, reseller flow-down, versioning commitments, and a deprecation notice period.

An integration ownership schedule identifying which connections were built by whom, what documentation exists, and what transfers on exit. This is the sector's most valuable undocumented asset.

A separation architecture description for platforms serving competitors, covering access controls, environment separation, internal mobility rules, and audit — publishable, because publishing it wins business.

An exit and portability annex: export format with schema documentation, historical data scope, transition assistance priced in advance, deletion obligations reconciled with regulatory retention and aggregate products, and a continuity mechanism.

A regulatory data element map, identifying which fields are prescribed, which are publicly obtainable, and which confidentiality promises therefore cannot be made.

A telematics and monitoring notice pack for drivers and warehouse staff, with purpose specificity and retention.

A consumer tracking page privacy notice, since these are ordinary web properties treated as operational tools.

A scraping response protocol, with terms of use, technical controls, evidence preservation, and a decision rule about when to escalate.

A customer list and integration know-how protection memorandum, recording what is treated as confidential, so that a departure claim has a foundation.

For general drafting starting points, see the Draft License Agreement and the License Agreement Template.

Five recurring matters

A shipper discovers its data appears in a benchmarking product. The first question is what the agreement permits, and the answer is usually a general licence clause that does not clearly authorise it. The second is whether the aggregation actually anonymises, which on thin lanes it often does not. Settle forward with an explicit annex, thresholds, and an opt-out, because litigating the clause is expensive and the relationship is the asset.

A competitor scrapes tracking and rate data from public pages. Assemble the theories — contract via terms of use, unauthorised access under 18 U.S.C. § 1030 as narrowed by Van Buren, and copyright in any protectable compilation — and be realistic that technical controls and rate limiting will do more than any of them. Preserve evidence of access patterns early.

A carrier objects to appearing in a rate comparison. This is the most litigable complaint in the sector because the injury is direct. Check whether the rates were supplied in confidence, whether the agreement addresses comparison products, and whether the presentation identifies the carrier. Suppression and aggregation thresholds resolve most of these.

A large customer terminates and demands its data plus deletion. Export in a documented format, scope historical data honestly, and be truthful about what cannot be removed from aggregate products. A promise of deletion that the provider will not keep is worse than a negotiated carve-out.

A platform serving three competitors is asked about separation. Answer with architecture rather than assurances: access controls, separated environments, internal mobility rules, and an audit. Customers who ask this question are deciding whether to participate at all, and a documented answer is a commercial advantage.

What good looks like

A data use matrix exists and is the same document in every customer agreement, so the provider knows across its book what it may do.

Benchmarking has an annex, thresholds, and a competition review, rather than resting on a general licence clause.

The integration estate is documented — connections, mappings, and quirks — and treated as confidential, which is both protection and transaction readiness.

API terms match the technical controls. Rate limits, versioning, and deprecation notice are enforced by the platform, not merely recited.

Regulatory data elements are mapped, so confidentiality promises are ones the provider can keep.

Separation architecture is documented and published where competitors share the platform.

Exit terms are real: documented export format, priced transition assistance, honest deletion terms, and a continuity mechanism.

Driver and warehouse monitoring has purpose-specific notices and short retention, rather than an acceptable-use clause doing all the work.

Providers with those eight negotiate from a position and survive a customer's departure without a dispute. Providers without them discover that the most valuable thing they built — the network — rests on terms drafted for a software business.