Commercial confidentiality
Singapore Non-Disclosure Agreement: Protected Information and Permitted Use
Design a disclosure boundary that people can apply to actual files, meetings and recipients.
A Singapore non-disclosure agreement should identify the protected information, the permitted purpose, authorised recipients and the duties that continue when discussions end. A promise not to disclose is only part of the protection: the recipient’s use of the information must also fit the agreed purpose. Receiving information should not silently grant commercial-use rights.
Key takeaways
- Define what is protected with enough precision for staff to recognise the covered material.
- Keep the evaluation purpose narrower than any future licence or commercial collaboration.
- Specify who can receive information and how onward access is controlled.
- Contract language works best alongside access controls and a disclosure record.
Define the information and parties before sharing
IPOS trade secret guidance explains that Singapore primarily protects trade secrets through the law of confidence and has no registration process for confidential information. It recommends access restrictions, clear records, confidentiality agreements and staff training. A label on a file is useful evidence, but the business also needs a process that preserves confidentiality.
Write down the parties’ exact legal identities and the information each may disclose. Distinguish technical material, business plans, pricing, customer information, analyses and oral disclosures. Consider how the agreement should treat prior disclosures and information created from protected material.
If the intended contracting entity has not yet been established, resolve its identity under the Singapore company registration process before signing in its name. An existing founder and a future company are different parties; obtain advice on any interim arrangement or later transfer of contractual rights.
Identify the parties and disclosure boundary
Clarify which company owns the information and which entity will receive it.
Translate the permitted purpose into everyday scenarios
Instead of using “business discussions” without explanation, identify the proposed transaction or evaluation. The Trade Secrets Enterprise Guide recommends limiting use, identifying recipients, setting protection measures and addressing return or destruction. The following original worksheet tests how a drafted purpose would operate.
| Proposed action | Question for the NDA | Operational response |
|---|---|---|
| Assess a supplier’s process | Is evaluation of this supply arrangement covered? | Give the evaluation team controlled access. |
| Send a file to another group company | Is that entity an authorised recipient? | Obtain permission or extend the binding protection. |
| Use a sample design in a product | Does a separate licence authorise commercial use? | Pause product use until rights are agreed. |
| Upload technical data to an external AI tool | Is that onward disclosure and processing permitted? | Review the tool and contract before uploading. |
| Keep a backup after discussions end | Does a defined retention exception apply? | Restrict retained copies and record the reason. |
This worksheet does not decide the enforceability of a particular clause. It exposes decisions the parties should resolve before exchanging material. Keep evaluation permission separate from rights to commercial exploitation. If a recipient needs commercial rights, negotiate them expressly in the appropriate agreement.
Choose one-way or mutual duties and workable exceptions
Use a one-way structure when only one party is disclosing protected information and a mutual structure when both will do so. The VIMA document suite includes NDA materials as drafting starting points, with a warning that the documents require tailoring. The model label does not establish the facts of your exchange.
Discuss treatment of material already public, demonstrably known beforehand, independently developed or lawfully obtained elsewhere. The party invoking an exclusion may need evidence under the negotiated terms. Avoid assuming that removing a confidentiality stamp makes non-public information available for unrestricted use.
Address legally compelled disclosure with an appropriate process and legal limits. Consider notification, the permitted extent of disclosure and assistance seeking protection, without writing a promise that obstructs lawful reporting or mandatory cooperation. Obtain advice where employment, whistleblowing or regulatory duties intersect with confidentiality.
Separate the period during which information may be disclosed from the period during which duties survive. A short evaluation can involve a trade secret that remains sensitive long afterwards. Specify what event ends the relevant obligation and which categories need continuing protection, with legal advice. Do not adopt an arbitrary standard number of years without considering the material and the governing law.
Map onward access and commercial rights
Separate the evaluation team from recipients or uses requiring further agreement.
Keep access, ownership and retention on separate tracks
Maintain a disclosure log identifying the file version, recipient, date and purpose. Match repository permissions to the authorised group, and confirm obligations for advisers or contractors who receive information. If a recipient leaves the project, close access rather than waiting for the NDA’s stated duration to expire.
The legal ownership and IP holding arrangements determine who can grant the relevant rights. An NDA does not itself complete an intellectual property assignment . Check separate ownership and licensing documents before commercial deployment.
Agree what happens on termination, including return, deletion, permitted legal retention and backup handling. A blanket deletion promise may not match technical reality; define any exception narrowly and keep confidentiality duties on retained material.
For an oral presentation, record the meeting date, participants, topic and any written follow-up required by the negotiated agreement. For a data room, preserve the access list and changes to permissions. At project closure, record return or deletion requests and any justified retained copies. These practical records support the contractual boundary without pretending that the business can prove deletion from every backup system merely from a signed NDA.
Approve the NDA only when the disclosure plan fits
Before sharing, test a representative file, a meeting disclosure and a proposed onward recipient against the drafted terms. Confirm legal parties, purpose, duration, exceptions, governing law and dispute arrangements with counsel.
If information has already leaked, preserve the relevant records, restrict further access and obtain legal advice promptly. Where personal data is involved, assess the separate data-protection obligations; a confidentiality agreement alone does not establish that a disclosure is lawful.
Prepare the contract and access handover
Bring the proposed exchange, recipient list and ownership records for a scoped review.
Frequently asked questions
Does every NDA need to be mutual?
No. Choose the structure that matches who will disclose information and who must protect it.
Is there one mandatory confidentiality period?
Do not assume one standard duration fits every category. Agree terms appropriate to the information and obtain advice on continuing protection.
Can a group affiliate receive the files automatically?
Not necessarily. Check authorised-recipient provisions and the protection binding that entity.
Does signing an NDA permit personal-data sharing?
Not by itself. Assess the applicable data-protection basis and safeguards separately.