The data may already exist. What you licence is the record that lets you use it.

YPAI licenses rights-cleared datasets it owns, and it represents datasets from partner suppliers as curated dataset sourcing, with rights and availability verified before you see a sample. Where the data you need exists somewhere else, YPAI sources it to order. Where it does not exist yet, YPAI collects only that gap. The four forms sit on one line, from data YPAI already holds to data collected for you, and the same consent and licence trace applies to all of them.

Under NDA you see dataset cards, the inventory that matches your requirement, prices, provenance descriptions, technical specifications, genuinely anonymised or controlled samples, and partner and sourcing information where the partner agreement allows it. The NDA is the first gate, and it opens the inventory. Training rights, evaluation on production data, resale, sublicensing, white-label rights, access to personal data and keeping samples are granted by the licence that follows.

A Dataset Licence Agreement, or a Master Services Agreement with a Statement of Work and a Data Licence Schedule. The schedule names the dataset, the licensor authority, the permitted uses, the derivative rules, sublicensing, territory, term and exclusivity, and it records the consent version that was active when the data was made. Samples and evaluation material provided before signature are deleted at YPAI's request once evaluation ends.

Each record carries the agreement that authorised it, the consent version that was active, the rights that applied when it was created and the uses allowed now, together with its lineage and an integrity check. The same record answers a contributor's withdrawal: the affected records, datasets and deliveries are identified and the remediation procedure applies to your copy. The record ships with the delivery, in machine-readable dataset metadata, so your compliance team reads it rather than takes it on trust.

Yes. Licences are structured exclusive or non-exclusive, term-based or renewing, with territory, permitted use and downstream-rights structures set in the schedule. Exclusivity is most often agreed for data collected to order, where the dataset is built against your requirement. The structure is agreed at scoping, together with the commercial terms.

Then that part is collected. YPAI names the gap against your requirement, missing languages, accents, age groups, scene or session types, formats, annotation or rights scope, and collects only that, under the same consent and rights controls as the inventory. Licensing what exists and collecting only the gap shortens the project and lowers its capital need compared with collecting everything from zero.

Yes, as white-label supply, where the end client does not necessarily contract with YPAI directly. That structure is written precisely: sublicensing, white-label rights, end-client disclosure, permitted use, model training, evaluation, derivative models, term, territory, exclusivity and indemnity are each set in the agreement.

Describe the need in the form above: what data, for what use, which modality, whether existing inventory is acceptable, and whether an NDA is in place. A named person reads it and comes back with what exists, what can be sourced through partners, and what would be collected, and the NDA is put in place before any inventory or sample is shared.