What licence and usage limits should we ask about before starting?

**Are the licence terms standard?**

Do not assume so. Terms are agreed for your engagement, so ask for them in writing before you begin and have your legal team review them.

**What should we ask about use?**

- Whether the release may be used for training, evaluation or both. - Whether models trained on it can be deployed commercially. - Whether use is limited to named teams, entities or environments.

**What about sharing and retention?**

Ask whether you may share the release with contractors or auditors, whether it can be published in part (for example in a paper or a customer demo), and how long you may keep it, including copies in training sets and checkpoints.

**What about derived material?**

Clarify who holds rights in your own graders, prompts and fine-tuned models built using the release, and whether you may combine it with your own data.

**What about changes?**

Ask how fixes work if you find realism or disclosure problems, how regenerations are versioned, and whether earlier versions must be retired.

**Does the licence settle privacy or regulatory questions?**

No. The output is generated, and a licence does not by itself establish that it meets your obligations. Run your own review of grounding and disclosure risk.

**Who should be in the first conversation?**

Bring an engineer, someone from legal or procurement, and a person responsible for data governance.