Compare data licensing terms

Put the same scope beside each proposal

Compare data licensing terms using one worksheet per proposal. Start with your company data summary, then note any requested additions, exclusions or ongoing updates. Two prices describe different deals if one covers a small historical export and the other includes future records. See what affects data value when comparing the scope behind each price.

Record the parties, date, currency and documents you received. Keep the marketing page separate from the proposed agreement. Ask which document controls if the order form, schedule and general terms disagree.

Protege's Provider Terms expressly say a signed Schedule controls a conflicting provision. Read the schedule even when you have already read the public terms. Protege Provider Terms, checked November 8, 2026.

Compare payment conditions

Write down the payment amount or formula and the event that makes it due. Then list every condition between signing and payment: sample review, acceptance, delivery, invoice or a later sale.

Mercor's data page describes wire payment on delivery of the anonymized dataset. Turing's current Lazarus FAQ describes revenue sharing and says the seller owes nothing if the record does not sell. These programs describe different ways of paying. Your agreement must state which payment you would receive and when. Mercor Data and Turing Lazarus, checked November 8, 2026.

For revenue sharing, ask what the percentage applies to, which deductions apply, when sales are reported and how you can check the calculation. Ask whether any minimum payment is contractual. For a fixed payment, ask what can cause rejection, a reduction or repayment.

Separate the uses and the rights

Ask the recipient to describe each permitted use in writing. Treat evaluation, training, testing, retrieval, onward licensing and making derived datasets as separate questions. Ask whether you approve downstream recipients or only the first contracting party.

Make a second list of rights you intend to retain. It might cover continued internal use, existing customer services, or licensing a defined subset elsewhere. Have your adviser compare that list with the proposed grant and restrictions.

SuperAnnotate's program page describes licensing for an agreed period and buyers the seller approves. Confirm how any promised control appears in the proposed agreement and who can change it. SuperAnnotate data partnerships, checked November 8, 2026.

Read exclusivity at each stage

Ask whether exclusivity covers the records, a field of use, a buyer group or the right to market the records. Record its start, end, renewal and exit conditions. Keep existing licenses on the same worksheet.

Turing's Lazarus page and FAQ describe an initial 90-day period when Turing alone sells the record, while describing downstream lab licenses as non-exclusive. Those statements cover different stages. Record both instead of reducing them to one exclusive-or-not answer. Turing Lazarus, checked November 8, 2026.

Use this discussion checklist

A deletion promise about source files may leave other questions unanswered. Ask about copies, backups, derivatives and trained models separately rather than assuming one sentence covers them all.

Use this worksheet to prepare for a review with your own legal and financial advisers. It cannot decide whether a particular contract suits you. Resolve rights questions before agreeing to share records, and use the buyer comparison to find each program's published information.

Use the offer worksheet for written proposals. The payment guide, delivery-schedule guide and derived-use guide explain the fields in more detail.