Skip to content
MirrorFirm

What can I license, what limits apply, and what should I bring to a first conversation?

A question-and-answer on licensable forms, the limits of generated output, why privacy or compliance should not be assumed, how changes are raised, and what to prepare.

**What can I license?** A buyer can ask to license a dataset, a task and evaluation pack, or a simulated environment, and can state the intended use: training, evaluation, internal research or product work. Terms are agreed with MirrorFirm directly. This page does not set out prices, timelines or contract terms.

**What limits apply to the output?** The output is generated. It does not contain real business records, and it should not be read as evidence of what any particular organisation does. Coverage is limited to the domains, channels, rules and tools agreed in scope.

**Does generated data remove privacy or compliance concerns?** No. Do not treat it as anonymised or as approved by any regulator. Generated text can still resemble real details by chance or through the way it was produced, so inspect a sample for grounding and disclosure risk, and apply your own review process.

**Can I ask for changes after seeing a sample?** Yes. You can raise ambiguities, missing exception paths or imbalance in case types, and ask for them to be addressed in a later version. Agree how changes are handled when you scope.

**What should I bring to the first conversation?** The task you want a model to do, the domain, the formats you accept, how you will evaluate, and any constraints on how the material may be stored or used.

**Can I restrict the pilot to evaluation only?** You can state that intent when scoping, and the licence can reflect it.

Come with a task, a domain, accepted formats and an evaluation plan, and treat privacy and grounding as things to inspect rather than assume.

Audience:
Model labs
Content type:
FAQ
Buyer question:
Scope and getting started

Content release: r-a220eb6e099b243b

More on Application intake