Start with the intended use
Training, evaluation and retrieval are different activities. A buyer may want examples to update a model, held-out tasks to test it, or an indexed reference collection. Ask which use is proposed before discussing a sample. A broad phrase such as “AI purposes” leaves too much unresolved.
Define the deliverable
Describe the sources, date range, formats, exclusions and version. A support dataset, for example, might include eligible tickets and resolution labels while excluding attachments, payments and account credentials. A description is a starting point for review, not proof of permission.
Agree what happens next
A useful agreement addresses recipient access, reuse, downstream sharing, security, payment, acceptance and termination. Ownership of the software account does not establish rights to customer content inside it. Have the relevant legal and privacy questions reviewed before transfer.
Practical guidance, not legal advice or a buyer specification. Examples are illustrative. Reviewed October 20, 2026.