What limits apply, and how does licensing work for generated booking material?
A question-and-answer covering what the output is, what it is not, how licence terms are agreed, and which assumptions a buyer should check themselves.
**Is any of this real business data?**
No. MirrorFirm provides generated, synthetic material. It is informed by direct observation of how real businesses operate, but it is not a copy of any organisation's records.
**Does generated mean anonymous or compliant?**
No such conclusion should be drawn. Generated output can still resemble real patterns too closely, so inspect a sample for grounding and disclosure risk, and run your own review against your obligations.
**Does it cover every lender or product?**
No. A release reflects the scope agreed, such as one product type and a set of task families. Systems, policies and field names in your organisation will differ, and the data should be treated as a starting point for your environment.
**How is licensing handled?**
Licence terms, permitted uses such as training, evaluation or internal tooling, and delivery arrangements are agreed with MirrorFirm during scoping. Ask for them in writing before you build on a release.
**Can the data be used to train a model?**
That depends on the licence you agree, so state your intended use at the start.
**What is a sensible first step?**
A small sample with agreed checks.
Know the limits before you start: the material is generated, grounding and disclosure should be inspected, and terms are agreed directly.
- Audience:
- Environment builders
- Content type:
- FAQ
- Buyer question:
- Scope and getting started
Content release: r-a220eb6e099b243b
Related questions
- What does a first pilot look like for an agent team in vendor finance?
- What limits apply, and will we receive any real customer records?
- How could a pilot be delivered, versioned and wired into our CI?
- How should a team scope and license a generated booking pack?
- What should we ask for in a sample or pilot of generated booking material?
- How should a sample be delivered, versioned and load-checked in my pipeline?