/app/licenses lists every license on your datasets and every buyer waiting for your approval.
You approve every buyer
No buyer receives any of your data until you approve them. When a buyer makes an offer, it appears here with the buyer's name and the proposed terms. You can approve or decline it. You can also tell us to exclude any company, including all of your competitors, and we will not offer your data to them.
What a license contains
| Term | Meaning |
|---|---|
| Uses | What the buyer may do with the data, such as training, fine-tuning or evaluation. |
| Length | How long the license runs. |
| Exclusivity | Whether other buyers can license the same dataset during the term. |
| History price | What the buyer pays for the records up to the first delivery. |
| Refresh price | What the buyer pays for each accepted monthly batch, if the license has a refresh term. |
| Status | The license's current state, such as whether its refresh term is active. |
Every license also forbids re-identifying anyone, reselling the data, and combining it with other data to identify people. See Licensing terms for the full list buyers agree to.
Refresh terms
A license with an active refresh term pays its refresh price for every batch of that dataset we accept. As long as the SDK keeps sending batches and the license keeps its refresh term, one dataset pays again every month. See How recurring revenue works.
Withdrawing a dataset
You can ask us to stop selling a dataset. We remove it from future sales, and existing licenses follow what your seller agreement says about withdrawal. Data a buyer already used to train a model cannot be removed from that model.