Business model
Sales qualification, privacy and model validation design, compliant SOW, and private environment.
Company & claims
Trust starts with a claim that can survive review.
MirrorFoundry separates proposed controls from proven controls, avoids automatic anonymisation claims, and defines the evidence a customer should expect before any synthetic release.
06
Delivery modelPublished
Privacy & termsPublished
Security obligationsContract-defined
Release qualityEvidence required
Operating facts
What a buyer can confirm before qualification.
These facts describe the current product preview, go-to-market, and delivery model. They are not a claim that statutory operator disclosures or production contracting are complete.
Operating region
European operations serving regulated and data-scarce organisations.
Access model
Customer-admin invitation after implementation and acceptance; no public signup.
Commercial contact
itops@mirrorfoundry.aiRelease evidence pack
Proof should be produced by the workflow—not added after the decision.
Every engagement should leave a reviewable chain from intended use and source scope to an accepted data or model decision.
Intended-use record
The decision, affected groups, permitted uses, exclusions, and accountable business owner.
Source profile
Approved fields, entities, relationships, sensitivity, constraints, holdout design, and retention.
Threat model
Similarity, linkage, inference, memorisation, and rare-record risks to test.
Utility protocol
Statistical, constraint, analytical, and model tasks with acceptance thresholds.
Observed results
Generator configuration, privacy results, fidelity, task performance, model scenarios, and exceptions.
Release decision
Named sign-off, limitations, permitted use, expiry or review date, and remaining risks.
Claims policy
What MirrorFoundry will not imply without evidence.
✓AnonymisationNot claimed automatically; release risk depends on data, generator, tests, and intended use.
✓Customer logosPublished only with customer authorisation.
✓Performance metricsPublished only with a defined baseline, task, population, period, and source.
✓Security certificationsNamed only after the certification is current and independently verifiable.
✓Regulatory complianceRequirements are evaluated in diligence and written into the applicable agreement.
Start with one release
Ask for the evidence before approving a release.
Bring company, privacy, legal, security, and model-validation requirements into qualification so the SOW can make every obligation explicit.
Request an assessment