Legal

Data supply agreement

The terms on which a data owner licenses data to DataBroker, so DataBroker can list and sell licenses to it and pay the owner a share.

Updated

1. About this agreement

This agreement is between DataBroker LLC, a Delaware limited liability company (“DataBroker”), and the company that accepts it (the “Data Owner”). It is made up of these standard terms, one or more Dataset Schedules, and the Data processing addendum. If they conflict, the Data Processing Addendum wins on personal information, then the Dataset Schedule for its dataset, then these terms. The person accepting confirms that they may bind the Data Owner.

2. Words with a set meaning

  • Dataset Schedule: a schedule both sides accept, in the app or in writing, that describes a dataset and sets its terms: its description and format, how and how often it is delivered, the revenue share, payout timing and minimum payout, notice periods, whether it is exclusive, the Release Standard, any minimum price, the buyer license terms allowed (including whether perpetual licenses may be sold), any insurance or reserve required under section 13, and any limits on use or on where it may be sold. A signed data license between the two sides that sets these terms counts as a Dataset Schedule.
  • Supplied Data: the data, files, code, documentation and metadata the Data Owner delivers under a Dataset Schedule, including updates.
  • Marketplace: a third-party platform on which DataBroker lists and sells data licenses.
  • Buyer: anyone who buys a license to Supplied Data from DataBroker, directly or through a Marketplace.
  • Buyer License: the license DataBroker or a Marketplace grants a Buyer.
  • Derived Data: data created from Supplied Data that does not reproduce it in substance, such as statistics, labels, annotations, embeddings, quality scores and summaries.
  • Sample: a limited extract, preview, schema, file listing or redacted view of Supplied Data used to describe it to prospective Buyers.
  • Personal Information: information about an identified or identifiable person, as defined by the privacy law that applies.
  • Release Standard: the level of de-identification the Supplied Data must meet before a Buyer receives it, as set in the Dataset Schedule. If none is set, the Release Standard is “no Personal Information”.

3. Delivering the data

The Data Owner delivers the Supplied Data through the upload or transfer methods DataBroker provides, in the format and on the schedule in the Dataset Schedule, with documentation that accurately and completely describes what it contains, where it came from and any limits on its use. The Data Owner will tell DataBroker promptly if it learns that anything in that description is wrong.

4. The license to DataBroker

The Data Owner grants DataBroker a worldwide, royalty-free (apart from the revenue share in section 9) license, for the term of each Dataset Schedule and as long afterward as section 14 allows, to:

  • receive, store, host, copy and keep the Supplied Data;
  • examine it, test it and run quality, security and privacy checks on it;
  • clean, normalize, reformat, deduplicate, label, annotate, index, de-identify, pseudonymize, redact and otherwise process it, including to meet the Release Standard;
  • create Derived Data and Samples from it;
  • describe, display and market it, including with Samples, metadata and the results of checks, on Marketplaces and elsewhere;
  • sell and grant Buyer Licenses to it, directly or through Marketplaces, and let Marketplaces grant Buyer Licenses on DataBroker's behalf;
  • deliver it to Buyers and Marketplaces, and support Buyers with updates and corrections.

The license is non-exclusive unless the Dataset Schedule says it is exclusive. DataBroker may let its affiliates, contractors, service providers and Marketplaces do any of these things for it, and is responsible for them. DataBroker may transfer the license only with this agreement as a whole (section 17).

5. Buyer Licenses

DataBroker sets the terms of Buyer Licenses, within what the Dataset Schedule allows. Every Buyer License will at least:

  • forbid the Buyer to resell, publish, redistribute or sublicense the Supplied Data as such, or to use it to offer a data service to others;
  • forbid any attempt to re-identify people in it;
  • carry the limits on use stated in the Dataset Schedule;
  • require the Buyer to delete the data when the license ends, unless the Dataset Schedule allows a perpetual license.

Unless the Dataset Schedule says otherwise, Buyers may use the data for their internal business purposes, including to train, fine-tune, test and evaluate machine learning models. Models and their outputs are not Supplied Data unless they knowingly reproduce a substantial part of it.

6. Listing and pricing

DataBroker decides whether, where and when to list Supplied Data, how to describe it within the documentation, and what to charge, subject to any minimum price in the Dataset Schedule. DataBroker may decline, pause or remove a listing at any time. It does not promise that any dataset will be listed or sold, or at any price. DataBroker will not name the Data Owner publicly as the source unless the Dataset Schedule allows it.

7. Ownership

The Data Owner keeps ownership of the Supplied Data. DataBroker owns Derived Data, Samples it creates, listing material, and its own tools and methods. Buyers own what they create under their Buyer Licenses. Nothing else is transferred.

8. The Data Owner's promises

The Data Owner promises, for as long as any license under this agreement lasts, that:

  • it is validly organized and has authority to enter this agreement;
  • it owns the Supplied Data or holds every right needed to grant the licenses in sections 4 and 5, and nothing it has agreed with anyone else conflicts with them;
  • the Supplied Data was collected and is supplied lawfully, without breaking any contract, terms of service, confidentiality duty or technical access restriction;
  • using the Supplied Data as this agreement allows will not infringe anyone's intellectual property, privacy or other rights;
  • its documentation is accurate and complete, and identifies any third-party or open-source material and the terms that apply to it; no such terms require a Buyer to publish or license its own code, models or data;
  • the Supplied Data contains no malware and no passwords, keys, tokens or other credentials;
  • it contains no Personal Information beyond what the Release Standard and the Data processing addendum allow, and none of the following unless the Dataset Schedule expressly permits it: special category or sensitive data (such as health, biometric, genetic, racial or ethnic origin, religion, sexual life or orientation, union membership, or criminal records), data about children under 16, government identification numbers, financial account or card numbers or credentials, or precise geolocation;
  • where the Supplied Data contains Personal Information, the Data Owner has a lawful basis and has given every notice and obtained every consent needed for DataBroker and Buyers to use it as this agreement allows;
  • it has told DataBroker the export control classification of the Supplied Data, if it has one, and the data is not subject to sanctions that would prevent its sale.

If Supplied Data does not meet these promises or its documentation, the Data Owner will fix it within 30 days of DataBroker's notice. If it does not, DataBroker may remove the dataset, refund Buyers, and recover those refunds and its reasonable costs from the Data Owner, in addition to its other rights.

DataBroker promises that it will use the Supplied Data only as this agreement allows, and will put the restrictions in section 5 in every Buyer License. Apart from the promises in this agreement, neither side gives any warranty, express or implied.

9. Revenue share

DataBroker pays the Data Owner the revenue share stated in the Dataset Schedule (your signed data license) for that dataset, applied to Net Receipts. Net Receipts means the money DataBroker actually receives from Buyers and Marketplaces for Buyer Licenses to the Supplied Data, after:

  • Marketplace fees and commissions, and payment, currency conversion and payout fees;
  • sales, use, value-added and similar taxes collected, and taxes withheld at source;
  • refunds, credits, chargebacks, payment reversals and dispute fees.

Where a sale bundles several datasets, Net Receipts are divided between them in proportion to their list prices. Money from Derived Data that DataBroker sells on its own is not Net Receipts unless the Dataset Schedule says so.

10. Statements and payouts

DataBroker shows each sale in the app and pays the Data Owner's share for each month in which it receives the money, on the payout timing and above the minimum payout stated in the Dataset Schedule; smaller balances carry forward. Payments are in U.S. dollars to the account the Data Owner names. The Data Owner must give a valid tax form before it is paid, and DataBroker may withhold tax where the law requires.

A Data Owner that disputes a statement must say so within 60 days. Once a year, on 30 days' notice, it may have an independent accountant bound by confidentiality check the records behind its payouts, at its own cost unless the check shows an underpayment of more than 5%, in which case DataBroker pays the reasonable cost of the check and the shortfall.

11. Refunds, disputes and netting

If money that counted toward a payout is later refunded, reversed, charged back or taken back by a Marketplace, the Data Owner's share of it is deducted from later payouts, or repaid within 30 days of request if no payouts are due. If a refund or a Buyer claim results from the Data Owner breaking this agreement, the Data Owner also bears DataBroker's share of the refund and its reasonable costs. DataBroker handles disputes with Buyers and Marketplaces and will consult the Data Owner before agreeing to a refund that the Data Owner must bear in full.

12. Indemnities

By the Data Owner. The Data Owner will defend DataBroker, its affiliates, and the Marketplaces and Buyers it has licensed, against any claim by a third party or a regulator, and pay the resulting losses, fines, settlements and reasonable legal costs, to the extent the claim alleges facts that would breach section 8, or that the Supplied Data infringes anyone's rights or was collected or supplied unlawfully. Amounts DataBroker must pay a Marketplace or Buyer under a final decision or an approved settlement under the terms that govern that Marketplace or Buyer count as losses, even if that decision is reached under another law or forum.

If the Supplied Data is, or seems likely to be, the subject of an infringement claim, the Data Owner will at its cost get the rights needed for it to continue to be used, or replace it with non-infringing data of equal quality; if neither is reasonably possible, DataBroker may remove it and the Data Owner will reimburse refunds DataBroker gives Buyers as a result.

By DataBroker. DataBroker will defend the Data Owner against any third-party claim, and pay the resulting losses and reasonable legal costs, to the extent it arises from DataBroker using the Supplied Data beyond the license in section 4, or failing to include the restrictions in section 5 in a Buyer License.

Process. The side seeking protection will tell the other promptly, give reasonable help at the other's cost, and let it control the defence. Where a Marketplace or Buyer brings a claim against DataBroker, DataBroker may control the defence itself, at the Data Owner's cost where the Data Owner owes the indemnity. No one may settle in a way that admits fault for the other side or binds it without its consent, which it will not unreasonably withhold.

13. Limits on liability, insurance and reserves

Neither side is liable for indirect, incidental, special, consequential or punitive losses, or for lost profits, even if told they were possible. Each side's total liability under this agreement is limited to the greater of the amounts paid or payable to the Data Owner under it in the 12 months before the event giving rise to the claim, and any minimum amount stated in the Dataset Schedule.

These limits do not apply to the indemnities in section 12, to a breach of section 8 or of the Data Processing Addendum, to a breach of confidentiality, or to fraud or wilful misconduct.

Insurance or a reserve. So that the Data Owner's promises and indemnity are backed by something real, DataBroker may require, in the Dataset Schedule or later by reasonable written request where a dataset's size, sensitivity or sales make it sensible, that the Data Owner either:

  • keeps insurance with a reputable insurer that covers its obligations under this agreement, such as cyber and privacy liability and technology errors and omissions (including intellectual property claims), at the limits the Dataset Schedule states, gives DataBroker a certificate of insurance on request, and tells DataBroker promptly if the cover is cancelled or reduced; or
  • at DataBroker's option, agrees that DataBroker may hold back part of the Data Owner's share as a reserve, as the Dataset Schedule states or as reasonably needed to cover a pending claim, refund or chargeback, and apply it to amounts the Data Owner owes under this agreement. DataBroker releases what is left of the reserve once the claim is resolved or the period in the Dataset Schedule ends.

Any requirement will be proportionate to the expected revenue and the risk of the dataset, and DataBroker will not ask for cover or a reserve for a dataset that is unlikely to cause loss. Insurance or a reserve does not limit what the Data Owner owes.

14. Term, takedown and what survives

This agreement starts when it is accepted and each Dataset Schedule lasts for the term it states, renewing for the same term unless either side gives notice. Either side may end a Dataset Schedule, or this whole agreement, for any reason by giving the written notice the Dataset Schedule states, or on 30 days' notice if the other side breaks it materially and does not fix the breach within that time.

Takedown. The Data Owner may ask DataBroker to stop new sales of a dataset on the notice the Dataset Schedule states for takedowns. It may require DataBroker to stop new sales at once, and to stop delivering updates, only if continuing would break the law or a court order, or because of a security incident, or because a third party credibly claims the data infringes its rights. DataBroker will then remove the listing as soon as reasonably possible, and tell Marketplaces to do the same.

After the end. Buyer Licenses granted before a dataset is removed continue for their own term, and DataBroker may keep the copies it needs to support them, to meet legal duties and to resolve disputes. The Data Owner's promises and indemnities continue for as long as those Buyer Licenses last, and DataBroker keeps paying the Data Owner's share of money it receives for them. Otherwise, DataBroker deletes the Supplied Data without undue delay, and within any period the Dataset Schedule or the Data Processing Addendum sets. Sections 7, 9 to 13, 14, 15, 16 and 17 continue after this agreement ends.

15. Confidentiality and no going around DataBroker

Each side will keep the other's non-public information confidential, use it only for this agreement, and share it only with staff, advisers and service providers who need it and are bound to keep it confidential. The Supplied Data is the Data Owner's confidential information, except as the licenses allow. The identity of Buyers, prices and sales figures are DataBroker's. These duties last for three years after this agreement ends, and for as long as the information remains a trade secret or Personal Information. The usual exceptions apply: information that is public through no fault of the recipient, already known to it, received lawfully from someone else, independently developed, or that the law requires it to disclose after notice where lawful.

While this agreement is in force and for 12 months after it ends, the Data Owner will not sell or license the Supplied Data directly to a Buyer it learned of through DataBroker, other than through DataBroker. Contact needed to deliver, correct or confirm deletion of data is allowed. If the Dataset Schedule makes a dataset exclusive, the Data Owner will not license it to anyone else for the period the schedule states.

16. Personal Information and security

The Data processing addendum governs any Personal Information in the Supplied Data. DataBroker will protect the Supplied Data with reasonable security measures. De-identification lowers risk but cannot guarantee that no one could ever be re-identified, and DataBroker does not promise that it does.

17. Disputes, notices and general terms

Governing law. This agreement is governed by the laws of the State of Delaware, without regard to its conflict-of-law rules. The Federal Arbitration Act governs the agreement to arbitrate below.

Disputes. Before starting a claim, the side with the complaint will write to the other and both will try in good faith for 30 days to settle it. After that, any dispute arising out of or relating to this agreement, a Dataset Schedule or the Data Processing Addendum will be decided by binding arbitration administered by the American Arbitration Association under its Commercial Arbitration Rules, before one arbitrator, seated in Wilmington, Delaware. The award is final, and judgment on it may be entered in any court with jurisdiction. Either side may instead bring an individual claim in a small claims court if it qualifies there, and either side may ask a court for an injunction or other urgent relief to protect its data, confidential information or intellectual property, or to enforce section 15, without first going to arbitration; such court matters are heard in the state or federal courts located in Delaware. Claims may be brought only individually, not in any class, collective, consolidated or representative proceeding, and to the extent any dispute is heard in court, both sides waive any right to a jury trial.

Notices. Notices go to the email address each side gives: for DataBroker LLC, a Delaware limited liability company, team@data.broker. Notices by email are effective when sent, unless the sender receives a message that delivery failed.

Neither side may transfer this agreement without the other's consent, except to a successor to its business, with notice. Neither side is responsible for delays caused by events beyond its reasonable control; if such an event stops delivery for more than 14 days, DataBroker may refund affected Buyers and net those refunds as in section 11. This agreement, its schedules and the Data Processing Addendum are the whole agreement on this subject. Changes must be in writing and accepted by both sides. If a part is unenforceable, the rest still applies. The sides are independent contractors. Questions: team@data.broker.