DATA & DEPLOYMENT

How your data is used and deployed.

Understand what belongs to your company, what a review shares and which deployment terms are agreed before work begins.

Company-specific knowledge

Your drawings, plant rates, manufacturing rules and proprietary learning remain within your company context. General software improvements are distinct from that content; ownership and permitted use are recorded in the engagement terms.

Separate buyer and supplier runs

A buyer’s reference analysis does not expose the supplier’s confirmed factory. Sharing a quotation or agreed result is distinct from sharing internal machine rates, constraints and estimating knowledge.

Approved learning with a scope

Reusable corrections retain the evidence, owner and applicable plant or process. A one-off assumption stays local to its case rather than automatically becoming a company-wide rule.

Agree the deployment record before activation.

Hosting, retention and integrations depend on the selected architecture. Record these decisions with your IT and security team; the website does not specify a universal retention period or deployment configuration.

Data path

Hosting location, model-provider processing and any information crossing the customer environment boundary.

Access and records

Who can read, change and approve each type of record; the logging evidence available for the chosen setup.

Retention and exit

Agreed retention, deletion and export arrangements for source documents, generated records and Company DNA.

System connections

The approved integration path, data exchanged, update frequency and ownership of each connection.

Discuss your deployment requirements