A data license agreement sets out who the parties are, exactly which data is covered, what a buyer may do with it and for how long, what each side promises, and how and when the owner is paid. At Paid4Data the paperwork is four documents: a mutual NDA, the data license, a Data Schedule attached to the license, and processing terms where UK or EU personal data is involved.
This article describes what the Paid4Data site says those documents contain. It does not quote clause wording, and it is general information, not legal advice. Your lawyer should review the actual documents, which is expected and built into the timeline.
The four documents and when you see them
| Document | When | What it does |
|---|---|---|
| Mutual NDA | Before the 30-minute scoping call | Covers anything either side shares. No data changes hands under it. |
| Data license | After the call, with the offer | Grants a non-exclusive license to de-identify your data and license it to AI buyers, with your warranties, Paid4Data's obligations and payment terms. |
| Data Schedule | Part of the license | Lists approved systems, date ranges, exclusions, restricted buyers and your payout share. |
| Processing terms | Only where UK or EU personal data is involved | Cover how data is handled before it is de-identified. |
The steps around these documents are on the how it works page.
Parties, definitions and the grant
Parties and definitions
The opening of any contract names who is bound by it. For a data license, that means the legal entity that controls the records, which is not always the trading name on the door. A single business unit, a closing practice or a wound-down fund can be the licensor if it controls the records and has the right to license them. The person signing needs authority to bind that entity.
Definitions matter because later clauses rely on them. The raw data you export and the de-identified dataset built from it are different things. Raw exports are deleted. The de-identified dataset is what buyers receive.
The grant and the permitted use
The grant is the sentence that gives permission. In Paid4Data's license it is a non-exclusive license to de-identify your data and license it to AI buyers. It is not a transfer of ownership. The company keeps ownership of its records.
Each license to a buyer then names:
- The use: training, evaluation or both. Training means using the data to teach a model. Evaluation means using it to test how well a model performs.
- The access mode: delivered files or hosted access, and in what format.
- Exclusive or non-exclusive: the trade-offs are in exclusive vs. non-exclusive data licensing.
The Data Schedule
The schedule is the part most owners should read twice, because it turns a general agreement into one about your company. It lists:
- Approved systems. Each source is named, for example a CRM, an accounting system or a helpdesk.
- Date ranges. The years of history included from each system.
- Exclusions. Accounts, customers or record types you have taken out. Payroll and HR records are always excluded, and some categories are never accepted at all, including health records, payment card and bank account numbers, government ID numbers, data about children and biometric data.
- Restricted buyers. Any competitor you name is barred from buying.
- Your payout share. The percentage of net receipts you receive on each sale.
If a system, a year or a customer is not on the schedule, it is not part of the deal.
Term, deletion and exclusivity
Two different clocks run under these documents.
The first is for your raw exports. Paid4Data deletes them within 30 days of finalizing the de-identified dataset, with written confirmation on request. The keys linking pseudonyms back to real names are kept separate and destroyed with the raw data.
The second is for each buyer. The license states the term, meaning how long the buyer may use the dataset, and a deletion date, meaning when the buyer must delete the data and confirm it.
Exclusivity belongs with the term because it is also about time. If a buyer wants to be the only one with the dataset for a period, the license says so and says for how long. Unless you agree otherwise, licenses are non-exclusive.
Warranties and buyer restrictions
Seller warranties: what you promise
A warranty is a promise, written into a contract, that a stated fact is true. In a data license the central warranty from the seller is about rights: that the company has the right to share the records listed in the schedule.
That promise is yours to check, and it is why the scoping call covers customer contracts and anything you want excluded. The five questions to work through are in can you legally sell your company's data. If you are unsure about a source, the schedule lets you leave it out.
Buyer restrictions
Your warranties are matched by limits on the other side. According to the security page, buyers contractually cannot:
- re-identify people or companies in the dataset;
- redistribute raw data;
- use it to compete with you.
Buyers also agree to delete records if they ever discover they can identify someone. No buyer sees data that has not been de-identified.
Confidentiality and the mutual NDA
The NDA comes first and is mutual, so it binds both sides. It covers what is said on the scoping call and anything either side shares, including the buyer's name, which Paid4Data discloses on the call. No data is transferred under the NDA. Data moves only after the license is signed, by secure upload or temporary read-only access, never by email.
Processing terms for UK or EU personal data
If your records include personal data about people in the UK or EU, data protection law applies to the raw data until it is de-identified, and the license comes with processing terms.
Article 28(3) of the EU General Data Protection Regulation says that processing by a processor must be governed by a contract that sets out the subject matter and duration of the processing, its nature and purpose, the type of personal data, the categories of people it relates to, and the controller's obligations and rights. The contract must require the processor to:
- process the data only on the controller's documented instructions;
- make sure the people handling it are bound by confidentiality;
- take the security measures the regulation requires;
- follow the regulation's conditions before engaging another processor;
- help the controller respond to individuals exercising their rights;
- delete or return the personal data at the end of the service, at the controller's choice;
- make available the information needed to show compliance, and allow audits.
Article 28(9) requires that contract to be in writing, which includes electronic form. The UK Information Commissioner's Office lists the same contents for contracts under the UK GDPR. Ask your lawyer whether these laws apply to your records.
Payment, statements and termination
Payment clauses in this license are tied to actual sales. Your share is the percentage of net receipts set in your Data Schedule. You are paid within 7 days of a buyer's payment clearing, with a statement for each sale showing the buyer category, date and amount.
No payment is owed until a buyer pays. No price or sale is guaranteed, and the license sets the real terms.
You can change your mind at any point before you sign the data license. After signing, the license's termination terms apply. The site does not publish those terms, so read that section with your lawyer and ask what happens to licenses already granted to buyers if the agreement ends.
More short answers are in the FAQ. To see the documents for your own company, request a free data review.
Sources
Checked on November 16, 2026.
- Regulation (EU) 2016/679 of the European Parliament and of the Council (General Data Protection Regulation), Article 28, EUR-Lex, Publications Office of the European Union
- What needs to be included in the contract?, Information Commissioner's Office (UK)