How is the technical information and intellectual property I share in a custom project protected?
Technical documents, schematics and implementation details shared during custom project discussions are used only for evaluating that project. Headings such as the scope of confidentiality, who the intellectual property will belong to, and permission to be named as a reference are clarified in writing at the start of the project.
Custom production requests often contain details about the customer's own machine, process or commercial information. For that reason we recommend that the following headings be put in writing before the project starts:
- Scope of confidentiality: which information counts as confidential, who may access it, and how long the confidentiality obligation lasts.
- Intellectual property: who will own the rights to the design, software and documentation produced at the end of the project; keeping separate the prior know-how each party brought into the project.
- Usage limits: whether the developed solution may be offered to other customers.
- Reference permission: whether the project may be named as a reference, and permission to share images.
In the first discussion the general framework of the application is usually enough; before sharing detailed schematics, code or production information, you may request that a mutual confidentiality document be signed.
Because the terms differ in every project, we do not impose a standard template. Send us your expectations through our contact page and let us build the working framework together.