Breshev Engineering · Project trust

Engineering data handling, NDA and intellectual property.

Confidentiality is part of engineering scope, not a footer disclaimer. Before project files are transferred, the parties define what data is needed, where it may be handled, who may access it, how long it is retained and what each result is allowed to disclose.

Discuss NDA or data handling AURA pilot process

Do not send confidential CAD, test data or customer files during the initial fit check. Machine type, speed range, constraints and the required decision are sufficient for the first conversation.

1 · Before transfer

The initial conversation uses the minimum non-confidential information needed to establish technical fit. NDA and project-specific data terms can be agreed before detailed geometry, reports, test traces or customer material are requested.

2 · Written scope

The engagement scope identifies required inputs, approved transfer route, permitted uses, access boundary, expected deliverables, retention period and any client-specific restrictions.

3 · Data minimisation

Only information needed for the agreed engineering decision should be transferred. When possible, identifiers and unrelated commercial information are removed before technical review.

4 · Access and storage

Project terms define where working files are held and who may access them. Client material is not published, added to the public validation registry or used in a public example without written permission.

5 · AI boundary

Client engineering files are not used to train public or shared AI models. Any project-specific use of AI involving confidential material requires an explicit written basis and remains subordinate to deterministic engineering review.

6 · Retention and deletion

Return, retention or deletion is handled according to the written project scope and any legal or contractual record requirements. A deletion confirmation can be included where agreed.

Intellectual-property boundary

Client background IP: pre-existing client geometry, data, processes and know-how remain the client's property.
Breshev Engineering background IP: AURA, its solver, methods, reusable software components and pre-existing templates remain Breshev Engineering property.
Project deliverables: ownership and permitted use of reports, configured cases, generated data and project-specific code are stated in the proposal or contract.
Public disclosure: no client name, logo, case result or identifiable project detail is used publicly without written authorisation.

Practical rule: confidentiality, evidence authority and release responsibility are three separate questions. Each is recorded explicitly before a project moves beyond the fit check.