Skip to content
MirrorFirm

What licence terms and limits should I expect for a sufficiency release?

Licence terms are agreed per release in writing; the output is generated rather than real records, and buyers remain responsible for inspecting grounding and disclosure risk and for their own compliance.

**What do the licence terms cover?**

Terms are set in the agreement for each release, so we do not state them here. Ask for them in writing, and say how you intend to use the material: model training, offline evaluation, a regression suite, a demonstration, or a combination. Intended use is a reasonable thing for the agreement to address.

**Is the data real?**

No. The commercial output is generated, synthetic material. MirrorFirm's approach is informed by direct observation of how real businesses operate, but a release does not deliver real business records.

**Does generated data settle privacy or regulatory questions?**

No, and you should not treat it that way. Generated output does not make a use compliant, and it does not by itself remove disclosure risk. Inspect samples for details that look too specific to a real source, ask what grounding each element has, and put the release through your own review.

**What limits should I plan for?**

- A release covers the case types, policy versions and formats agreed in scope. - Labels reflect the stated policy, and your own policy may differ in details. - A pilot sample shows fit; it does not show how an agent will behave across all your cases.

Prices, timelines and service levels are agreed for a specific scope and are not set out here.

Ask for terms in writing, state your intended use up front, and treat compliance and disclosure review as your own task.

Audience:
Agent developers
Content type:
FAQ
Buyer question:
Scope and getting started

Content release: r-a220eb6e099b243b

More on Document sufficiency