Start with a non-confidential brief
For the first discussion, describe the product category, intended use, markets and broad requirements without revealing proprietary details. If the project needs sensitive drawings, BOMs, algorithms or customer information, request an NDA before disclosing them. An inquiry form, an email request or this policy page is not itself an executed confidentiality agreement. Identify the actual legal parties and confirm that the people signing have authority to do so.
How to request an NDA
Send your company’s legal name, business address, project description, proposed disclosing and receiving parties and a contact person. If you have a preferred NDA template, share it through the agreed business channel. State whether information will flow in one direction or both. The parties should review and sign the agreed document before sensitive disclosure; a request does not promise immediate acceptance of every term or a fixed turnaround time.
Information to include in the scope
Confidential information may include drawings, specifications, BOMs, software, datasets, pricing, launch plans and business relationships, depending on the agreement. Define how written, visual, oral and electronic disclosures are identified. Discuss whether notes, samples, derived analysis and copies are covered. Clearly describe the permitted evaluation or development purpose. Avoid assuming that every routine communication is confidential if the signed document uses a narrower definition or a marking requirement.
Permitted recipients and use
The agreement should identify who can receive the information and on what basis. A project may need technical staff, an approved testing partner or a manufacturing participant. Discuss necessary access, equivalent confidentiality obligations and approval for additional recipients. Define restrictions on use, copying and disclosure. If subcontractor participation matters to your risk review, clarify it before files are shared rather than after sensitive materials have reached an unapproved party.
Exclusions and required disclosure
Common NDA discussions distinguish protected material from information already lawfully known, independently developed, publicly available without breach or legitimately received from another source. The agreed document should define any exclusions and the evidence needed to apply them. It should also address a legally required disclosure, including notice and a limited disclosure where permitted. This overview does not create an exception broader than the executed NDA or override a binding legal obligation.
Duration, return and retention
Agree the disclosure period and how long confidentiality duties last. These periods can differ from the project’s commercial timeline. State what happens to samples, files, notes and copies when evaluation ends. Discuss return or deletion, any legally required records, routine backups and restrictions on retained material. Do not assume an immediate deletion of all email and backup copies is technically possible unless the agreed process describes how it will be achieved.
No automatic license or exclusivity
Receiving confidential information should not be confused with receiving a patent, copyright, software or manufacturing license. Ownership, development deliverables, permitted manufacture and exclusivity need their own agreement. An NDA also does not place an order, guarantee project feasibility or commit either party to a supply relationship. Review IP Protection for the separate questions of background technology, tooling, software rights and project handover.
Sharing files after signature
Use the agreed email recipients or secure transfer channel. Name files clearly, include revision identifiers and keep a record of disclosure and approvals. Share only what is necessary for the current work package. Do not add patient records, passwords or unrelated personal information to a hardware project brief. If access credentials are needed for a technical test, arrange restricted project access separately instead of placing live credentials in an ordinary RFQ.
Incident review and next steps
If information is sent to the wrong recipient or you suspect unauthorized disclosure, promptly contact the agreed project contacts, identify the affected files and explain what happened. The parties should review access, preserve relevant records and decide the response under the NDA and applicable law. Do not make unverified public accusations or redistribute the sensitive material while investigating. Keep confidentiality questions distinct from commercial performance disputes so the appropriate records can be reviewed.
Common questions
Can we share our BOM before an NDA is signed?
Use a non-confidential summary first. If the BOM is proprietary, agree and execute the appropriate confidentiality arrangement before disclosure.
Can we use our own NDA template?
You can propose a template for review. The binding terms are the document accepted and signed by the actual parties.
Does an NDA transfer the design to STAR KING?
An NDA addresses confidentiality. Ownership and licenses must be dealt with separately in the project agreement.
Questions about your project?
For a business inquiry or policy clarification, contact the STAR KING team. Identify your company, product or order reference and the question you want to resolve. Use a non-confidential summary until a suitable file-sharing or confidentiality arrangement is agreed.